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.

15031504150515061507150815091510151115121513151415151516151715181519152015211522152315241525152615271528152915301531153215331534153515361537153815392. Number the digits and characters of the <strong>GS1</strong> element string as shown above.3. Determine the number of digits L in the <strong>GS1</strong> Company Prefix. This may be done, forexample, by reference to an external table of company prefixes.4. Arrange the digits as shown for the <strong>EPC</strong> URI. Note that the GDTI check digit d 13 isnot included in the <strong>EPC</strong> URI.Example:<strong>EPC</strong> URI: urn:epc:id:gdti:0614141.12345.006847<strong>GS1</strong> element string: (253) 0614141 12345 2 006847Spaces have been added to the <strong>GS1</strong> element string for clarity, but they are never encoded.8 URIs for <strong>EPC</strong> Pure Identity PatternsCertain software applications need to specify rules for filtering lists of <strong>EPC</strong> pureidentities according to various criteria. This specification provides a Pure Identity PatternURI form for this purpose. A Pure Identity Pattern URI does not represent a single <strong>EPC</strong>,but rather refers to a set of <strong>EPC</strong>s. A typical Pure Identity Pattern URI looks like this:urn:epc:idpat:sgtin:0652642.*.*This pattern refers to any <strong>EPC</strong> SGTIN, whose <strong>GS1</strong> Company Prefix is 0652642, andwhose Item Reference and Serial Number may be anything at all. The tag length andfilter bits are not considered at all in matching the pattern to <strong>EPC</strong>s.In general, there is a Pure Identity Pattern URI scheme corresponding to each PureIdentity <strong>EPC</strong> URI scheme (Section 6.3), whose syntax is essentially identical except thatany number of fields starting at the right may be a star (*). This is more restrictive than<strong>EPC</strong> <strong>Tag</strong> Pattern URIs (Section 13), in that the star characters must occupy adjacentrightmost fields and the range syntax is not allowed at all.The pure identity pattern URI for the DoD Construct is as follows:urn:epc:idpat:usdod:CAGECodeOrDODAACPat.serialNumberPatwith similar restrictions on the use of star (*).8.1 SyntaxThe grammar for Pure Identity Pattern URIs is given below.IDPatURI ::= “urn:epc:idpat:” IDPatBodyIDPatBody ::= GIDIDPatURIBody | SGTINIDPatURIBody |SGLNIDPatURIBody | GIAIIDPatURIBody | SSCCIDPatURIBody |GRAIIDPatURIBody | GSRNIDPatURIBody | GDTIIDPatURIBody |DODIDPatURIBody | ADIPatURIBodyGIDIDPatURIBody ::= “gid:” GIDIDPatURIMainGIDIDPatURIMain ::=2*(NumericComponent “.”) NumericComponent| 2*(NumericComponent “.”) “*”Copyright ©2005- 2011 <strong>GS1</strong> AISBL, All Rights Reserved. Page 51 of 218

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

Saved successfully!

Ooh no, something went wrong!