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...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>EPC</strong> = urn:epc:id:sgtin:0614141.012345.62852(10cc Syringe #62852 – trade item)<strong>EPC</strong> = urn:epc:id:grai:0614141.54321.2528(Pharma Tote #2528 – reusable asset)<strong>EPC</strong>s:All physical objectsEstablishes the context as all physical objectsTherefore, any <strong>EPC</strong> could go here605606607608609610611612613614615616617618619620621622urn:epc:id:sgtin:0614141.012345.62852urn:epc:id:grai:0614141.54321.2528…Figure 4. Illustration of <strong>EPC</strong> Identifier NamespaceIn contrast, the <strong>EPC</strong> namespace is a space of identifiers for any physical object. The setof <strong>EPC</strong>s can be thought of as identifiers for the members of the set “all physical objects.”<strong>EPC</strong>s are used in contexts where any type of physical object may appear, such as in theset of observations arising in the hospital storage room example above. Note that the<strong>EPC</strong> URI as illustrated in Figure 4 includes strings such as sgtin, grai, and so on aspart of the <strong>EPC</strong> URI identifier. This is in contrast to <strong>GS1</strong> Keys, where no such indicationis part of the key itself (instead, this is indicated outside of the key, such as in the XMLelement name in the example in Figure 3, or in the Application Identifier (AI)that accompanies a <strong>GS1</strong> Key in a <strong>GS1</strong> Element String).4.3 Relationship Between <strong>EPC</strong>s and <strong>GS1</strong> KeysThere is a well-defined relationship between <strong>EPC</strong>s and <strong>GS1</strong> keys. For each <strong>GS1</strong> key thatdenotes an individual physical object (as opposed to a class), there is a corresponding<strong>EPC</strong>. This correspondence is formally defined by conversion rules specified in Section 7,which define how to map a <strong>GS1</strong> key to the corresponding <strong>EPC</strong> value and vice versa. Thewell-defined correspondence between <strong>GS1</strong> keys and <strong>EPC</strong>s allows for seamless migrationof data between <strong>GS1</strong> key and <strong>EPC</strong> contexts as necessary.Copyright ©2005- 2011 <strong>GS1</strong> AISBL, All Rights Reserved. Page 22 of 218

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

Saved successfully!

Ooh no, something went wrong!