Draft: Conformity Assertion Protocol

** DRAFT **

Summary

Adds a new page documenting the proposed UNTP Conformance Assertion Protocol (UCAP) which is a machine-readable mechanism for software providers to declare their UNTP implementation scope and for any verifier to programmatically confirm that declaration against live production APIs.

Assumptions and open dependencies

This page describes a protocol that depends on several artefacts and infrastructure that do not yet exist. This is a document as a design proposal, not a description of implemented capability.

Dependency	Status	Notes
/.well-known/untp-conformance URI	Provisional — noted in-page	Requires IANA registration before the spec can be finalised. The existing /.well-known/resolver is backed by ISO/IEC 18975; this URI has no such backing yet.
JSON-LD context https://vocabulary.uncefact.org/untp/conformance/v1	Does not exist	Defines new VC types (UNTPConformanceAssertion, UNTPConformanceTestReport) and all CAD/CTR fields. Needs authoring and hosting.
test-suite.uncefact.org manifest service	Does not exist	The page assumes UN/CEFACT will host versioned test suite manifests at canonical URLs under this domain.
Test manifest DSL (assertion types, URL templating, severity model)	Designed in this page only	The declarative test format (httpStatus, jsonSchema, jsonPath, header assertions with urlTemplate variable binding) is specified here for the first time. It has no formal spec or reference implementation.
uncefact/ucap-action@v1 and uncefact/ucap-publish-action@v1 GitHub Actions	Do not exist	Referenced in the CI/CD section as available tooling. The open-source UCAP verifier CLI is also mentioned but not yet built.
BitstringStatusList infrastructure for CTR revocation	Not operational	The CTR examples include a credentialStatus block assuming the registrar operates W3C BitstringStatusList revocation infrastructure.

did:web:registrar.uncefact.org is already established in the implementation governance page and is not a new assumption.