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.

GraphicSymbolNameBinaryValueURIFormGraphicSymbolName8 Eight Digit 111000 8 S CapitalS9 Nine Digit 111001 9 T CapitalTA Capital A 000001 A U CapitalUB Capital B 000010 B V CapitalVC Capital C 000011 C W CapitalWD Capital D 000100 D X CapitalXE Capital E 000101 E Y CapitalYF Capital F 000110 F Z CapitalLetter ZG Capital G 000111 GBinaryValue010011 S010100 T010101 U010110 V010111 W011000 X011001 Y011010 ZURIForm39683969397039713972Table 48. Characters Permitted in 6-bit Alphanumeric FieldsAppendix H (Intentionally Omitted)[This appendix is omitted so that Appendices I through M, which specify packed objects,have the same appendix letters as the corresponding annexes of ISO/IEC 15962 , 2ndEdition.]3973Appendix IPacked Objects Structure39743975397639773978397939803981398239833984I.1 OverviewThe Packed Objects format provides for efficient encoding and access of user data. ThePacked Objects format offers increased encoding efficiency compared to the No-Directory and Directory Access-Methods partly by utilizing sophisticated compactionmethods, partly by defining an inherent directory structure at the front of each PackedObject (before any of its data is encoded) that supports random access while reducing thefixed overhead of some prior methods, and partly by utilizing data-system-specificinformation (such as the <strong>GS1</strong> definitions of fixed-length Application Identifiers).I.2 Overview of Packed Objects DocumentationThe formal description of Packed Objects is presented in this Appendix and AppendicesJ, K, L, and M, as follows:Copyright ©2005- 2011 <strong>GS1</strong> AISBL, All Rights Reserved. Page 163 of 218

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

Saved successfully!

Ooh no, something went wrong!