Add a worked facility-resolution example (current examples are all product-based)

Impacted Sections

https://untp.unece.org/docs/specification/IdentityResolver/

idr-api.json (resolution path + IDR-02)

Issue Description

The resolver supports facilities in principle, but every worked example is product-based — leaving the facility path underspecified.

The spec names three entity types — businesses, locations (facilities), and products — and defines a dfr link relation for resolving a facility identifier to a Digital Facility Record, with facility-identifier URL examples (e.g. https://facilities-register.example/ABC123456). So facilities are in scope by design, and serial/batch qualifiers are optional. However, the requirement language (IDR-02 is framed around “a data carrier on a physical product or asset”), the OpenAPI samples, and every end-to-end walkthrough are product/GS1-centric (GTINs, serial and batch numbers). There is no worked facility example. As a committed Identity Resolver for FACILITY identifiers, OS Hub has no concrete facility-resolution pattern to build against, and it is unclear whether facility resolution is meant to reuse the product path as-is (minus qualifiers) or follow different conventions.

I Have

Provide a worked FACILITY example showing how a facility-only register resolves an identifier to a DFR using the dfr link relation — without product carriers or qualifier paths — and add facility-oriented resolver guidance alongside the existing product guidance.

• [WG-Adoption, WG-SupplyChain ]