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.

188018811882188318841885188618871888188918901891189218931894189518961897189818991900190119021903190419051906190719081909191019111912urn:epc:raw:[att=x01][umi=1][xpc=x0004]:96.x1234567890ABCDEF01234567This is a tag with toggle=0, random data in bits 20 h onward (not decodable as an <strong>EPC</strong>),the hazardous material attribute bit set to one, non-zero contents in user memory, andhas been recommissioned (as indicated by the extended PC).urn:epc:raw:[xpc=x0001]:96.xC1.x1234567890ABCDEF01234567This is a tag with toggle=1, Application Family Indicator = C1 (hexadecimal), and hashad its user memory killed (as indicated by the extended PC).12.3<strong>EPC</strong> <strong>Tag</strong> URI and <strong>EPC</strong> Pure Identity URIThe Pure Identity <strong>EPC</strong> URI as defined in Section 6 is a representation of an <strong>EPC</strong> for usein information systems. The only information in a Pure Identity <strong>EPC</strong> URI is the <strong>EPC</strong>itself. The <strong>EPC</strong> <strong>Tag</strong> URI, in contrast, contains additional information: it specifies thecontents of all control information fields in the <strong>EPC</strong> memory bank, and it also specifieswhich encoding scheme is used to encode the <strong>EPC</strong> into binary. Therefore, to convert aPure Identity <strong>EPC</strong> URI to an <strong>EPC</strong> <strong>Tag</strong> URI, additional information must be provided.Conversely, to extract a Pure Identity <strong>EPC</strong> URI from an <strong>EPC</strong> <strong>Tag</strong> URI, this additionalinformation is removed. The procedures in this section specify how these conversionsare done.12.3.1 <strong>EPC</strong> Binary Coding SchemesFor each <strong>EPC</strong> scheme as specified in Section 6, there are one or more corresponding <strong>EPC</strong>Binary Coding Schemes that determine how the <strong>EPC</strong> is encoded into binaryrepresentation for use in RFID tags. When there is more than one <strong>EPC</strong> Binary CodingScheme available for a given <strong>EPC</strong> scheme, a user must choose which binary codingscheme to use. In general, the shorter binary coding schemes result in fewer bits andtherefore permit the use of less expensive RFID tags containing less memory, but arerestricted in the range of serial numbers that are permitted. The longer binary codingschemes allow for the full range of serial numbers permitted by the <strong>GS1</strong> GeneralSpecifications, but require more bits and therefore more expensive RFID tags.It is important to note that two <strong>EPC</strong>s are the same if and only if the Pure Identity <strong>EPC</strong>URIs are character for character identical. A long binary encoding (e.g., SGTIN-198) isnot a different <strong>EPC</strong> from a short binary encoding (e.g., SGTIN-96) if the <strong>GS1</strong> CompanyPrefix, item reference with indicator, and serial numbers are identical.The following table enumerates the available <strong>EPC</strong> binary coding schemes, and indicatesthe limitations imposed on serial numbers.<strong>EPC</strong>Scheme<strong>EPC</strong> BinaryCodingScheme<strong>EPC</strong> +FilterBitCountIncludesFilterValueSerial Number Limitationsgtin sgtin-96 96 Yes Numeric-only, no leading zeros, decimalvalue must be less than 2 38 (i.e., decimalvalue less than or equal to274,877,906,943).Copyright ©2005- 2011 <strong>GS1</strong> AISBL, All Rights Reserved. Page 70 of 218

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

Saved successfully!

Ooh no, something went wrong!