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.

734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775urn:epc:id:sgtin:0614141.112345.400Each <strong>EPC</strong> scheme provides a namespace of identifiers that can be used to identifyphysical objects of a particular type. Collectively, the <strong>EPC</strong> URIs from all schemes areunique identifiers for any type of physical object.6.1 Use of the <strong>EPC</strong> URIThe <strong>EPC</strong> URI is the preferred way within an information system to denote a specificphysical object.The structure of the <strong>EPC</strong> URI guarantees worldwide uniqueness of the <strong>EPC</strong> across alltypes of physical objects and applications. In order to preserve worldwide uniqueness,each <strong>EPC</strong> URI must be used in its entirety when a unique identifier is called for, and notbroken into constituent parts nor the urn:epc:id: prefix abbreviated or dropped.When asking the question “do these two data structures refer to the same physicalobject?”, where each data structure uses an <strong>EPC</strong> URI to refer to a physical object, thequestion may be answered simply by comparing the full <strong>EPC</strong> URI strings as specified in[RFC3986], Section 6.2. In most cases, the “simple string comparison” method sufficies,though if a URI contains percent-encoding triplets the hexadecimal digits may requirecase normalization as described in [RFC3986], Section 6.2.2.1. The construction of the<strong>EPC</strong> URI guarantees uniqueness across all categories of objects, provided that the URI isused in its entirety.In other situations, applications may wish to exploit the internal structure of an <strong>EPC</strong> URIfor purposes of filtering, selection, or distribution. For example, an application may wishto query a database for all records pertaining to instances of a specific product identifiedby a GTIN. This amounts to querying for all <strong>EPC</strong>s whose <strong>GS1</strong> Company Prefix and itemreference components match a given value, disregarding the serial number component.Another example is found in the Object Name Service (ONS) [ONS1.0.1], which uses thefirst component of an <strong>EPC</strong> to delegate a query to a “local ONS” operated by an individualcompany. This allows the ONS system to scale in a way that would be quite difficult ifall ONS records were stored in a flat database maintained by a single organization.While the internal structure of the <strong>EPC</strong> may be exploited for filtering, selection, anddistribution as illustrated above, it is essential that the <strong>EPC</strong> URI be used in its entiretywhen used as a unique identifier.6.2 Assignment of <strong>EPC</strong>s to Physical ObjectsThe act of allocating a new <strong>EPC</strong> and associating it with a specific physical object iscalled “commissioning.” It is the responsibility of applications and business processesthat commission <strong>EPC</strong>s to ensure that the same <strong>EPC</strong> is never assigned to two differentphysical objects; that is, to ensure that commissioned <strong>EPC</strong>s are unique. Typically,commissioning applications will make use of databases that record which <strong>EPC</strong>s havealready been commissioned and which are still available. For example, in an applicationthat commissions SGTINs by assigning serial numbers sequentially, such a databasemight record the last serial number used for each base GTIN.Because visibility data and other business data that refers to <strong>EPC</strong>s may continue to existlong after a physical object ceases to exist, an <strong>EPC</strong> is ideally never reused to refer to aCopyright ©2005- 2011 <strong>GS1</strong> AISBL, All Rights Reserved. Page 28 of 218

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

Saved successfully!

Ooh no, something went wrong!