GS1 EPC Tag Data Standard 1.6 - Indicod-Ecr

405740584059406040614062406340644065406640674068406940704071407240734074407540764077407840794080408140824083408440854086408740884089409040914092409340944095 Certain flag patterns indicate an inter-Object pattern (Directory Pointer orPadding) Other flag patterns indicate the Packed Object’s type (Map or. List), and mayindicated the presence of an optional Addendum subsection for editing.Object Info: All Packed Objects contain an Object Info Section which includesObject Length Information and ID Value Information: Object Length Information includes an ObjectLength field (indicating the overalllength of the Packed Object in octets) followed by Pad Indicator bit, so that thenumber of significant bits in the Packed Object can be determined. ID Value Information indicates which Identifiers are present and in what order,and (if an IDLPO) also includes a leading NumberOfIDs field, indicating howmany ID Values are encoded in the ID List.The Object Info section is encoded in one of the following formats, as shown inFigure I 3-3 and Figure I 3-4. ID List (IDLPO) Object Info format: Object Length (EBV-6) plus Pad Indicator bit A single ID List or an ID Lists Section (depending on Format Flags) ID Map (IDMPO) Object Info format: One or more ID Map sections Object Length (EBV-6) plus Pad Indicator bitFor either of these Object Info formats, an Optional Addendum subsection may bepresent at the end of the Object Info section.Secondary ID Bits: A Packed Object may include a Secondary ID section, if neededto encode additional bits that are defined for some classes of IDs (these bits completethe definition of the ID).Aux Format Bits: A Data Packed Object may include an Aux Format Section, whichif present encodes one or more bits that are defined to support data compression, butdo not contribute to defining the ID.Data Section: A Data Packed Object includes a Data Section, representing thecompressed data associated with each of the identifiers listed within the PackedObject. This section is omitted in a Directory Packed Object, and in a Packed Objectthat uses No-directory compaction (see I.7.1). Depending on the declaration of dataformat in the relevant ID table, the Data section will contain either or both of twosubsections: Known-Length Numerics subsection: this subsection compacts andconcatenates all of the non-empty data strings that are known a priori to benumeric. AlphaNumeric subsection: this subsection concatenates and compacts all of thenon-empty data strings that are not a priori known to be all-numeric.Copyright ©2005- 2011 GS1 AISBL, All Rights Reserved. Page 166 of 218