GS1 EPC Tag Data Standard 1.6 - Indicod-Ecr

32213222322332243225322632273228322932303231323232333234323532363237323832393240324132423243324432453246324732483249325032513252325332543255325632573258325932603261326232633264Access Method, Extended Syntax Indicator, and Data Format. The Access Method isspecified in the two most significant bits of the DSFID, and is encoded with the value“10” to designate the “Packed Objects” Access Method as specified in Appendix I hereinif the “Packed Objects” Access Method is employed, and is encoded with the value “00”to designate the “No-Directory” Access Method as specified in [ISO15962] if the “No-Directory” Access Method is employed. The next bit is set to one if there is a secondDSFID byte present. The five least significant bits specify the Data Format, whichindicates what data system predominates in the memory contents. If GS1 ApplicationIdentifiers (AIs) predominate, the value of “01001” specifies the GS1 Data Format 09 asregistered with ISO, which provides most efficient support for the use of AI dataelements. Appendix I through Appendix M of this specification contain the completespecification of the “Packed Objects” Access Method; it is expected that this content willappear as Annex I through Annex M, respectively, of ISO/IEC 15962, 2 nd Edition[ISO15962], when the latter becomes available A complete definition of the DSFID isspecified in ISO/IEC 15962 [ISO15962]. A complete definition of the table that governsthe Packed Objects encoding of Application Identifiers (AIs) is specified by GS1 andregistered with ISO under the procedures of ISO/IEC 15961, and is reproduced in E.3.This table is similar in format to the hypothetical example shown as Table L-1 inAppendix L, but with entries to accommodate encoding of all valid ApplicationIdentifiers.A tag whose User Memory Bank programming conforms to this specification SHALL beencoded using either the Packed Objects Access Method or the No-Directory AccessMethod, provided that if the No-Directory Access Method is used that the “applicationdefined”compaction mode as specified in [ISO15962] SHALL NOT be used. A tagwhose User Memory Bank programming conforms to this specification MAY use anyregistered Data Format including Data Format 09.Where the Packged Objects specification in Appendix I makes reference to Extensible BitVectors (EBVs), the format specified in Appendix D SHALL be used.A hardware or software component that conforms to this specification for User MemoryBank reading and writing SHALL fully implement the Packed Objects Access Method asspecified in Appendix I through Appendix M of this specification (implying support forall registered Data Formats), SHALL implement the No-Directory Access Method asspecified in [ISO15962], and MAY implement other Access Methods defined in[ISO15962] and subsequent versions of that standard. A hardware or softwarecomponent NEED NOT, however, implement the“application-defined” compaction modeof the No-Directory Access Method as specified in [ISO15962]. A hardware or softwarecomponent whose intended function is only to initialize tags (e.g., a printer) may conformto a subset of this specification by implementing either the Packed Objects or the No-Directory access method, but in this case NEED NOT implement both.Explanation (non-normative): This specification allows two methods of encoding data inuser memory. The ISO/IEC 15962 “No-Directory” Access Method has an installed baseowing to its longer history and acceptance within certain end user communities. ThePacked Objects Access Method was developed to provide for more efficient reading andwriting of tags, and less tag memory consumption.Copyright ©2005- 2011 GS1 AISBL, All Rights Reserved. Page 127 of 218