FprEN ISO 21597-2

SLOVENSKI STANDARD
oSIST prEN ISO 21597-2:2018
01-november-2018

,LQIRUPDFLMVNLYVHEQLN]DL]URþLWHYSRGDWNRY6SHFLILNDFLMD]DL]PHQMDYRGHO

Information container for data drop - Exchange specification - Part 2: Dynamic semantics

d'information pour extraction de données (ICDD) - Partie 2: Titre manque (ISO/DIS

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may

be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting

on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address

below or ISO’s member body in the country of the requester. A.5 Use case 2D – Deliver GML representations 44

ISO (the International Organization for Standardization) is a worldwide federation of national

standards bodies (ISO member bodies). The work of preparing International Standards is

normally carried out through ISO technical committees. Each member body interested in a

subject for which a technical committee has been established has the right to be represented on

that committee. International organizations, governmental and non-governmental, in liaison

with ISO, also take part in the work. ISO collaborates closely with the International

Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.

The procedures used to develop this document and those intended for its further maintenance

are described in the ISO/IEC Directives, Part 1. In particular the different approval criteria

needed for the different types of ISO documents should be noted. This document was drafted in

Attention is drawn to the possibility that some of the elements of this document may be the

subject of patent rights. ISO shall not be held responsible for identifying any or all such patent

rights. Details of any patent rights identified during the development of the document will be in

Any trade name used in this document is information given for the convenience of users and

For an explanation on the meaning of ISO specific terms and expressions related to conformity

assessment, as well as information about ISO’s adherence to the World Trade Organization

This document was prepared by Technical Committee ISO/TC 59, Buildings and civil engineering

works, Subcommittee SC 13, Organization and digitization of information about buildings and civil

ISO 21597 consists of the following parts, under the general title Information Container for Data

This document has been developed in response to the need of the Construction industry to

handle multiple documents and structured data as one integrated information delivery.

In Part 1 of this standard, a specification is given for a container supporting the storage of

Part 2 adds the ability to include user-defined schemas (i.e. data models) that capture the

semantics of, for example, national or organization-specific standards. This facilitates

streamlined data exchange according to these schemas using linked data principles.

The ability to enrich the data contributes significantly to the value of the container, allowing the

formalization of data exchanges in the construction sector. For example, users are enabled to

This Part 2 of the ICDD standard adds functionality to the container format specified in Part 1.

Part 1 defines a generic container format to store documents using various formats and

structure and the ability to provide links between documents or between referable subsets of

these documents (documents and datasets are the payload of the container). Building on that

foundation, Part 2 of this standard adds the possibility of adding more semantic (meaningful)

information to the contents of the container, as well as to the links between pieces of

This standard does not prescribe the structure or format of the documents in the payload.

This standard is suitable for industry sectors such as the built environment, where many

different standards are used, where there is a mixture of digital representations of proposed or

existing built and natural assets (in open or proprietary formats), requiring the use of legacy

systems and the application of different classification systems. This part adds the ability to link,

in a semantic and meaningful way, those islands of data represented using different formats and

structure. This standard is not meant to replace other standards such as ISO 16739 which is

This standard provides two conformance classes. Both conformance classes open the ability to

In Conformance Class A, the container format of Part 1 is expanded with an ontology dynamic

semantics, providing basic support for creating an information model that captures the required

semantics of project, organization or sector standards and agreements. By doing so, it provides

building blocks that make it easier to link different sources of information. This is achieved by

introducing support for typed entities, typed entity properties and typed relationships between

those entities (such as the relationship between an assembly and its parts or between a physical

entity and its associated requirements). There is also support for defining provenance,

In Conformance Class B, the user is offered complete freedom to add user defined ontologies to

The use cases are in line with those of Part 1, but may include numerous extensions. The

1. Make use of asset type libraries describing the required properties per asset type

2. Link to a specific classification system, e.g. CoClass, Uniclass or OmniClass™

5. Add semantic links (i.e. meaningful links) to and between information provided using

Since this standard capitalizes on Linked Open Data technology, the header file, along with any

additional RDF/OWL files, forms a suite that may be directly queried by software using standard

The following documents are referred to in the text in such a way that some or all of their

content constitutes requirements of this document. For dated references, only the edition cited

