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
- No tags were found...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
19801981198219831984198519861987198819891990199119921993199419951996199719981999200020012002200320042005200620072008200920102011201220132014201520164. If the attribute bits are non-zero, construct a string [att=xNN], where NN is thevalue of the attribute bits as a 2-digit hexadecimal numeral.5. If the user memory indicator is non-zero, construct a string [umi=1].6. If Step 4 or Step 5 yielded a non-empty string, insert those strings following therightmost colon (“:”) character of the URI, followed by an additional coloncharacter.7. The resulting string is the <strong>EPC</strong> <strong>Tag</strong> URI.12.3.3 <strong>EPC</strong> <strong>Tag</strong> URI to <strong>EPC</strong> Pure Identity URIGiven: An <strong>EPC</strong> <strong>Tag</strong> URI as specified in Section 12. This is a string that matches the<strong>Tag</strong>URI production of the grammar in Section 12.4.Procedure:1. Starting with the <strong>EPC</strong> <strong>Tag</strong> URI, replace the prefix urn:epc:tag: withurn:epc:id:.2. Replace the <strong>EPC</strong> binary coding scheme name with the corresponding <strong>EPC</strong> schemename. For example, replace sgtin-96 or sgtin-198 with sgtin.3. If the coding scheme includes a filter value, remove the filter value (the digitfollowing the rightmost colon character) and the following dot (“.”) character.4. If the URI contains one or more control fields as specified in Section 12.2.2, removethem and the following colon character.5. The resulting string is the Pure Identity <strong>EPC</strong> URI.12.4GrammarThe following grammar specifies the syntax of the <strong>EPC</strong> <strong>Tag</strong> URI and <strong>EPC</strong> Raw URI.The grammar makes reference to grammatical elements defined in Sections 5 and 6.3.<strong>Tag</strong>OrRawURI ::= <strong>Tag</strong>URI | RawURI<strong>Tag</strong>URI ::= “urn:epc:tag:” <strong>Tag</strong>URIControlBody<strong>Tag</strong>URIControlBody ::= ( ControlField+ “:” )? <strong>Tag</strong>URIBody<strong>Tag</strong>URIBody ::= SGTIN<strong>Tag</strong>URIBody | SSCC<strong>Tag</strong>URIBody |SGLN<strong>Tag</strong>URIBody | GRAI<strong>Tag</strong>URIBody | GIAI<strong>Tag</strong>URIBody |GDTI<strong>Tag</strong>URIBody | GSRN<strong>Tag</strong>URIBody | GID<strong>Tag</strong>URIBody |DOD<strong>Tag</strong>URIBody | ADI<strong>Tag</strong>UriBodySGTIN<strong>Tag</strong>URIBody ::= SGTINEncName “:” NumericComponent “.”SGTINURIBodySGTINEncName ::= “sgtin-96” | “sgtin-198”SSCC<strong>Tag</strong>URIBody ::= SSCCEncName “:” NumericComponent “.”SSCCURIBodySSCCEncName ::= “sscc-96”Copyright ©2005- 2011 <strong>GS1</strong> AISBL, All Rights Reserved. Page 74 of 218
Change language