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.

3421342234233424342534263427342834293430343134323433343434353436343734383439344034413442344334443445344634473448344934503451345234533454345534563457345834593460URI in this specification and the specifications referenced herein (including the <strong>GS1</strong>General Specifications).The following conformance requirements apply to Pure Identity URI <strong>EPC</strong> Producers: A Pure Identity <strong>EPC</strong> URI Producer SHALL produce as output strings that satisfy thegrammar in Section 6, including all constraints on the number of characters in variouscomponents. A Pure Identity <strong>EPC</strong> URI Producer SHALL NOT produce as output a string thatbegins with the characters urn:epc:id: that does not satisfy the grammar ofSection 6, including all constraints on the number of characters in variouscomponents. If a Pure Identity <strong>EPC</strong> URI Producer constructs a Pure Identity <strong>EPC</strong> URI fromcomponent parts, it SHALL do so in a manner consistent with this specification.The following conformance requirements apply to <strong>EPC</strong> <strong>Tag</strong>/Raw URI Consumers:An <strong>EPC</strong> <strong>Tag</strong>/Raw URI Consumer SHALL accept as input any string that satisfies the<strong>Tag</strong>URI production of the grammar of Section 12.4, and that can be encodedaccording to Section 14.3 without causing an exception.An <strong>EPC</strong> <strong>Tag</strong>/Raw URI Consumer MAY accept as input any string that satisfies theRawURI production of the grammar of Section 12.4.An <strong>EPC</strong> <strong>Tag</strong>/Raw URI Consumer SHALL reject as invalid any input string thatbegins with the characters urn:epc:tag: that does not satisfy the grammar ofSection 12.4, or that causes the encoding procedure of Section 14.3 to raise anexception.An <strong>EPC</strong> <strong>Tag</strong>/Raw URI Consumer that accepts <strong>EPC</strong> Raw URIs as input SHALL rejectas invalid any input string that begins with the characters urn:epc:raw: that doesnot satisfy the grammar of Section 12.4.To the extent that an <strong>EPC</strong> <strong>Tag</strong>/Raw URI Consumer interprets the contents of an <strong>EPC</strong><strong>Tag</strong> URI or <strong>EPC</strong> Raw URI, it SHALL do so in a manner consistent with thedefinitions of the <strong>EPC</strong> <strong>Tag</strong> URI and <strong>EPC</strong> Raw URI in this specification and thespecifications referenced herein (including the <strong>GS1</strong> General Specifications).The following conformance requirements apply to <strong>EPC</strong> <strong>Tag</strong>/Raw URI Producers: An <strong>EPC</strong> <strong>Tag</strong>/Raw URI Producer SHALL produce as output strings that satisfy the<strong>Tag</strong>URI production or the RawURI production of the grammar of Seciton 12.4,provided that any output string that satisfies the <strong>Tag</strong>URI production must beencodable according to the encoding procedure of Section 14.3 without raising anexception. An <strong>EPC</strong> <strong>Tag</strong>/Raw URI Producer SHALL NOT produce as output a string that beginswith the characters urn:epc:tag: or urn:epc:raw: except as specified in theprevious bullet. If an <strong>EPC</strong> <strong>Tag</strong>/Raw URI Producer constructs an <strong>EPC</strong> <strong>Tag</strong> URI or <strong>EPC</strong> Raw URI.fromcomponent parts, it SHALL do so in a manner consistent with this specification.Copyright ©2005- 2011 <strong>GS1</strong> AISBL, All Rights Reserved. Page 132 of 218

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

Saved successfully!

Ooh no, something went wrong!