ISO/IEC 18384-3:2016 defines a formal ontology for service-oriented architecture (SOA), an architectural style that supports service orientation. The terms defined in this ontology are key terms from the vocabulary in ISO/IEC 18384-1.
This document specifies the metamodel that provides a facility to register administrative and evolution information related to ontologies. The metamodel is intended to promote interoperability among application systems, by providing administrative and evolution information related to ontologies, accompanied with standardized ontology repositories that register ontologies themselves in specific languages. This document does not specify the metamodels of ontologies expressed in specific languages and the mappings among them.
The present document will provide a comparison between both internal and external 'cloud-based' solutions with a life cycle analysis addressing: aenergy consumption; b)green-house gas (GHG) emission; c)water consumption; d)waste management from production to end-of-life management.
The present document replaces TS 103463 and defines in greater detail a number of Key Performance Indicators (KPIs) for Smart Areas (both urban and rural) expressing sustainability performance in terms of People, Planet, Prosperity and Governance. Certain of the KPIs are grouped and presented as Global KPIs in TS 103 463-2.
This document outlines the concepts and principles for information management at a stage of maturity described as "building information modelling (BIM) according to the ISO 19650 series". This document provides recommendations for a framework to manage information including exchanging, recording, versioning and organizing for all actors. This document is applicable to the whole life cycle of any built asset, including strategic planning, initial design, engineering, development, documentation and construction, day-to-day operation, maintenance, refurbishment, repair and end-of-life. This document can be adapted to assets or projects of any scale and complexity, so as not to hamper the flexibility and versatility that characterize the large range of potential procurement strategies and so as to address the cost of implementing this document.
This part of ISO 9735 specifies syntax rules for EDIFACT security. It provides a method to address message/package level, group level and interchange level security for authenticity, integrity and non-repudiation of origin, in accordance with established security mechanisms.
This document gives guidelines for performance criteria and an evaluation methodology for authentication solutions that aim to unambiguously establish material good authenticity and integrity throughout an entire material good's life cycle. It focuses on the authentication of a material good and, if appropriate, its components, parts and related data:
— covered by intellectual property rights;
— covered by relevant international, regional or national regulations;
— with counterfeiting-related implications;
— otherwise with a distinctive identity.
This document is applicable to all types and sizes of organizations that require the ability to validate the authenticity and integrity of material goods. It will help organizations to determine the categories of authentication elements they need in order to combat counterfeiting-related risks, and the criteria for selecting authentication elements, after having undertaken a counterfeiting risk assessment.
Authentication solutions can be used in areas such as anti-counterfeiting, prevention of product fraud and prevention of diversion.
This document does not specify economic criteria aiming to correlate performance and costs of the authentication solutions.
This document gives guidelines for establishing interoperability among independently functioning product identification and related authentication systems, as described in ISO 16678. The permanent transfer of data from one system to another is out of the scope of this document.
It also gives guidance on how to specify an environment open to existing or new methods of identification and authentication of objects, and which is accessible for legacy systems that may need to remain active.
It is applicable to any industry, stakeholder or user group requiring object identification and authentication systems. It can be used on a global scale, or in limited environments. This document supports those involved in planning and establishing interoperation.
This document specifies three business requirements for the visibility of logistics traffic flow based on the use cases and gap analysis in Annex A. It includes
1) LISS network architecture requirements,
2) visibility data interchange requirements between LISSs, and
3) visibility data interface and process requirements for an LISS network.
These three business requirements are described further in Clause 6, Clause 7 and Clause 8 respectively.
Furthermore, Clause 8 describes the requirement for a guideline for business participants and stakeholders in an LISS network such as logistics information service providers, single window/SSP operators, data providers and logistics data users.
This document does not include standardization
1) at the level of logistics devices (areas of standardisation covered by ISO/TC 104, ISO/TC 204),
2) for ships, navigation and marine technologies (areas of standardisation covered by ISO/TC 8), or
3) related to international data exchange such as standards developed, published and maintained by UN/CEFACT, GS1, WCO which are referenced as appropriate in this document.
ISO 14533-3:2017 specifies the elements, among those defined in PDF Advanced Electronic Signatures (PAdES), that enable verification of a digital signature over a long period of time.
It does not give new technical specifications about the digital signature itself, nor new restrictions of usage of the technical specifications about the digital signatures which already exist.
This document establishes a framework for identification and authentication systems. It provides recommendations and best practice that include:
— management and verification of identifiers;
— physical representation of identifiers;
— participants’ due diligence;
— vetting of all participants within the system;
— relationship between the unique identifier (UID) and possible authentication elements related to it;
— questions that deal with the identification of the inspector and any authorized access to privileged information about the object;
— inspector access history (logs).
The model described in this document is intended to determine the common functions of different systems.
This document describes processes, functions and functional units of a generic model. It does not specify any specific technical solutions.
Object identification systems can incorporate other functions and features such as supply chain traceability, quality traceability, marketing activities and others, but these aspects are out of scope of this document.
NOTE This document does not refer to industry-specific requirements such as GS1 Global Trade Item Number (GTIN).
This document specifies the elements, among those defined in XAdES digital signatures, that enable verification of a digital signature over a long period of time.
It does not give new technical specifications about the digital signature itself, nor new restrictions of usage of the technical specifications about the digital signatures which already exist.
NOTE XAdES digital signatures is the widely-used extended specification of “XML-Signature Syntax and Processing”.