Missing top-level credential types in the UNTP v0.7.0 JSON-LD context

The UNTP v0.7.0 JSON-LD context (https://vocabulary.uncefact.org/untp/0.7.0/context/) does not define any of the top-level credential types that credentials are expected to declare in their type array: DigitalProductPassport, DigitalConformityCredential, DigitalFacilityRecord, DigitalIdentityAnchor, or DigitalTraceabilityEvent.

The specification documents each of these as a distinct credential type that appears in the JSON-LD type array alongside VerifiableCredential (e.g. "type": ["VerifiableCredential", "DigitalProductPassport"]), but none of them are mapped in the context. A credential that declares one of these types will have the type dropped during JSON-LD expansion because it cannot resolve to an absolute IRI. This breaks downstream consumers that rely on expanded JSON-LD to identify the credential type, and makes it impossible to validate that a credential has been correctly typed according to the UNTP specification.

Can we add mappings for each of the five top-level credential types to the v0.7.0 context file so that credentials conforming to the published specification can be expanded?