applies. For undated references, the latest edition of the referenced document (including any

ISO/IEC 21320-1:2015, Information technology — Document Container File — Part 1: Core

ISO 6707-1, Buildings and civil engineering works — Vocabulary — Part 1: General terms

W3C OWL, Web Ontology Language, https://www.w3.org/TR/2012/REC-owl2-syntax-20121211/

In addition to the terms and definitions given in ISO 21597-1, for the purposes of this document,

ISO and IEC maintain terminological databases for use in standardization at the following

RDF/OWL file providing the object classes and properties that shall be used to specify a user-

physical, digital, conceptual, or other kind of thing (either real or imaginary) with some fixed

formal model of a bounded set of facts, concepts or instructions to meet a specified requirement

ontology that adds more semantic (meaningful) information to the contents of the container

In addition to the abbreviated terms given in ISO 21597-1, for the purposes of this document,

The ontologies specified in this standard use the languages RDF [https://www.w3.org/RDF/],

NOTE: It is expected that RDF/OWL will be an important technology and a general platform for Ontologies

In general, when used in the context of the world wide web, these languages use the following

- Open world assumption - the truth of a statement is independent of whether it is known.

In other words, not knowing that a statement is explicitly true does not imply that the

- No unique names assumption - unless explicitly stated otherwise, it cannot be assumed

The datasets that comply with the ontologies specified in this standard shall use the following

- Closed world assumption - a statement that is true is also known to be true; therefore,

- Unique naming assumption - resources in a container that are identified with different

URIs are considered to be different, unless explicitly declared as the same (using the

Table 1 in ISO 21597-1 (section 4.1) lists the RDF/OWL constructs that are used in this standard

and the interpretation to be used when validating the contents of a container. It is noted that,

once the content of the container has been validated, the data can be used in an open world

Throughout this standard, the structure of the ontologies is illustrated using a UML notation as

In addition to the namespaces listed in ISO 21597-1, Table 1 lists the namespaces and

This standard distinguishes two conformance classes, A and B. Both conformance classes offer

the possibility to add more semantics to the contents of the container by means of the addition

In Conformance Class A, the container format of Part 1 is expanded with an ontology named

DynamicSemantics.rdf. Any UDO added to the container shall be an extension based on

DynamicSemantics.rdf, meaning that any additional class or property shall be a subclass or

subproperty of the classes and properties defined in that ontology. A few examples of such

In Conformance Class B, any UDO may be added to the container. There is no requirement to use

the dynamic semantics ontology. The sole condition is that UDOs shall be expressed in

The structure of the container shall be the same as that of a Part 1 container. Figure 1 shows the

In Conformance Class A, the container format of Part 1 is expanded with an ontology named

DynamicSemantics.rdf. It shall be included in the ‘Ontology resources’ folder. Users may also add

In Conformance Class B, the DynamicSemantics.rdf ontology may be present in the ‘Ontology

For both conformance classes, UDOs shall be stored in the ‘Ontology resources’ folder.

Figure 2 shows the minimum content of the ‘Ontology resources’ folder of a Part 2 container in

Figure 2 - Minimum content of the Ontology resources folder for Conformance Class A

For Conformance Class A, the container format of Part 1 is expanded with an ontology named

DynamicSemantics.rdf. It provides a few basic classes and properties that are very common for

the construction domain. In this way, a foundation is provided for semantic interoperability

Table 2 provides an overview and rationale for the contents of DynamicSematics.rdf.

Metadata ds:Concept is introduced as a subclass of ds:DynamicSemantics and is the root

Tables 3, 4 and 5 list the objects, datatype properties and object properties respectively that are

ds:Assembly a class denoting that individuals of this class can belong to an Assembly-Part

ds:BooleanProperty a ds:BooleanProperty is a subtype of a ds:SimpleProperty where the

ds:ComplexProperty a ds:ComplexProperty can be used to relate to a ds:ComplexPropertyValue that

contains more complex content than a ds:SimpleProperty, while still behaving as a

property of a ds:Concept. An individual of the class ds:ComplexProperty refers to

ds:ComplexPropertyValue entities can be connected to ds:ComplexPropertyValue via a ds:ComplexProperty;

contains the actual content of this property; this can comprise of a ds:Entity with

ds:DynamicSemantics a superclass for all ICCD dynamic semantics classes; this class is without any

ds:Connection connection between individuals of the class ds:Entity only, since the

ds:ContainsRelation a ds:ContainsRelation is a subtype of ds:Relation that is connected to exactly 1

ds:ContainsRelationGroup a ds:ContainsRelationGroup allows the grouping of ds:ContainsRelations enabling

to distinguish multiple ds:ContainsRelation sets; this forms the basis for advanced

ds:DateTimeProperty a ds:DateTimeProperty is a subtype of a ds:SimpleProperty where the

ds:DirectedConnection a directed connection is a subtype of ds:Connection and connects 2 ds:Entity

ds:Concept abstract class (when the owl:UnionClass is interpreted as a constraint) that is the

basis for classes such as ds:Entity, ds:AbstractProperty, ds:Part/ds:Assembly and

ds:AbstractProperty an abstract Class (when owl:UnionClass is interpreted as a constraint) for

ds:ComplexProperty and ds:SimpleProperty; ds:AbstractProperty shall have at least

ds:ExpiredConcept Defines individuals that are expired; individuals of class ds:Concept can be made a

ds:FloatProperty a ds:FloatProperty is a subtype of a ds:SimpleProperty where the ds:datatypeValue

ds:IntegerProperty a ds:IntegerProperty is a subtype of a ds:SimpleProperty where the

ds:NumericProperty an abstract property (when owl:UnionClass is interpreted as a constraint) for

ds:AbstractProperty; a ds:Entity is a physical, digital, conceptual, or other kind of

ds:Relation a abstract class for adding relationships between instances of ds:Concept

ds:SimpleProperty a generic class for all simple properties; an individual of class ds:SimpleProperty

ds:StringProperty a ds:StringProperty is a subtype of ds:SimpleProperty where the ds:datatypeValue

ds:UriProperty a ds:UriProperty is a subtype of ds:SimpleProperty where the ds:datatypeValue is

ds:datatypeValue ds:datatypeValue holds the content for an individual of class ds:SimpleProperty

ds:belongsToAssembly a property connecting a ds:ContainsRelationGroup to a ds:Assembly

ds:fromEntity a subproperty of ds:HasConnectedEntities to denote a direction; ds:fromEntity

ds:groupedBy a ds:ContainsRelation can be grouped via a ds:ContainsRelationGroup; this

property is used to relate the ds:ContainsRelation to the ds:ContainsRelationGroup

ds:hasAssembly ds:hasAssembly is a sub property of ds:hasConnectedEntities and relates an

ds:hasConnectedEntities ds:hasConnectedEntities relates any ds:Concept to a ds:Relation

ds:hasContainsRelation ds:hasContainsRelations relates a ds:ContainsRelation to a ds:Assembly; it is the

ds:hasIncomingConnections ds:hasIncomingConnections is a sub property of ds:hasConnections and relates a