GS1 EPC Tag Data Standard 1.6 - Indicod-Ecr

45494550455145524553455445554556455745584559456045614562456345644565456645674568456945704571457245734574457545764577457845794580458145824583the case of a Data Addendum Packed Object containing only Delete operations, and thecase of a Packed Object that uses No-directory compaction (see I.7.1). When a Datasection is present, it follows the Object Info section (and the Secondary ID and AuxFormat sections, if present). Depending on the characteristics of the encoded IDs anddata strings, the Data section may include one or both of two subsections in the followingorder: a Known-Length Numerics subsection, and an AlphaNumerics subsection. Thefollowing paragraphs provide detailed descriptions of each of these Data Sectionsubsections. If all of the subsections of the Data section are utilized in a Packed Object,then the layout of the Data section is as shown in Figure I 8-1.1 stKLNFigure I 8-1: Maximum Structure of a Packed Objects Data sectionKnown-Length NumericsubsectionBinary2 ndKLNBinary…LastKLNBinaryNon-NumBaseBit(s)A/N Header BitsPrefixBit,PrefixRun(s)SuffixBit,SuffixRun(s)AlphaNumeric subsectionCharMapExt’d.NumBinaryBinary Data SegmentsExt’dNon-NumBinaryI.8.1 Known-length-Numerics subsection of the Data SectionFor always-numeric data strings, the ID table may indicate a fixed number of digits (thisfixed-length information is not encoded in the Packed Object) and/or a variable numberof digits (in which case the string’s length was encoded in the Aux Format section, asdescribed above). When a single data item is specified in the FormatString column(see J.2.3) as containing a fixed-length numeric string followed by a variable-lengthstring, the numeric string is encoded in the Known-length-numerics subsection and thealphanumeric string in the Alphanumeric subsection.The summation of fixed-length information (derived directly from the ID table) plusvariable-length information (derived from encoded bits as just described) results in a“known-length entry” for each of the always-numeric strings encoded in the currentPacked Object. Each all-numeric data string in a Packed Object (if described as allnumericin the ID Table) is encoded by converting the digit string into a single Binarynumber (up to 160 bits, representing a binary value between 0 and (10 48 -1)). Figure K-1in Annex K shows the number of bits required to represent a given number of digits. Ifan all-numeric string contains more than 48 digits, then the first 48 are encoded as one160-bit group, followed by the next group of up to 48 digits, and so on. Finally, theBinary values for each all-numeric data string in the Object are themselves concatenatedto form the Known-length-Numerics subsection.I.8.2 Alphanumeric subsection of the Data sectionThe Alphanumeric (A/N) subsection, if present, encodes all of the Packed Object’s datafrom any data strings that were not already encoded in the Known-length Numericssubsection. If there are no alphanumeric characters to encode, the entire A/N subsectionis omitted. The Alphanumeric subsection can encode any mix of digits and non-digitBase10BinaryNon-NumBinaryCopyright ©2005- 2011 GS1 AISBL, All Rights Reserved. Page 181 of 218