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.
This Standard specifies the minimum requirements for telecommunications infrastructure of data centers and computer rooms, including single tenant enterprise data centers and multi-tenant data centers. The topology specified in this document is intended to be applicable to any size data center.
This Technical Report aims to help citizens to understand the relevance of using electronic signature within their day-to-day lives. It also explains the legal and the technical backgrounds of electronic signatures. This document gives guidance on the use of electronic signatures and addresses typical practical questions the citizen may have on how to proceed to electronically sign, where to find the suitable applications and material.
The present Technical Report provides guidance on the selection of standards and options for the signature/seal creation and other related devices (area 2) as identified in the framework for standardization of signatures: overview ETSI/TR 119 000 [16]. The present Technical Report describes the Business Scoping Parameters relevant to this area (see Clause 5) and how the relevant standards and options for this area can be identified given the Business Scoping Parameters (Clause 6). The target audience of this document includes: - business managers who potentially require support from electronic signatures/seals in their business and will find here an explanation of how electronic signatures/seals standards can be used to meet their business needs; - application architects who will find here material that will guide them throughout the process of designing a system that fully and properly satisfies all the business and legal/regulatory requirements specific to electronic signatures/seals, and will gain a better understanding on how to select the appropriate standards to be implemented and/or used; - developers of the systems who will find in this document an understanding of the reasons that lead the systems to be designed as they were, as well as a proper knowledge of the standards that exist in the field and that they need to know in detail for a proper development.
ISO 15118-2:2014 specifies the communication between battery electric vehicles (BEV) or plug-in hybrid electric vehicles (PHEV) and the Electric Vehicle Supply Equipment. The application layer message set defined in ISO 15118-2:2014 is designed to support the energy transfer from an EVSE to an EV. ISO 15118-1 contains additional use case elements describing the bidirectional energy transfer. The implementation of these use cases requires enhancements of the application layer message set defined herein. The purpose of ISO 15118-2:2014 is to detail the communication between an EV (BEV or a PHEV) and an EVSE. Aspects are specified to detect a vehicle in a communication network and enable an Internet Protocol (IP) based communication between EVCC and SECC. ISO 15118-2:2014 defines messages, data model, XML/EXI based data representation format, usage of V2GTP, TLS, TCP and IPv6. In addition, it describes how data link layer services can be accessed from a layer 3 perspective. The Data Link Layer and Physical Layer functionality is described in ISO 15118-3.