The GS1-Conformant Resolver standard defines how a GS1 Digital Link URI carrying a product or location key, such as a GTIN or GLN, resolves to the information sources related to it, including how a resolver responds to bad requests.
GS1-Conformant Resolver Standard
The GS1-Conformant Resolver standard defines how a GS1 Digital Link URI carrying a product or location key, such as a GTIN or GLN, resolves to the information sources related to it, including how a resolver responds to bad requests.
Where it stands
As of 2026-10-13, the Agentic Standards Map records:
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”.
Why it matters to agents
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). …
Sources
- https://ref.gs1.org/standards/resolver/
- https://ref.gs1.org/standards/resolver/1.2.1/GS1_Conformant_Resolver_standard_i1.2.1-r-2026-08-07
- https://ref.gs1.org/standards/resolver/archive
Status and relevance quoted, shortened, from the Agentic Standards Map by Francesco Marinoni Moretto, CC BY 4.0, https://frmoretto.github.io/agentic-standards-map/. The full entry, with every dated source, is in map.json under gs1-conformant-resolver.
Industry: logistics
Related standards
Standards this one builds on, supersedes, profiles or is commonly deployed beside.
