A technical specification that defines an API and corresponding OAuth 2.0-based authorization mechanisms for the issuance of W3C Verifiable Credentials.
Alternative protocol to exchange verifiable credentials between supply chain actors.
The Supply Chain Reference Data Model (SCRDM) Business Requirement Specification (SCRDM BRS), in combination with the UN/CEFACT business process International Supply Chain Reference Model (ISCRM) and the BRS for the Multi-Modal Transport Reference Data Model (MMT RDM-BRS), provides the framework for any cross-border transport-related business and government domains to specify their own specific information exchange requirements whilst complying with the overall process and data structures.
A JSON Schema / JSON-LD reference data model, being a subset of the Buy-Ship-Pay Reference Data Model (part of the UN Core Component Library) with a specific focus on Sustainable Development and Circular Economy (SDCE).
This specification defines a business‐oriented artefact either referencing (as a header) or containing (as an envelope) a payload of one or more business documents or other artefacts with supplemental semantic information about the collection of payloads as a whole. This is distinct from any transport‐ layer infrastructure header or envelope.
A use case for a data structure to support the reuse and recycle stages of the value chains through a digital representation and exchange of circular product data.
The UN/LOCODE, in full: United Nations Code for Trade and Transport Locations, is an international five-letter code for places in countries around the world, which replaces the full place name. Currently, UN/LOCODE includes over 103034 locations in 249 countries and territories and it is widely used in the transport industry.
A list of all code sets associated with coded data elements, see also UNECE Code List recommendations.
The UN Core Component Library (CCL) is a library of business semantics in a data model which is harmonised, audited and published by UN/CEFACT. The CCL uses Core component Technical Specifications (CCTS) to ensure consistency and interoperability.
The OpenAPI Naming and Design Rules technical specification defines an architecture and a set of rules necessary to specify, describe and implement APIs based on an OpenAPI specification to consistently express business information.
The JSON Schema Naming and Design Rules technical specification defines an architecture and a set of rules necessary to define, describe and use JSON to consistently express business information exchanges namely via APIs
The UN/CEFACT Core Components Technical Specification describes and specifies a new approach to the well-understood problem of the lack of information interoperability between applications in the e-business arena.