GS1 EPC Tag Data Standard 1.6 - Indicod-Ecr

101310141015101610171018101910201021102210231024102510261027102810291030103110321033103410351036103710381039104010411042104310441045104610471048104910501051a unique [GS1] Company Prefix may use any of the identity types and encodinginstructions described in the EPC Tag Data Standards document to encode tags.”General syntax:urn:epc:id:usdod:CAGEOrDODAAC.SerialNumberExample:urn:epc:id:usdod:2S194.12345678901Grammar:DOD-URI ::= “urn:epc:id:usdod:” DODURIBodyDODURIBody ::= CAGECodeOrDODAAC “.” DoDSerialNumberCAGECodeOrDODAAC ::= CAGECode | DODAACCAGECode ::= CAGECodeOrDODAACChar*5DODAAC ::= CAGECodeOrDODAACChar*6DoDSerialNumber ::= NumericComponentCAGECodeOrDODAACChar ::= Digit | “A” | “B” | “C” | “D” |“E” | “F” | “G” | “H” | “J” | “K” | “L” | “M” | “N” | “P” |“Q” | “R” | “S” | “T” | “U” | “V” | “W” | “X” | “Y” | “Z”6.3.10 Aerospace and Defense Identifier (ADI)The variable-length Aerospace and Defense EPC identifier is designed for use by theaerospace and defense sector for the unique identification of parts or items. The existingunique identifier constructs are defined in the Air Transport Association (ATA) Spec2000 standard [SPEC2000], and the US Department of Defense Guide to UniquelyIdentifying items [UID]. The ADI EPC construct provides a mechanism to directlyencode such unique identifiers in RFID tags and to use the URI representations at otherlayers of the EPCglobal architecture.Within the Aerospace & Defense sector identification constructs supported by the ADIEPC, companies are uniquely identified by their Commercial And Government Entity(CAGE) code or by their Department of Defense Activity Address Code (DODAAC).The NATO CAGE (NCAGE) code is issued by NATO / Allied Committee 135 and isstructurally equivalent to a CAGE code (five character uppercase alphanumeric excludingcapital letters I and O) and is non-colliding with CAGE codes issued by the US DefenseLogistics Information Service (DLIS). Note that in the remainder of this section, allreferences to CAGE apply equally to NCAGE.ATA Spec 2000 defines that a unique identifier may be constructed through thecombination of the CAGE code or DODAAC together with either: A serial number (SER) that is assigned uniquely within the CAGE code orDODAAC; or An original part number (PNO) that is unique within the CAGE code or DODAACand a sequential serial number (SEQ) that is uniquely assigned within that originalpart number.Copyright ©2005- 2011 GS1 AISBL, All Rights Reserved. Page 36 of 218