GS1 Web URI Structure Standard
GS1 Web URI Structure Standardenabling consistent representation of GS1 identification keyswithin web addresses to link to online information andservicesRelease 1.0, Ratified, Aug 2018
GS1 Web URI Structure StandardDocument SummaryDocument ItemCurrent ValueDocument NameGS1 Web URI Structure StandardDocument DateAug 2018Document Version1.0Document IssueDocument StatusRatifiedDocument Descriptionenabling consistent representation of GS1 identification keys within webaddresses to link to online information and servicesContributorsNameOrganisationDominique Guinard (Chair)EVRYTHNGSeán Lightholder (Chair)Wal-Mart Stores, Inc.Laurent Tonnelier (Chair)mobiLead / serviceTagHirokazu NagaiJapan Pallet Rental CorporationDeborah ArcoleoHershey Company (The)Stephen BrownMead WestvacoHenk DannenbergNXP SemiconductorsVera FeuersteinNestleBrian NewbyUnilever UKMandeep SodhiNestleJohn TerwilligerAbbott Laboratories Inc.Julie VargasAvery Dennison RFIDEvan BacchusCostco WholesaleYolande DiazCarrefourJonas ElanderAxfood Sverige ABMax EngströmH&MSylvia Rubio AlegrenICA ABHans Peter ScheidtC & A SCSJoachim WilkensC & A SCSMarc BlanchetViageniePhilip Allgaierbpcompass GmbHDalibor BiscevicBusiness Technologies LtdPatrick ChanezINEXTO SARoland DonzelleSQUARE / TINTAMARAnthony GraignicYESITISMark HarrisonMilecastle Media LimitedJohn HerzigBarcode Graphics Inc CanadaRelease 1.0, Ratified, Aug 2018 2018 GS1 AISBLPage 2 of 54
GS1 Web URI Structure StandardNameOrganisationAndr‚ MachadoTrustaTAGZbigniew SaganAdvanced Track and TraceKim SimonalleQliktag Software (formally Zeebric LLC)Elizabeth WaldorfTraceLinkGeorge Wright IVProduct Identification & Processing SystemsIlteris OneyecomesKoji AsanoGS1 JapanAndrea AusiliGS1 ItalyXavier BarrasGS1 FranceMats BjorkqvistGS1 SwedenJonas BuskenfriedGS1 SwedenEmanuela CasaliniGS1 ItalyKarolin CatelaGS1 SwedenMadalina CernatGS1 RomaniaAnthony ChanGS1 Hong KongNicolas CollignonGS1 Belgium & LuxembourgLuiz CostaGS1 BrazilBenjamin CoutyGS1 FranceLeonardo de ViveirosGS1 BrazilKevin DeanGS1 CanadaFerran Domenech FusteGS1 SpainXiaowen DongGS1 ChinaDorothee Doswald-KuhlmannGS1 SwitzerlandVanessa GiulieriGS1 ItalyHeinz GrafGS1 SwitzerlandRami HabbalGS1 UAEGary HartleyGS1 New ZealandHideki IchiharaGS1 JapanYoshihiko IwasakiGS1 JapanRicky JonesGS1 UKSang Ik JungGS1 KoreaKimmo KeravuoriGS1 FinlandKazuna KimuraGS1 JapanBoris KrcelicGS1 ArgentinaIlka MachemerGS1 GermanyNoriyuki MamaGS1 JapanRoberto MatsubayashiGS1 BrazilDaniel Mueller-SauterGS1 SwitzerlandPrince NamaneGS1 South AfricaMori NaokoGS1 JapanRelease 1.0, Ratified, Aug 2018 2018 GS1 AISBLPage 3 of 54
GS1 Web URI Structure StandardNameOrganisationDaisuke NegishiGS1 JapanStaffan OlssonGS1 SwedenMichel OttikerGS1 SwitzerlandSebastián PerazzoGS1 ArgentinaBijoy PeterGS1 IndiaSarina PielaatGS1 NetherlandsNeil PiperGS1 UKPaul ReidGS1 UKAlexandre RieucauGS1 FranceNick RusmanGS1 NetherlandsRoxana Saravia BulminiGS1 ArgentinaSue SchmidGS1 AustraliaEugen SehorzGS1 Austria GmbHXiaojing ShaoGS1 ChinaSean SloanGS1 AustraliaAndrew SteeleGS1 AustraliaXia TaoGS1 ChinaRalph TroegerGS1 GermanyFrits van den BosGS1 NetherlandsRocio VizcarraGS1 ArgentinaAmber WallsGS1 USQian WangGS1 FranceShu WangGS1 ChinaYi WangGS1 ChinaStephan WijnkerGS1 AustraliaCarrie WilkieGS1 USRuoyun YanGS1 ChinaYuwen ZhangGS1 ChinaPeter AlvarezGS1 Global OfficeDipan AnarkatGS1 Global OfficePhil ArcherGS1 Global OfficeHenri BarthelGS1 Global OfficeRobert BeidemanGS1 Global OfficeChuck BissGS1 Global OfficeScott GrayGS1 Global OfficeEric KauzGS1 Global OfficeSean LockheadGS1 Global OfficeJeanette McVeighGS1 Global OfficeMarkus MuellerGS1 Global OfficeGreg RoweGS1 Global OfficeRelease 1.0, Ratified, Aug 2018 2018 GS1 AISBLPage 4 of 54
GS1 Web URI Structure StandardNameOrganisationKevin StarkGS1 Global OfficeGarry ThanielGS1 Global OfficeElena TomanovichGS1 Global OfficeLog of ChangesReleaseDate of ChangeChanged BySummary of Change1.0Aug 2018Phil Archer, DominiqueGuinard, Mark Harrison,Marie Petre & GregRoweInitial release developed on WR 17-000343DisclaimerGS1 , under its IP Policy, seeks to avoid uncertainty regarding intellectual property claims by requiring the participants inthe Work Group that developed this GS1 Web URI Standard to agree to grant to GS1 members a royalty-free licence or aRAND licence to Necessary Claims, as that term is defined in the GS1 IP Policy. Furthermore, attention is drawn to thepossibility that an implementation of one or more features of this Standard may be the subject of a patent or otherintellectual property right that does not involve a Necessary Claim. Any such patent or other intellectual property right isnot subject to the licencing obligations of GS1. Moreover, the agreement to grant licences provided under the GS1 IP Policydoes not include IP rights and any claims of third parties who were not participants in the Work Group.Accordingly, GS1 recommends that any organisation developing an implementation designed to be in conformance with thisStandard should determine whether there are any patents that may encompass a specific implementation that theorganisation is developing in compliance with the Standard and whether a licence under a patent or other intellectualproperty right is needed. Such a determination of a need for licencing should be made in view of the details of the specificsystem designed by the organisation in consultation with their own patent counsel.THIS DOCUMENT IS PROVIDED “AS IS” WITH NO WARRANTIES WHATSOEVER, INCLUDING ANY WARRANTY OFMERCHANTABILITY, NONINFRINGEMENT, FITNESS FOR PARTICULAR PURPOSE, OR ANY WARRANTY OTHER WISE ARISINGOUT OF THIS SPECIFICATION. GS1 disclaims all liability for any damages arising from use or misuse of this document,whether special, indirect, consequential, or compensatory damages, and including liability for infringement of anyintellectual property rights, relating to use of information in or reliance upon this document.GS1 retains the right to make changes to this document at any time, without notice. GS1 makes no warranty for the use ofthis document and assumes no responsibility for any errors which may appear in the document, nor does it make acommitment to update the information contained herein.GS1 and the GS1 logo are registered trademarks of GS1 AISBL.Release 1.0, Ratified, Aug 2018 2018 GS1 AISBLPage 5 of 54
GS1 Web URI Structure StandardTable of Contents1Executive overview . 82Foreword . 83Introduction . 943.1What is a URI? . 93.2Why Linked Data? . 123.3Use of GS1 Web URIs with various kinds of data carriers. 12Working assumptions and technical design principles . 144.1Do no harm to the existing GS1 System Architecture and existing identification practices . 144.2Use of barcodes containing GS1 Web URI and GS1 barcodes . 154.3A note on terminology . 164.4Security and privacy of information . 174.5Contextual information . 174.6Access to traceability data by various supply chain stakeholders . 174.7Supporting machine-to-machine communication and expressing facts and relationships betweenthings and about things . 1854.8Explicit link to the GS1 identification key(s) . 204.9Validation principles for GS1 Web URIs . 20GS1 Web URI syntax . 205.1Formal specification . 205.1.1Character sets . 205.1.2Primary identification keys . 225.1.3Key qualifiers . 225.1.4Primary key formats . 235.1.5Key qualifier formats . 245.1.6Primary identifier and value concatenation . 245.1.7Key qualifier concatenation . 245.1.8Path element order . 255.1.9Data attributes . 255.1.10Constructing the URI . 335.2Canonical GS1 Web URIs. 345.3An explanation of Web URI syntax and options for extensions. 355.4Examples of GS1 Web URIs . 365.4.1GTIN . 365.4.2GTIN CPV . 365.4.3GTIN Batch/Lot . 365.4.4GTIN Serial Number (also known as SGTIN). 375.4.5GTIN Batch/Lot Serial Number Expiry Date. 375.4.6GTIN Net Weight . 375.4.7GTIN Typed Link . 385.4.8GTIN Batch/Lot Serial Number Expiry Date Typed Link . 385.4.9SSCC . 395.4.10SSCC with specified Content, Count and Batch/Lot . 395.4.11Physical location represented by a GLN or GLN GLN Extension . 39Release 1.0, Ratified, Aug 2018 2018 GS1 AISBLPage 6 of 54
GS1 Web URI Structure Standard6Resolving GS1 Web URIs . 406.1Resolving Protocol . 406.2Extraction step . 416.3Validation step . 416.46.56.3.1Check the length . 426.3.2Check the character set . 426.3.3Check the GS1 check digit (where appropriate) . 426.3.4Check the internal database of identifiers supported by this resolver . 43Resolution step . 446.4.1A note on HTTP response codes: . 446.4.2When a resolver has only partial information . 44Examples of use . 446.5.1Using the provided domain to call the resolver . 446.5.2Replacing the domain to call an alternative resolver . 456.5.3Retailer operates their own resolver . 466.5.4Smartphone app for nutrition / dietary / allergen information . 476.5.5Product comparison apps . 487Glossary. 488References . 52AIntellectual property . 54Release 1.0, Ratified, Aug 2018 2018 GS1 AISBLPage 7 of 54
GS1 Web URI Structure Standard1Executive overviewGS1 has been strong in product identification for many years - but GS1 identification keys havebeen designed to serve use cases that are primarily driven by the needs of supply chains (andtraditionally are most relevant from manufacturer to checkout). In the 21st century, that’s notenough. As a result of this standard, it will be possible to represent GS1 identification keysconsistently within Web addresses (Web URIs) as well as within the barcodes containing GS1 WebURI, such that a single identification approach will be able to support both product identification forsupply chain applications and a link to online material. It’s this dual functionality and enormousflexibility that is currently not possible when, for example, Brand Owners embed an unstructuredWeb page address in a QR Code .The use of 2D barcodes like ISO/IEC 18004 QR Code or ISO/IEC 16022 DataMatrix ECC 200, inaddition to 1D barcodes on consumer packs, is a core driver of this work. Consumers routinely seekproduct information on the Web, especially via mobile, and manufacturers may respond to thisdemand by adding a second machine readable barcode to the product. For retail products, this isusually a QR Code 1 that encodes the address of a Web page from which product and marketinginformation is available. SmartLabel is a high-profile example of this, where Web addresses (WebURIs) are encoded into QR Codes today with little or no standardised structure. However, we alsoneed publicly available standard references or services that could support the transformation of theGS1 data encoded in the GS1 1D/2D barcode into this standard Web URI syntax. GS1 DataMatrixwithout a URI/URL encoded in the barcode in regulated healthcare is the principle data carrier and isanother driver for this standard, in order to support the GS1 Digital Bridge Service concept.The scope of the work accommodates all Class 1 and Class 2 GS1 Keys and Key qualifiers (e.g.,serial number, batch number, consumer product variant) and other relevant attributes as the sametechnologies are equally applicable to SSCCs, GLNs, GIAIs, GRAIs, GSRNs etc. While the syntax cansupport Class 2 Keys, it is up to the Class 2 Issuing Agencies to determine its fit for their use. ForClass 3 GS1 Keys, GS1 welcomes bilateral discussions with Issuing Agencies to see where alignmentis possible.This GS1 standard references a number of third-party standards from the Internet Engineering TaskForce (IETF) and the World Wide Web Consortium (W3C).2ForewordGS1 defines a wide range of identifiers that underpin the supply chain and retail industry across theworld. This document assumes the reader is familiar with these and the concept of GS1 ApplicationIdentifiers. If not, please see information on [GS1 identification keys] and the [GENSPECS] forfurther background. Readers who are already very familiar with the terms URI, URN and URL, andthe differences between these, can skip section 3.1.This work has been motivated by a number of trends. For example: the desire among retailers tomove to 2D barcodes that can carry more information than just the GTIN; the problems of multiplebarcodes causing scanning errors through conflicts which suggests a need for a single butmultipurpose barcode; the growing expectation among consumers that more information is availableonline about the products they’re considering buying; the brand owner concept of the pack as amedia channel linking to multimedia experiences, and more.Section 3.2 provides a high-level overview of why Web technologies are appropriate to meet theseneeds. However, for this to work fully within the existing GS1 system, it must be possible totranslate between GS1 Web URIs and GS1 element strings such that the two are completelyinterchangeable. Achieving that requires the level of precision in the structure of a GS1 Web URIthat this document provides.Unless otherwise specified, the term ‘QR Code ’ refers to the widely used ISO / IEC 18004 QR Code , not GS1 QRCodes. ‘QR Code’ is a registered trademark of Denso Wave, a subsidiary of Denso Corporation.1Release 1.0, Ratified, Aug 2018 2018 GS1 AISBLPage 8 of 54
GS1 Web URI Structure Standard3Introduction3.1What is a URI?This subsection provides some clarification about what a Uniform Resource Identifier (URI) is, howURIs relate to Uniform Resource Names (URNs) and Uniform Resource Locators (URLs), as well asproviding an explanation of the main structural elements within a Web URI.Figure 3-1 shows a Venn diagram in which we see that Uniform Resource Identifier is the broadterm that includes Uniform Resource Names (URNs) and Uniform Resource Locators (URLs) as wellas URIs with various protocols including http or https, ftp, mailto, tel etc. This means that every URLand every URN is also a URI, since URI is the broader umbrella term. Furthermore, InternationalizedResource Identifiers (IRIs) are an even broader category that support characters from the UniversalCharacter Set / Unicode, whereas URIs only support the ASCII character set. IRIs are defined in[IRIs].Figure 3-1 URNs and URLs are also URIsFigure 3-2 shows another Venn diagram. This time, it shows two capabilities:1. The capability to easily resolve to resources (e.g. information) on the Web.2. The capability to provide a globally unambiguous name for anything, whether or not the thingexists only on the Web or in the real world.The first capability is usually associated with URLs and Web addresses.The second capability is usually associated with URNs.Web URIs exist at the intersection of these two capabilities; in terms of their syntax, they look likeURLs because they specify http or https as their protocol - and they can be configured to behavelike URLs in terms of supporting Web requests via the http / https Web protocol. However, they arealso a perfectly valid way of assigning a globally unambiguous name for anything, whether in thereal world or online. Note that 'globally unambiguous' does not mean globally unique; two
, under its IP Policy, seeks to avoid uncertainty regarding intellectual property claims by requiring the participants in the Work Group that developed this GS1 Web URI Standard to agree to grant to GS1 members a royalty-free licence or a
Foodstuffs GS1 NPC Supplier Guidelines Version 2.2 Page 4 of 28 GS1 PRODUCTFLOW / NPC PROCESSES As a supplier to Foodstuffs you will need to: Register for GS1 ProductFlow and work with GS1 to achieve GS1 Product Flow Certified status. Foodstuffs will then "activate" your company in the Foodstuffs eXchange to be a ProductFlow user.
Jan 16, 2021 · GS1 Digital Link Standard: URI Syntax enabling consistent representation of GS1 identification ke
healthcare industry through local support initiatives like GS1 Healthcare US in the United States. About GS1 Healthcare US GS1 Healthcare US is an industry group that focuses on driving the adoption and implementation of GS1 Standards in the healthcare industry in the United States to help improve patient safety and supply chain efficiency.
industry through local support initiatives like GS1 Healthcare US in the United States. ABOUT GS1 HEALTHCARE US GS1 Healthcare US is an industry group that focuses on driving the adoption and implementation of GS1 Standards in the healthcare industry in the United States to improve patient safety and supply chain efficiency.
GS1 , under its IP Policy, seeks to avoid uncertainty regarding intellectual property claims by requiring the participants in the Work Group that developed this GS1 AIDC Fresh Foods Sold at Point -of-Sale Implementation Guideline to agree to grant to GS1 members a royalty-free licence or a RAND licence to Necessary Claims, as that term is defined in the GS1
the GS1 GTIN Management Rules to ensure the accurate allocation and application of the UDI code. 2 Characters, such as letters and numbers, which can be read by persons and are encoded in GS1 AIDC data carriers confined to a GS1 standard structure and format. The human readable interpretation is a one-to-one illustration of the encoded data.
UDI in GS1 AIDC terms identify 9 The HRI format shall follow the GS1 GTIN Management Standard. Refer to the appropriate UDI regulation and the GS1 GTIN Management Standard for complete details on DI / GTIN change.
National Animal – the tsuru is designated as a Japanese national treasure and is an animal symbol of Japan – like the kangaroo for Australia, . and many more people could now learn to fold paper, including paper cranes. These pictures show two pages from the book, and two ladies with a child folding paper cranes – you can see the small scissors to cut the paper. 4 千羽鶴 Senbazuru .
