GS1-Conformant Resolver Standard 1.2.1
GS1specificationcore entry
Verified 2026-10-13. Status as of 2026-10-13. All entries.
Seams: S2
Status
Release 1.2.1 ratified August 2026 (standards page and PDF print no day); the archive page on ref.gs1.org lists "Published 19 August 2026".
Relevance
The standard defines how a GS1 Digital Link URI, which carries a product or location key such as a GTIN or a Global Location Number (GLN), is resolved to related information sources. The query string "carries attributes of the identified entity and does not form part of the entity's identifier"; for an invalid request URI "the resolver SHALL respond with an HTTP response code of 400 (Bad Request)", and for a valid URI with no information it "SHALL return a simple 404 Not Found response" (sections 2.12, 2.4.1).
A conformant resolver publishes a Resolver Description File at /.well-known/gs1resolver.
Committed next
None declared in the sources read.
Boundary
Out of scope: identical targets or linksets across resolvers, and any particular behaviour for query string parameters.
Sources
- https://ref.gs1.org/standards/resolver/ normative text, read 2026-10-13 · archived
- https://ref.gs1.org/standards/resolver/1.2.1/GS1_Conformant_Resolver_standard_i1.2.1-r-2026-08-07 normative text, read 2026-10-03 · archived
- https://ref.gs1.org/standards/resolver/archive official decision or commitment, read 2026-10-13 · archived
Overlaps
W3C DID Resolution, UN Transparency Protocol, Identity Resolver, GS1 Digital Link Standard, URI Syntax 1.7.0
Neighbours in the map
Solid lines: overlaps declared by one of the two entries. Dashed lines, coloured by seam: entries named by the same seam (S1 to S4) in the seams note. Every node is a link.
Evidence and coverage
- Read
- Standards page, PDF (text extracted) and archive page of the Resolver, in full, 2026-10-03; for dates also the URI Syntax standard page and archive.
- Not read
- The www.gs1.org standards page.