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.

17781779178017811782178317841785178617871788178917901791179217931794179517961797179817991800180118021803180418051806180718081809In the table above, attribute bits marked as “unassigned” are reserved for assignment by<strong>EPC</strong>global in future versions of this specification. Implementations of the encoding anddecoding rules specified herein SHALL accept any value of the attribute bits, whetherreserved or not. Applications, however, SHOULD direct an encoder to write a zero foreach unassigned bit, and SHOULD NOT rely upon the value of an unassigned bitdecoded from a tag, as doing so may cause interoperability problems if an unassignedvalue is assigned in a future revision to this specification.12 <strong>EPC</strong> <strong>Tag</strong> URI and <strong>EPC</strong> Raw URIThe <strong>EPC</strong> memory bank of a Gen 2 tag contains a binary-encoded <strong>EPC</strong>, along with othercontrol information. Applications do not normally process binary data directly. Anapplication wishing to read the <strong>EPC</strong> may receive the <strong>EPC</strong> as a Pure Identity <strong>EPC</strong> URI, asdefined in Section 6. In other situations, however, a capturing application may beinterested in the control information on the tag as well as the <strong>EPC</strong>. Also, an applicationthat writes the <strong>EPC</strong> memory bank needs to specify the values for control information thatare written along with the <strong>EPC</strong>. In both of these situations, the <strong>EPC</strong> <strong>Tag</strong> URI and <strong>EPC</strong>Raw URI may be used.The <strong>EPC</strong> <strong>Tag</strong> URI specifies both the <strong>EPC</strong> and the values of control information in the<strong>EPC</strong> memory bank. It also specifies which of several variant binary coding schemes is tobe used (e.g., the choice between SGTIN-96 and SGTIN-198). As such, an <strong>EPC</strong> <strong>Tag</strong>URI completely and uniquely specifies the contents of the <strong>EPC</strong> memory bank. The <strong>EPC</strong>Raw URI also specifies the complete contents of the <strong>EPC</strong> memory bank, but repesentsthe memory contents as a single decimal or hexadecimal numeral.12.1Structure of the <strong>EPC</strong> <strong>Tag</strong> URI and <strong>EPC</strong> Raw URIThe <strong>EPC</strong> <strong>Tag</strong> URI begins with urn:epc:tag:, and is used when the <strong>EPC</strong> memorybank contains a valid <strong>EPC</strong>. <strong>EPC</strong> <strong>Tag</strong> URIs resemble Pure Identity <strong>EPC</strong> URIs, but withadded control information. The <strong>EPC</strong> Raw URI begins with urn:epc:raw:, and isused when the <strong>EPC</strong> memory bank does not contain a valid <strong>EPC</strong>. This includes situationswhere the toggle bit (bit 17 h ) is set to one, as well as situations where the toggle bit is setto zero but the remainder of the <strong>EPC</strong> bank does not conform to the coding rules specifiedin Section 14, either because the header bits are unassigned or the remainder of the binaryencoding violates a validity check for that header.The following figure illustrates these URI forms.Copyright ©2005- 2011 <strong>GS1</strong> AISBL, All Rights Reserved. Page 66 of 218

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

Saved successfully!

Ooh no, something went wrong!