Please note that this specification is suitable for pre-production pilot implementations.
Use Cases
Use cases explain UNTP through real-world scenarios, rather than the point-by-point reference in the technical specifications. Each one follows a business through a problem and shows how the UNTP credentials and discovery mechanisms fit together, usually touching several specifications and roles at once.
Use cases are illustrative, not normative. Where a use case and a specification appear to disagree, the specification is authoritative.
How to read a use case
Every use case opens with an "at a glance" block that lists:
- Specifications touched — links to the UNTP specifications the story relies on.
- Roles — the actors in the story and the part each one plays (issuer, holder, verifier, registrar, auditor, and so on).
- Sample credentials — links to worked example artefacts where they exist.
The body then tells the story in plain language, usually as a sequence of stages, with a diagram of how the credentials and identifiers connect.
Scenario catalogue
| Use case | Specifications touched | Primary roles |
|---|---|---|
| Discovery | DFR, DPP, DIA, Identity Resolver, DCC | Facility operator, Software provider, Registers and resolvers, Auditors, Business register, Data consumers |
New use cases are added over time. Each specification page also links back to the use cases that exercise it, so you can move between the two views in either direction.
Contributing a use case
Copy _template.md in this folder, fill in the "at a glance" block and the narrative, add a row to the catalogue table above, and open a merge request. Keep the story concrete: name the actors, state the business outcome, and link to the specifications rather than restating them.
For sample artefacts, link to the normative samples under artefacts/samples/ for any standard credential, and add only scenario-specific glue (resolver responses, link entries) under artefacts/use-case-samples/<scenario>/. That folder is illustrative and non-normative; it is not part of conformance testing.