GS1 EPC Tag Data Standard 1.6 - Indicod-Ecr

10521053105410551056105710581059106010611062106310641065106610671068106910701071107210731074107510761077107810791080108110821083108410851086108710881089109010911092The US DoD Guide to Uniquely Identifying Items defines a number of acceptablemethods for constructing unique item identifiers (UIIs). The UIIs that can be representedusing the Aerospace and Defense EPC identifier are those that are constructed throughthe combination of a CAGE code or DODAAC together with either: a serial number that is unique within the enterprise identifier. (UII Construct #1) an original part number and a serial number that is unique within the original partnumber (a subset of UII Construct #2)Note that the US DoD UID guidelines recognize a number of unique identifiers based onGS1 identifier keys as being valid UIDs. In particular, the SGTIN (GTIN + SerialNumber), GIAI, and GRAI with full serialization are recognized as valid UIDs. Thesemay be represented in EPC form using the SGTIN, GIAI, and GRAI EPC schemes asspecified in Sections 6.3.1, 6.3.5, and 6.3.4, respectively; the ADI EPC scheme is notused for this purpose. Conversely, the US DoD UID guidelines also recognize a widerange of enterprise identifiers issued by various issuing agencies other than thosedescribed above; such UIDs do not have a corresponding EPC representation.For purposes of identification within the ATA Spec 2000 framework, the ADI EPCscheme may be used for assigning a unique identifier for RFID purposes to a part that istraditionally not serialized or not required to be serialized for other purposes. In thissituation, the first character of the serial number component of the ADI EPC SHALL be asingle '#' character. This is used to indicate that the serial number does not correspond tothe serial number of a traditionally serialized part because the '#' character is notpermitted to appear within the values associated with either the SER or SEQ text elementidentifiers in Spec 2000.For parts that are traditionally serialized / required to be serialized for purposes other thanhaving a unique RFID identifier, and for all usage within US DoD UID guidelines, the '#'character SHALL NOT appear within the serial number element.For companies who serialize uniquely within their CAGE code or DODAAC, a zerolengthstring SHALL be used in place of the Original Part Number element whenconstructing an EPC.General syntax:urn:epc:id:adi:CAGEOrDODAAC.OriginalPartNumber.SerialExamples:urn:epc:id:adi:2S194..12345678901urn:epc:id:adi:W81X9C.3KL984PX1.2WMA52Grammar:ADI-URI ::= “urn:epc:id:adi:” ADIURIBodyADIURIBody ::= CAGECodeOrDODAAC “.” ADIComponent “.”ADIExtendedComponentADIComponent ::= ADIChar*ADIExtendedComponent ::= “%23”? ADIChar+ADIChar ::= UpperAlpha | Digit | OtherADICharCopyright ©2005- 2011 GS1 AISBL, All Rights Reserved. Page 37 of 218