GS1 EPC Tag Data Standard 1.6 - Indicod-Ecr

5622562356245625562656275628562956305631563256335634563556365637563856395640564156425643564456455646564756485649565056515652565356545655565656575658565956605661566256635664a) there are no further Packed Objects in Memory (if the leading 8-bit pattern isall zeroes, this indicates the Terminating Pattern)b) one or more Padding bytes are present. If padding is present, skip the paddingbytes, which are as described in Annex I, and examine the first non-pad byte.c) a Directory Pointer is encoded. If present, record the offset indicated by thefollowing bytes, and then continue examining from the next byte in memoryd) a Format Flags section is present, in which case process this section accordingto the format described in Annex Ie) a default-format Packed Object begins at this locationIf the Packed Object had a Format Flags section, then this section may indicate that thePacked Object is of the ID Map format, otherwise it is of the ID List format. Accordingto the indicated format, parse the Object Information section to determine the ObjectLength and ID information contained in the Packed Object. See Annex I for the detailsof the two formats. Regardless of the format, this step results in a known Object length(in bits) and an ordered list of the ID Values encoded in the Packed Object. From thegoverning ID Table, determine the list of characteristics for each ID (such as the presenceand number of Secondary ID bits).Parse the Secondary ID section of the Object, based on the number of Secondary ID bitsinvoked by each ID Value in sequence. From this information, create a list of the fullyqualifiedID Values (FQIDVs) that are encoded in the Packed Object.Parse the Aux Format section of the Object, based on the number of Aux Format bitsinvoked by each FQIDV in sequence.Parse the Data section of the Packed Object:a) If one or more of the FQIDVs indicate all-numeric data, then the PackedObject’s Data section contains a Known-Length Numeric subsection, whereinthe digit strings of these all-numeric items have been encoded as a series ofbinary quantities. Using the known length of each of these all-numeric dataitems, parse the correct numbers of bits for each data item, and convert eachset of bits to a string of decimal digits.b) If (after parsing the preceding sections) one or more of the FQIDVs indicatealphanumeric data, then the Packed Object’s Data section contains anAlphaNumeric subsection, wherein the character strings of thesealphanumeric items have been concatenated and encoded into the structuredefined in Annex I. Decode this data using the “Decoding Alphanumericdata” procedure outlined below.For each FQIDV in the decoded sequence:a) convert the FQIDV to an OID, by appending the OID string defined in theregistered format’s ID Table to the root OID string defined in that ID Table(or to the default Root OID, if none is defined in the table)b) Complete the OID/Value pair by parsing out the next sequence of decodedcharacters. The length of this sequence is determined directly from the IDTable (if the FQIDV is specified as fixed length) or from a correspondingentry encoded within the Aux Format section.Copyright ©2005- 2011 GS1 AISBL, All Rights Reserved. Page 212 of 218