11.08.2015 Views

GS1 EPC Tag Data Standard 1.6 - Indicod-Ecr

GS1 EPC Tag Data Standard 1.6 - Indicod-Ecr

GS1 EPC Tag Data Standard 1.6 - Indicod-Ecr

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

4477447844794480448144824483448444854486448744884489449044914492449344944495449644974498449945004501450245034504450545064507Pattern‘1’ “Packed-Object” compaction See I.7.2‘000’ “Application-Defined”, as defined for the No-Directoryaccess methodSee I.7.1‘001’ “Compact”, as defined for the No-Directory access method See I.7.1‘010’ “UTF-8”, as defined for the No-Directory access method See I.7.1‘011bbbb’(‘bbbb’ shall be in the range of 4..14): reserved for futuredefinitionSee I.7.1If the Compact-Parameter bit pattern is ‘1’, then the remainder of the Aux Format sectionis encoded as described in I.7.2; otherwise, the remainder of the Aux Format section isencoded as described in I.7.1.I.7.1 Support for No-Directory compaction methodsIf any of the No-Directory compaction methods were selected by the Compact-Parameterbits, then the Compact-Parameter bits are followed by an byte-alignment padding patternconsisting of zero or more ‘0’ bits followed by a single ‘1’ bit, so that the next bit afterthe ‘1’ is aligned as the most-significant bit of the next byte.This next byte is defined as the first octet of a “No-Directory <strong>Data</strong> section”, which is usedin place of the <strong>Data</strong> section described in I.8. The data strings of this Packed Object areencoded in the order indicated by the Object Info section of the Packed Object,compacted exactly as described in Annex D of [ISO15962] (Encoding rules for No-Directory Access-Method), with the following two exceptions:The Object-Identifier is not encoded in the “No-Directory <strong>Data</strong> section”, because ithas already been encoded into the Object Info and Secondary ID sections.The Precursor is modified in that only the three Compaction Type Code bits aresignificant, and the other bits in the Precursor are set to ‘0’.Therefore, each of the data strings invoked by the ID Table entry are separately encodedin a modified data set structure as: The are determined and encoded as described in D.1.1 andD.1.2 of [ISO15962] and the is determined and encoded asdescribed in D.2 of [ISO15962].Following the last data set, a terminating precursor value of zero shall not be encoded(the decoding system recognizes the end of the data using the encoded ObjectLength ofthe Packed Object).I.7.2 Support for the Packed-Object compaction methodIf the Packed-Object compaction method was selected by the Compact-Parameter bits,then the Compact-Parameter bits are followed by zero or more Aux Format bits, as maybe invoked by the ID Table entries used in this Packed Object. The Aux Format bits areCopyright ©2005- 2011 <strong>GS1</strong> AISBL, All Rights Reserved. Page 179 of 218

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!