ISO

This document represents an open international standard for information used in Building Information Modeling (BIM) that is exchanged and shared among software applications used by the various participants in the construction or facility management industry sector. This document includes definitions that cover information required for buildings and infrastructure works over their life cycle. This edition of the document added coverage of information required for infrastructure facilities including bridges, roads, railways, waterways and port facilities.

This document comprises the publication of a data schema, its documentation, the property and quantity set definitions and the mechanism of an exchange file format structure.

Definitions from this document are used to support different recognized work flows in the construction and facility management industry sector, representing information deliveries. Such information deliveries can be described according to ISO 29481.

Different implementation levels of this document can be defined to better support multiple information deliveries, they are referred to as a Model View Definition (MVD). Each MVD identifies which subset of the definitions of this document imposes requirements for implementation in software applications. Conforming software applications need to identify the model view definition they conform to when applying for software certification.

The following are within the scope of this edition of this document:

1. BIM exchange format definitions that are required during the life cycle phases of buildings and infrastructure:
   • demonstrating the need;
   • conception of need;
   • outline feasibility;
   • substantive feasibility study and outline financial authority;
   • outline conceptual design;
   • full conceptual design;
   • coordinated design;
   • procurement and full financial authority;
   • production information;
   • construction;
   • operation and maintenance.
2. BIM exchange format definitions that are required by the various disciplines involved within the life cycle phases:
   • architecture and civil engineering design;
   • service and utilities engineering;
   • structural engineering;
   • procurement;
   • construction planning;
   • facility and utility management;
   • project management;
   • client requirement management;
   • industry authorities for permits and approval.
3. BIM exchange format definitions including:
   • project structure;
   • physical components;
   • spatial components;
   • analysis items;
   • processes;
   • resources;
   • controls;
   • actors;
   • context definition.

The standard specifies a data model in UML and a derived XML schema (XSD) for defining the Level of Information Need in software applications based on concepts and principles given in Part 1, and guidance given in Part 2, in compliance with the principles and data exchange standards of data templates (ISO 23387). The standard defines the exchange format schema in XSD according to the UML schema and it gives guidelines for the usage and application of the schema. In addition, the integration with Linked Data principles and paradigms will be demonstrated.

This document provides an overview of synthetic data concepts, methods, uses and considerations in the context of AI systems.

This document defines a framework for blockchain-enabled micro-credentials supporting workforce development, lifelong learning, and skills portability. It specifies:

• DLT Trust and Governance Infrastructure for credential issuance, verification, and lifecycle management;

• interoperability of Learning outcomes Credential Representation across platforms, sectors, and skills and occupation taxonomies (e.g. ESCO, O’NET, etc);

• alignment with decentralized identity and verifiable credential standards (e.g. W3C Verifiable Credentials and DIDs);

• semantic interoperability through linkage with reference models for lifecycle processes including issuance, update, revocation, expiry, and stacking of micro-credentials;

• Audit trail DLT based of Learning process and records.

Distributed Ledger Technologies can provide governance evidence infrastructures supporting transparency, auditability, accountability and trust across workforce credential ecosystems.

This document defines a process for reviewing and analyzing smart contract code. It specifies supporting methods to allow identification and mitigation of smart contract security vulnerabilities.

ISO Technical Specifications for Taxonomy and Classification for Smart Contracts. 

This document provides an overview of DLT-based collections of physical and digital items as well as collections management. This document discusses implementation considerations regarding DLT-based collections and collections management.

This document specifies tokenization methods in distributed ledger technologies (DLTs), including private DLTs, public permissioned DLTs, and public permissionless DLTs. It defines methodological requirements for tokenization and identifies the governance impacts, benefits, challenges and representative use cases associated with each DLT type. The scope is strictly limited to methodological aspects. It does not prescribe lifecycle models, asset taxonomies or jurisdiction-specific regulatory frameworks. Instead, it sets out governance-neutral criteria that enable tokenization to be secure, reliable, scalable and aligned with sustainability across diverse deployment contexts. This document provides a foundational, interoperable framework intended to support industry, regulators and technical committees, and to facilitate future collaboration and sector-specific adaptations.

This document provides a vocabulary for digital currencies (central bank digital currencies and non-fiat digital currencies)

This document specifies a taxonomy and an ontology for blockchain and distributed ledger technologies (DLT). The taxonomy includes a taxonomy of concepts, a taxonomy of DLT systems and a taxonomy of application domains, purposes and economy activity sections for use cases. The ontology includes classes and attributes as well as relations between concepts. The audience includes but is not limited to academics, architects, customers, users, tool developers, regulators, auditors and standards development organizations.