Generated from the main-branch git history. Every commit gets surfaced here as soon as it lands in production. Subscribe via the RSS feed.
Resolution of a public passport no longer requires an API key. Requiring a credential to be told where a public passport lives defeats the point of publishing one. Ownership scoping is unchanged: a caller still sees only public records plus their own.
The public conformance statement was rewritten after reading the normative texts rather than summaries of them. The harmonised family is eight standards, not six. Two claims that were wrong are gone: one standard specifies no retention period at all, and another does not reference the Asset Administration Shell normatively anywhere. A statement that overclaims is worse than one that says less.
Passports can now carry the IDTA-02099-1 DPP metadata submodel, whose fields correspond to the common information model in EN 18223. Granularity, facility and registry identifiers are stored as real fields rather than free text, so they can be queried instead of parsed.
The relation names used to type our links were checked against the GS1 Web Vocabulary rather than assumed. Two of them did not exist in any vocabulary and have been replaced with the defined terms. A link typed with an invented relation is not interoperable, however well-formed it looks.
A public endpoint now answers with an RFC 9264 link set: given only a product's unique identifier, a resolver is told where the passport lives and what else is published about it, without needing an account. A withdrawn identifier answers with the withdrawal rather than silence, so a client can tell 'retired' apart from 'never existed'.
A pointer must be an HTTPS URL that carries no embedded credentials before it can be registered, and a pointer that answers with an authorisation error is refused. A pointer that simply cannot be reached is accepted: an endpoint being temporarily down is not the same as it being wrong.
Navigate + run actions