SIST EN ISO 21597-2:2021
(Main)Information container for linked document delivery - Exchange specification - Part 2: Link types (ISO 21597-2:2020)
Information container for linked document delivery - Exchange specification - Part 2: Link types (ISO 21597-2:2020)
This document provides the opportunity to add information about the contents of a container by further
specializing the generic types of links specified in ISO 21597-1. The defined link types have been chosen
to enhance the use of the container by allowing the addition of semantic relationships that are human
interpretable to provide greater clarity about those links.
Informationscontainer zur Datenübergabe - Austausch-Spezifikation - Teil 2: Dynamische Semantik (ISO 21597-2:2020)
Dieses Dokument bietet die Möglichkeit, Informationen über die Inhalte eines Containers durch weitere Spezialisierung der in ISO 21597 1 festgelegten generischen Typen von Links hinzuzufügen. Die festgelegten Linktypen wurden ausgewählt, um die Verwendung des Containers zu verbessern, indem die Ergänzung semantischer von Menschen auswertbarer Beziehungen ermöglicht wird, um eine größere Klarheit über diese Links zu erhalten.
Organisation de l'information concernant les travaux de construction - Conteneur d'information pour extraction de données (ICDD) - Partie 2: Titre manque (ISO 21597-2:2020)
Le présent document offre l'opportunité d'ajouter des informations relatives au contenu d'un conteneur au moyen d'une spécialisation supplémentaire des types de liens génériques définis dans l'ISO 21597-1. Les types de liens définis ont été choisis pour améliorer l'utilisation du conteneur en permettant d'ajouter des relations sémantiques qui peuvent être interprétées par l'humain afin de donner une plus grande clarté à ces liens.
Informacijski vsebnik za izročitev povezanih dokumentov - Specifikacija za izmenjavo - 2. del: Vrste povezav (ISO 21597-2:2020)
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
SIST EN ISO 21597-2:2021
01-februar-2021
Informacijski vsebnik za izročitev povezanih dokumentov - Specifikacija za
izmenjavo - 2. del: Vrste povezav (ISO 21597-2:2020)
Information container for linked document delivery - Exchange specification - Part 2: Link
types (ISO 21597-2:2020)
Informationscontainer zur Datenübergabe - Austausch-Spezifikation - Teil 2: Dynamische
Semantik (ISO 21597-2:2020)
Organisation de l'information concernant les travaux de construction - Conteneur
d'information pour extraction de données (ICDD) - Partie 2: Titre manque (ISO 21597-
2:2020)
Ta slovenski standard je istoveten z: EN ISO 21597-2:2020
ICS:
35.240.67 Uporabniške rešitve IT v IT applications in building
gradbeništvu and construction industry
91.010.01 Gradbeništvo na splošno Construction industry in
general
SIST EN ISO 21597-2:2021 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST EN ISO 21597-2:2021
---------------------- Page: 2 ----------------------
SIST EN ISO 21597-2:2021
EN ISO 21597-2
EUROPEAN STANDARD
NORME EUROPÉENNE
November 2020
EUROPÄISCHE NORM
ICS 35.240.67; 91.010.01
English Version
Information container for linked document delivery -
Exchange specification - Part 2: Link types (ISO 21597-
2:2020)
Conteneur d'informations pour la livraison de Informationscontainer zur Datenübergabe - Austausch-
documents liés - Spécification d'échange - Partie 2: Spezifikation - Teil 2: Dynamische Semantik (ISO
Types de liens (ISO 21597-2:2020) 21597-2:2020)
This European Standard was approved by CEN on 14 November 2020.
CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this
European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references
concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN
member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by
translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC Management
Centre has the same status as the official versions.
CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway,
Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and
United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION
EUROPÄISCHES KOMITEE FÜR NORMUNG
CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2020 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN ISO 21597-2:2020 E
worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
SIST EN ISO 21597-2:2021
EN ISO 21597-2:2020 (E)
Contents Page
European foreword . 3
2
---------------------- Page: 4 ----------------------
SIST EN ISO 21597-2:2021
EN ISO 21597-2:2020 (E)
European foreword
This document (EN ISO 21597-2:2020) has been prepared by Technical Committee ISO/TC 59
"Buildings and civil engineering works" in collaboration with Technical Committee CEN/TC 442
“Building Information Modelling (BIM)” the secretariat of which is held by SN.
This European Standard shall be given the status of a national standard, either by publication of an
identical text or by endorsement, at the latest by May 2021, and conflicting national standards shall be
withdrawn at the latest by May 2021.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CEN shall not be held responsible for identifying any or all such patent rights.
According to the CEN-CENELEC Internal Regulations, the national standards organizations of the
following countries are bound to implement this European Standard: Austria, Belgium, Bulgaria,
Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland,
Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Republic of
North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the
United Kingdom.
Endorsement notice
The text of ISO 21597-2:2020 has been approved by CEN as EN ISO 21597-2:2020 without any
modification.
3
---------------------- Page: 5 ----------------------
SIST EN ISO 21597-2:2021
---------------------- Page: 6 ----------------------
SIST EN ISO 21597-2:2021
INTERNATIONAL ISO
STANDARD 21597-2
First edition
2020-11
Information container for linked
document delivery — Exchange
specification —
Part 2:
Link types
Conteneur d'informations pour la livraison de documents liés —
Spécification d'échange —
Partie 2: Types de liens
Reference number
ISO 21597-2:2020(E)
©
ISO 2020
---------------------- Page: 7 ----------------------
SIST EN ISO 21597-2:2021
ISO 21597-2:2020(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO 2020
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.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO 2020 – All rights reserved
---------------------- Page: 8 ----------------------
SIST EN ISO 21597-2:2021
ISO 21597-2:2020(E)
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
3.1 Terms and definitions . 1
3.2 Abbreviated terms . 1
4 Specifications . 2
4.1 Use of RDF, RDFS and OWL constructs. 2
4.2 Symbols and notation. 2
4.3 Container structure . 2
4.4 Link types . 3
4.4.1 Overview . 3
4.4.2 Categories of link types . 3
4.4.3 Summary of the specified link types . 5
5 Link type description and usage . 5
5.1 General . 5
5.2 Identity. 6
5.3 Conflict . 6
5.4 Alternative . 7
5.5 Specialization . 7
5.6 Aggregation . 8
5.7 Membership. 8
5.8 Replacement . 9
5.9 Elaboration . 9
5.10 Control .10
6 Conformance requirements .10
6.1 Overview .10
6.2 General conformance requirements .10
Annex A (informative) Use cases.12
Annex B (informative) How to validate with SHACL .17
Annex C (normative) Extended Linkset ontology .21
© ISO 2020 – All rights reserved iii
---------------------- Page: 9 ----------------------
SIST EN ISO 21597-2:2021
ISO 21597-2:2020(E)
Foreword
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 accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www .iso .org/ directives).
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 the Introduction and/or
on the ISO list of patent declarations received (see www .iso .org/ patents).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, 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 (WTO) principles in the Technical Barriers to Trade (TBT), see www .iso .org/
iso/ foreword .html.
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 engineering
works, including building information modelling (BIM), in collaboration with the European Committee
for Standardization (CEN) Technical Committee CEN/TC 442, Building Information Modelling (BIM), in
accordance with the Agreement on technical cooperation between ISO and CEN (Vienna Agreement).
A list of all parts in the ISO 21597 series can be found on the ISO website.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www .iso .org/ members .html.
iv © ISO 2020 – All rights reserved
---------------------- Page: 10 ----------------------
SIST EN ISO 21597-2:2021
ISO 21597-2:2020(E)
Introduction
The ISO 21597 series has been developed in response to a need within the construction industry to be
able to handle multiple interrelated documents as a single information delivery.
In ISO 21597-1, a specification is given for a generic container format that stores documents using
various formats and structures, along with a means of linking otherwise disconnected data within
those documents (including individual parts). These documents can have any syntax and semantics.
This document extends that specification by the addition of common link types (that define
relationships) as specializations of the generic types provided in ISO 21597-1. This provides the ability
to add information about the contents of a container, rather than extending the contents.
The link types provide the ability to express comparison, ordering and dependency relationships
between the documents and entities within documents that form part of the payload of a container. This
contributes greatly to the value of the container by providing commentary, guidance and explanation
of the relationships between link elements which could otherwise be unclear or ambiguous, without
making any assumptions about, nor being dependent on the specific type of the link elements.
The specification of link types in this document deliberately uses only annotation to add further
details or meta data to the defined link types. This allows the container to be machine readable and
human interpretable while noting that machine reasoning is not within the scope of this document. The
concern is to avoid the risk of reading too much into the intention behind the expressed relationships. If
machine reasoning is needed, further specifications would be required that are not in the current scope
of this document.
The International Organization for Standardization (ISO) draws attention to the fact that it is claimed
that compliance with this document may involve the use of a patent.
ISO takes no position concerning the evidence, validity and scope of this patent right.
The holder of this patent right has assured ISO that he/she is willing to negotiate licences under
reasonable and non-discriminatory terms and conditions with applicants throughout the world. In
this respect, the statement of the holder of this patent right is registered with ISO. Information may be
obtained from the patent database available at www .iso .org/ patents.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights other than those in the patent database. ISO shall not be held responsible for identifying
any or all such patent rights.
© ISO 2020 – All rights reserved v
---------------------- Page: 11 ----------------------
SIST EN ISO 21597-2:2021
---------------------- Page: 12 ----------------------
SIST EN ISO 21597-2:2021
INTERNATIONAL STANDARD ISO 21597-2:2020(E)
Information container for linked document delivery —
Exchange specification —
Part 2:
Link types
1 Scope
This document provides the opportunity to add information about the contents of a container by further
specializing the generic types of links specified in ISO 21597-1. The defined link types have been chosen
to enhance the use of the container by allowing the addition of semantic relationships that are human
interpretable to provide greater clarity about those links.
2 Normative references
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 amendments) applies.
ISO 21597-1:2020, Information container for linked document delivery — Exchange specification — Part 1:
Container
W3C-OWL2-SPEC. Motik B., Patel-Schneider P.F., Parsia B., eds. OWL 2 Web Ontology Language:
Structural Specification and Functional-Style Syntax (Second Edition). W3C Recommendation, 11
December 2012 [viewed July 22nd 2019]. Latest version available at http:// www .w3 .org/ TR/ owl2
-syntax/
W3C-RDF11-CONCEPTS. Cyganiak R., Wood D., Lanthaler M. RDF 1.1 Concepts and Abstract Syntax.
W3C Recommendation, 25 February 2014 [viewed July 22nd 2019]. Latest version available at http://
www .w3 .org/ TR/ rdf11 -concepts/
W3C-RDF11-SCHEMA. Brickley D., Guha R.V. RDF Schema 1.1. W3C Recommendation, 25 February 2014
[viewed July 22nd 2019]. Latest version available at http:// www .w3 .org/ TR/ rdf -schema/
W3C-RDF11-XML. Gandon F., Schreiber G. RDF 1.1 XML Syntax. W3C Recommendation, 25 February
2014 [viewed July 22nd 2019]. Latest version available at http:// www .w3 .org/ TR/ rdf -syntax -grammar/
3 Terms and definitions
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 21597-1 apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at http:// www .electropedia .org/
3.2 Abbreviated terms
For the purposes of this document, the abbreviated terms given in ISO 21597-1 apply.
© ISO 2020 – All rights reserved 1
---------------------- Page: 13 ----------------------
SIST EN ISO 21597-2:2021
ISO 21597-2:2020(E)
4 Specifications
4.1 Use of RDF, RDFS and OWL constructs
All ontologies held in containers that conform to the ISO 21597 series shall be based on the languages
RDF [W3C-RDF11-CONCEPTS], RDFS [W3C-RDF11-SCHEMA] and OWL [W3C-OWL2-SPEC] (referred to
collectively in the ISO 21597 series as RDF(S)/OWL) and shall be serialized in RDF/XML [W3C-RDF11-
XML] or any other equivalent RDF serialization recommended by W3C.
The terms inverse, functional, transitive and symmetric as used in this document are defined in
paragraph 9.2 of the OWL 2 specification [W3C-OWL2-SPEC].
ISO 21597-1:2020, Table 1 lists the RDF/OWL constructs that are used in the ISO 21597 series and the
interpretation to be used when validating the contents of a container.
4.2 Symbols and notation
Throughout this document, the structure of the ontologies is illustrated using a UML notation as
described in ISO 21597-1:2020, 4.2.
In addition to the namespaces listed in ISO 21597-1:2020, Table 2, Table 1 lists the namespaces and
corresponding prefixes used in this document.
Table 1 — Namespaces and prefixes used in ontologies defined in this document
Ontology Prefix Namespace
Extended Linkset els https:// standards .iso .org/ iso/ 21597/ -2/ ed -1/ en/ ExtendedLinkset
ontology
4.3 Container structure
The structure of the container shall be the same as that of ISO 21597-1. Figure 1 shows the minimum
content of the ‘Ontology resources’ folder of an ICDD Part 2 container.
2 © ISO 2020 – All rights reserved
---------------------- Page: 14 ----------------------
SIST EN ISO 21597-2:2021
ISO 21597-2:2020(E)
Figure 1 — Minimum content of the “Ontology resources” folder
4.4 Link types
4.4.1 Overview
This document specifies nine link types that shall be used where there is a need to express relationships
between documents and/or elements within documents that form the payload of the container. These
are defined in the Extended Linkset ontology in Annex C and shall be referenced in any datasets that
conform to this document. The link types shall be used to propose semantic relationships between
documents and individual elements within the documents to suggest identity, taxonomy, meronomy
and other groupings, as well as precedence, conflicts and alternatives.
The proposed relationships represent the opinion of the authoring/providing party, and generally do
not have the same status as the linked elements referenced. In all cases, the intention is that recipients
use the link types to clarify their understanding and help them manage and use the information.
The provisional nature of the links shall be taken into account in all cases. For example, a conflict
relationship may be reported that on examination is not deemed critical by the receiver.
Furthermore, the relationships defined using these link types shall not duplicate or contradict each
other, nor shall any relationships found within the documents. The link types shall not be used to imply
any more specific relationships that depend on the semantics of the linked elements. For example, a
dependency relationship between two work-package descriptions shall not be assumed to imply
sequencing.
4.4.2 Categories of link types
The link types fall into two broad categories: those that are specialized from ls: DirectedBinaryLink
(Figure 2); and those specialized from ls: Directed1toNLink (Figure 3). As functional sub-class concepts,
these are all objectified concepts that can carry annotated properties and metadata in the form of
annotations. This ensures that they are machine readable and can be reported to the end user, but all
interpretation is left entirely to the human receiver.
© ISO 2020 – All rights reserved 3
---------------------- Page: 15 ----------------------
SIST EN ISO 21597-2:2021
ISO 21597-2:2020(E)
Figure 2 — Link types that use binary relationships
Each of the one-to-many link types depicted in Figure 3 has an explicitly defined inverse relationship
shown in Figure 4. This gives the user a clear choice to express the semantics using either the primary
or inverse relationship.
Figure 3 — Link types that use one-to-many relationships
Figure 4 — Inverses of the link types that use one-to-many relationships
4 © ISO 2020 – All rights reserved
---------------------- Page: 16 ----------------------
SIST EN ISO 21597-2:2021
ISO 21597-2:2020(E)
4.4.3 Summary of the specified link types
Table 2 provides a list of the link types specified in this document.
Table 2 — Link types specified in this document
Grouping Name Description
Binary links that This link type relates two link elements that are identical but
Identity
express comparative may be represented in different ways.
relationships
This link type relates two link elements that conflict with one
Conflict
another in some way.
This link type relates two link elements where one is an
Alternative
alternative to the other.
One-to-many links that This link type relates one link element to one or more other link
Specialization
express ordering elements that are specializations or sub-classes.
relationships
This link type relates one link element to one or more other link
Aggregation elements to form an assembly of parts where those parts exist
independently.
This link type relates one link element to one or more other link
Membership
elements to form a grouping based on some consistent criteria.
One-to-many links that This link type relates one link element to one or more other link
express dependency Replacement elements where they are a development of or supersede it in
relationships some way.
This link type relates one link element to one or more other link
Elaboration elements where they provide further explanation, reasoning,
derivation, information or usage.
This link type relates one link element to one or more other link
Control
elements over which it exercises some type of control.
5 Link type description and usage
5.1 General
This clause describes the link types specified in this document including examples of their intended
usage. Further examples are provided in Annex A, building on use case 1B in ISO 21597-1.
© ISO 2020 – All rights reserved 5
---------------------- Page: 17 ----------------------
SIST EN ISO 21597-2:2021
ISO 21597-2:2020(E)
5.2 Identity
Name: els:I sIdenticalTo
This link type indicates that two link elements are actually the same thing even though having different
representations. It can be used to identify synonyms, multi representations, etc. and is intended to
help consolidate and cross-reference the information. It is generally intended to be interpreted as both
symmetric and transitive.
EXAMPLE 1: document to document
“SitePlan.gml” The link type declares that two documents represent the
same thing, only in different ways.
IsIdenticalTo
“SitePlan.pdf”
EXAMPLE 2: document to referenced part of a document
“FirstFloor.pdf” The link type declares that a document is the same as a
specific storey in a building model.
IsIdenticalTo
“Architectural.ifc:*.Name=’1st floor’ ”
EXAMPLE 3: referenced part of a document to a referenced part of another document
“Architectural.ifc:*.Name=’1st floor’ ” The link type declares that a building storey is the same in
two separate domain models, architectural and structural.
IsIdenticalTo
“Structural.ifc:*.Name=’+3.600’ ”
5.3 Conflict
Name: els: ConflictsWith
This link type indicates overlap in space and/or time, or difference in properties or difference in
relationships. It can be used to allow recipients to note the unresolved situation. It is generally intended
to be interpreted as symmetric but not transitive.
EXAMPLE 1: document to document
“ConstructionAccessPlan.gml” The link type declares an unspecified conflict between a
construction site layout plan and previous commitments to
ConflictsWith
neighbours that should be noted by the receiver.
“AdjacentOwnersLiaison.pdf”
EXAMPLE 2: document to referenced part of a document
“SteelFrameMethodStatement.pdf” The link type declares an unspecified conflict between a
method statement and members in a building model that
ConflictsWith
should be noted by the receiver.
“Structural.ifc:*.Name=’Bracing’ ”
EXAMPLE 3: referenced part of a document to a referenced part of another document
“Architectural.ifc:*.Name=’Wall034’ ” The link type declares an unspecified conflict between
elements within two domain models that should be noted
ConflictsWith
by the receiver.
“Structural.ifc:*.Name=’Beam078’ ”
6 © ISO 2020 – All rights reserved
---------------------- Page: 18 ----------------------
SIST EN ISO 21597-2:2021
ISO 21597-2:2020(E)
5.4 Alternative
Name: els:I sAlternativeTo
This link type indicates alternative options or variants. It can be used for any type of document to
allow recipients to note the exist
...
SLOVENSKI STANDARD
oSIST prEN ISO 21597-2:2018
01-november-2018
,LQIRUPDFLMVNLYVHEQLN]DL]URþLWHYSRGDWNRY6SHFLILNDFLMD]DL]PHQMDYRGHO
'LQDPLþQDVHPDQWLND ,62',6
Information container for data drop - Exchange specification - Part 2: Dynamic semantics
(ISO/DIS 21597-2:2018)
Organisation von Daten zu Bauwerken - Informationscontainer zur Datenübergabe
(ICDD) - Teil 2: Dynamische Semantik (ISO/DIS 21597-2:2018)
Organisation de l'information concernant les travaux de construction - Conteneur
d'information pour extraction de données (ICDD) - Partie 2: Titre manque (ISO/DIS
21597-2:2018)
Ta slovenski standard je istoveten z: prEN ISO 21597-2
ICS:
35.240.67 Uporabniške rešitve IT v IT applications in building
gradbeništvu and construction industry
91.010.01 Gradbeništvo na splošno Construction industry in
general
oSIST prEN ISO 21597-2:2018 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
oSIST prEN ISO 21597-2:2018
---------------------- Page: 2 ----------------------
oSIST prEN ISO 21597-2:2018
DRAFT INTERNATIONAL STANDARD
ISO/DIS 21597-2
ISO/TC 59/SC 13 Secretariat: SN
Voting begins on: Voting terminates on:
2018-09-07 2018-11-30
Information container for data drop — Exchange
specification —
Part 2:
Dynamic semantics
Titre manque —
Partie 2: Titre manque
ICS: 35.240.67; 91.010.01
THIS DOCUMENT IS A DRAFT CIRCULATED
This document is circulated as received from the committee secretariat.
FOR COMMENT AND APPROVAL. IT IS
THEREFORE SUBJECT TO CHANGE AND MAY
NOT BE REFERRED TO AS AN INTERNATIONAL
STANDARD UNTIL PUBLISHED AS SUCH.
IN ADDITION TO THEIR EVALUATION AS
ISO/CEN PARALLEL PROCESSING
BEING ACCEPTABLE FOR INDUSTRIAL,
TECHNOLOGICAL, COMMERCIAL AND
USER PURPOSES, DRAFT INTERNATIONAL
STANDARDS MAY ON OCCASION HAVE TO
BE CONSIDERED IN THE LIGHT OF THEIR
POTENTIAL TO BECOME STANDARDS TO
WHICH REFERENCE MAY BE MADE IN
Reference number
NATIONAL REGULATIONS.
ISO/DIS 21597-2:2018(E)
RECIPIENTS OF THIS DRAFT ARE INVITED
TO SUBMIT, WITH THEIR COMMENTS,
NOTIFICATION OF ANY RELEVANT PATENT
RIGHTS OF WHICH THEY ARE AWARE AND TO
©
PROVIDE SUPPORTING DOCUMENTATION. ISO 2018
---------------------- Page: 3 ----------------------
oSIST prEN ISO 21597-2:2018
ISO 21597-2:2019
ISO/DIS 21597-2:2018(E)
Contents
Contents 2
Foreword 4
Introduction 5
1 Scope 6
2 Normative references 8
3 Terms, definitions and abbreviated terms 8
3.1 Terms and definitions 8
3.2 Abbreviated Terms 9
4 Specifications 9
4.1 Use of RDF, RDFS and OWL constructs 9
4.2 Symbols and notation 10
4.3 Conformance classes 10
4.4 Container structure 10
4.5 Dynamic semantics ontology 12
4.5.1 Overview 12
4.5.2 Objects, properties and descriptions 14
4.5.3 Metadata 16
4.5.4 Entities 17
4.5.5 Properties 18
4.5.5.1 Simple Properties 19
4.5.5.2 Complex Properties 21
4.5.6 Relations 22
4.5.6.1 Connection 23
4.5.6.2 Contains Relations 25
4.5.7 Expiring Concepts 27
4.5.8 Part 1 integration 28
5. Conformance requirements 29
Annex A (informative) Use cases 31
COPYRIGHT PROTECTED DOCUMENT
A.1 Introduction 31
A.2 Use case 2A – Inspection report in RDF format 31
© ISO 2018
A.3 Use case 2B – Use of a UDO-based classification system 37
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
A.4 Use case 2C – Link to an external classification system 43
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 copyright office
Annex B (informative) Extensions to dynamic semantics 47
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
B.1 ICDD-QUDT-Units 47
Phone: +41 22 749 01 11
Fax: +41 22 749 09 47
Email: copyright@iso.org
Website: www.iso.org
2
Published in Switzerland
ii © ISO 2018 – All rights reserved
---------------------- Page: 4 ----------------------
oSIST prEN ISO 21597-2:2018
ISO/DIS 21597-2:2018(E)
ISO 21597-2:2019
Contents
Contents 2
Foreword 4
Introduction 5
1 Scope 6
2 Normative references 8
3 Terms, definitions and abbreviated terms 8
3.1 Terms and definitions 8
3.2 Abbreviated Terms 9
4 Specifications 9
4.1 Use of RDF, RDFS and OWL constructs 9
4.2 Symbols and notation 10
4.3 Conformance classes 10
4.4 Container structure 10
4.5 Dynamic semantics ontology 12
4.5.1 Overview 12
4.5.2 Objects, properties and descriptions 14
4.5.3 Metadata 16
4.5.4 Entities 17
4.5.5 Properties 18
4.5.5.1 Simple Properties 19
4.5.5.2 Complex Properties 21
4.5.6 Relations 22
4.5.6.1 Connection 23
4.5.6.2 Contains Relations 25
4.5.7 Expiring Concepts 27
4.5.8 Part 1 integration 28
5. Conformance requirements 29
Annex A (informative) Use cases 31
A.1 Introduction 31
A.2 Use case 2A – Inspection report in RDF format 31
A.3 Use case 2B – Use of a UDO-based classification system 37
A.4 Use case 2C – Link to an external classification system 43
A.5 Use case 2D – Deliver GML representations 44
Annex B (informative) Extensions to dynamic semantics 47
B.1 ICDD-QUDT-Units 47
2
© ISO 2018 – All rights reserved
---------------------- Page: 5 ----------------------
oSIST prEN ISO 21597-2:2018
ISO/DIS 21597-2:2018(E)
ISO 21597-2:2019
B.2 Subtyping of links 47
B.3 Transformation property 48
Annex C (informative) IFC Integration 49
C.1 Levels of integration 49
C.2 Extending dynamic semantics with IFC information 49
C.3 Example 50
C.4 Prototype 52
Annex D (Informative) How to validate with SHACL 55
D.1 UDO testing for Conformance Class A example 55
D.2 Data validation example 57
Annex E (normative) Dynamic semantics ontology 61
3
© ISO 2018 – All rights reserved
---------------------- Page: 6 ----------------------
oSIST prEN ISO 21597-2:2018
ISO/DIS 21597-2:2018(E)
ISO 21597-2:2019
Foreword
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
accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see
www.iso.org/directives).
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
the Introduction and/or on the ISO list of patent declarations received (see
www.iso.org/patents).
Any trade name used in this document is information given for the convenience of users and
does not constitute an endorsement.
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
(WTO) principles in the Technical Barriers to Trade (TBT) see the following URL:
www.iso.org/iso/foreword.html.
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
engineering works, including building information modelling (BIM).
ISO 21597 consists of the following parts, under the general title Information Container for Data
Drop – Exchange specification:
— Part 1: Container
— Part 2: Dynamic semantics
4
© ISO 2018 – All rights reserved
---------------------- Page: 7 ----------------------
oSIST prEN ISO 21597-2:2018
ISO/DIS 21597-2:2018(E)
ISO 21597-2:2019
Introduction
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
documents, including the ability to add links between documents.
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
specify information deliveries conform to internal standards.
5
© ISO 2018 – All rights reserved
---------------------- Page: 8 ----------------------
oSIST prEN ISO 21597-2:2018
ISO/DIS 21597-2:2018(E)
ISO 21597-2:2019
Information container for data drop - Exchange specification -
Part 2: Dynamic Semantics
1 Scope
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
information in the container using Linked Open Data technology.
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
recognized as the standard for describing building objects.
This standard provides two conformance classes. Both conformance classes open the ability to
specialize the container for use cases not otherwise handled.
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,
versioning and creating libraries.
In Conformance Class B, the user is offered complete freedom to add user defined ontologies to
the container, with the sole condition that it is expressed in RDF/OWL.
The use cases are in line with those of Part 1, but may include numerous extensions. The
following list gives some examples:
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™
3. Add the ability for exchanging systems engineering information
4. Link to product requirement libraries
5. Add semantic links (i.e. meaningful links) to and between information provided using
existing standards like PLCS, IFC and GML
6. Link to an ontology for Units and Measures, like QUDT
7. Link to one or more Product Catalogues
6
© ISO 2018 – All rights reserved
---------------------- Page: 9 ----------------------
oSIST prEN ISO 21597-2:2018
ISO/DIS 21597-2:2018(E)
ISO 21597-2:2019
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
techniques such as SPARQL.
7
© ISO 2018 – All rights reserved
---------------------- Page: 10 ----------------------
oSIST prEN ISO 21597-2:2018
ISO/DIS 21597-2:2018(E)
ISO 21597-2:2019
2 Normative references
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
amendments) applies.
ISO/IEC 21320-1:2015, Information technology — Document Container File — Part 1: Core
http://standards.iso.org/ittf/PubliclyAvailableStandards/index.html
ISO 6707-1, Buildings and civil engineering works — Vocabulary — Part 1: General terms
W3C RDF standard, Recource Description Framework,
https://www.w3.org/standards/techs/rdf#w3c_all
RDF Schema 1.1 - W3C Recommendation 25 February 2014
https://www.w3.org/TR/rdf-schema/
W3C OWL, Web Ontology Language, https://www.w3.org/TR/2012/REC-owl2-syntax-20121211/
W3C XML, Schema Part 2: Datatypes, http://www.w3.org/TR/xmlschema-2/
3 Terms, definitions and abbreviated terms
3.1 Terms and definitions
In addition to the terms and definitions given in ISO 21597-1, for the purposes of this document,
the following general terms and definitions apply.
ISO and IEC maintain terminological databases for use in standardization at the following
addresses:
- ISO Online browsing platform: available at http://www.iso.org/obp
- IEC Electropedia: available at http://www.electropedia.org/.
3.1.1
dynamic semantics ontology
RDF/OWL file providing the object classes and properties that shall be used to specify a user-
defined ontology (UDO) that complies with Conformance Class A in this standard
3.1.2
entity
physical, digital, conceptual, or other kind of thing (either real or imaginary) with some fixed
aspects
3.1.3
information model
formal model of a bounded set of facts, concepts or instructions to meet a specified requirement
8
© ISO 2018 – All rights reserved
---------------------- Page: 11 ----------------------
oSIST prEN ISO 21597-2:2018
ISO/DIS 21597-2:2018(E)
ISO 21597-2:2019
3.1.4
property
named value denoting a characteristic of an entity that has semantic impact
3.1.5
relation
nature of how two entities affect each other including dependencies
3.1.6
user-defined ontology
ontology that adds more semantic (meaningful) information to the contents of the container
3.2 Abbreviated Terms
In addition to the abbreviated terms given in ISO 21597-1, for the purposes of this document,
the following abbreviated terms are used to part.
UDO User-Defined Ontology
QUDT Quantities, Units, Dimensions and Data Types
PLCS Product Life Cycle Support
4 Specifications
4.1 Use of RDF, RDFS and OWL constructs
The ontologies specified in this standard use the languages RDF [https://www.w3.org/RDF/],
RDFS [https://www.w3.org/TR/rdf-schema/] and OWL [https://www.w3.org/OWL/].
NOTE: It is expected that RDF/OWL will be an important technology and a general platform for Ontologies
for the coming decades. Proprietary systems will increasingly adopt RDF/OWL.
In general, when used in the context of the world wide web, these languages use the following
principles to support reasoning:
- 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
statement is false;
- No unique names assumption - unless explicitly stated otherwise, it cannot be assumed
that resources that are identified by different URIs are different.
The datasets that comply with the ontologies specified in this standard shall use the following
interpretation of RDF, RDFS and OWL:
- Closed world assumption - a statement that is true is also known to be true; therefore,
conversely, what is not formally specified in a container to be true, is false;
- 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
owl:sameAs predicate).
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
context.
9
© ISO 2018 – All rights reserved
---------------------- Page: 12 ----------------------
oSIST prEN ISO 21597-2:2018
ISO/DIS 21597-2:2018(E)
ISO 21597-2:2019
4.2 Symbols and notation
Throughout this standard, the structure of the ontologies is illustrated using a UML notation as
described in ISO 21597-1 (section 4.2).
In addition to the namespaces listed in ISO 21597-1, Table 1 lists the namespaces and
corresponding prefixes used in this standard.
Table 1 - Namespaces and prefixes used in ontologies defined in this standard
Ontology Prefix Namespace
Container ontology ds http://www.iso-icdd.org/part2/2019/DynamicSemantics
http://qudt.org/schema/qudt
QUDT ontology qudt
4.3 Conformance classes
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
of user-defined ontologies (UDOs).
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
extensions are provided in Annex B.
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
RDF/OWL.
See chapter 5 for the detailed requirements of both conformance classes.
4.4 Container structure
The structure of the container shall be the same as that of a Part 1 container. Figure 1 shows the
minimum structure of the root of a container.
10
© ISO 2018 – All rights reserved
---------------------- Page: 13 ----------------------
oSIST prEN ISO 21597-2:2018
ISO/DIS 21597-2:2018(E)
ISO 21597-2:2019
Figure 1 - Minimum structure of the root of a container
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
user defined ontologies (UDOs) that are extensions of DynamicSemantics.rdf.
In Conformance Class B, the DynamicSemantics.rdf ontology may be present in the ‘Ontology
resources’ folder but is not required.
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
Conformance Class A.
11
© ISO 2018 – All rights reserved
---------------------- Page: 14 ----------------------
oSIST prEN ISO 21597-2:2018
ISO/DIS 21597-2:2018(E)
ISO 21597-2:2019
Figure 2 - Minimum content of the Ontology resources folder for Conformance Class A
4.5 Dynamic semantics ontology
4.5.1 Overview
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
among extensions.
Table 2 provides an overview and rationale for the contents of DynamicSematics.rdf.
12
© ISO 2018 – All rights reserved
---------------------- Page: 15 ----------------------
oSIST prEN ISO 21597-2:2018
ISO/DIS 21597-2:2018(E)
ISO 21597-2:2019
Table 2 - Overview and rationale for the dynamic semantics ontology
Content Description
Concepts
Holding ds:DynamicSemantics is introduced as a root for dynamic semantics.
Metadata ds:Concept is introduced as a subclass of ds:DynamicSemantics and is the root
for representing entities (with properties and relationships) contained
within an information model. It has the ct:creator and ct:modifier properties.
All other Part 2 classes to support dynamic semantics are subclasses of
ds:Concept.
Representing
A key class is ds:Entity. This class inherits its metadata from ds:Concept and
Information
is equipped to support ‘connections’.
Model Entities
The ds:Entity class is very general and can be used and tailored by
extensions to represent, for example, physical components, spatial concepts,
functional entities, etc.
Expanding
Part 2 allows the use of standard RDF/OWL properties. See chapter 5 for
Property
more information on using RDF/OWL properties. It is noted that those
Definitions
standard properties are limited in their semantic richness.
Therefore, we introduce an option to treat properties as owl:Classes. This is
done to provide the flexibility to add statements about the values of
properties and enable interoperability with other ontologies such as QUDT.
In particular, this standard makes a distinction between a ds:SimpleProperty
class (for single values) and a ds:ComplexProperty class (for multiple values).
Specifying
There are two types of relationships very common to the construction
Relationships
industry and widely used: those are ‘connection’ and ‘decomposition’.
Therefore, those relationships should have a standardized format.
An individual of the ds:Entity class can be related to other individuals via the
subclasses of the ds:Relation class. Specifically the ds:ContainsRelation
subclass can be used to model the relationship between individuals of class
ds:Assembly and their instances of class ds:Part (i.e. a decomposition
structure). The other subclass, ds:Connection, may be used to model kinds of
relationships other than decomposition.
Expiring
To exchange multiple versions of an individual of class ds:Concept, the
Concepts
ds:priorVersion property may be used to relate a new ds:Concept to an old
version of ds:Concept.
To expire a ds:Concept explicitly the individual must be made a member of
ds:ExpiredConcept class
13
© ISO 2018 – All rights reserved
---------------------- Page: 16 ----------------------
oSIST prEN ISO 21597-2:2018
ISO/DIS 21597-2:2018(E)
ISO 21597-2:2019
4.5.2 Objects, properties and descriptions
Tables 3, 4 and 5 list the objects, datatype properties and object properties respectively that are
used in the dynamic semantics ontology, providing brief descriptions of each.
Table 3 - Classes defined in the dynamic semantics ontology
Object name Description
ds:Assembly a class denoting that individuals of this class can belong to an Assembly-Part
hierarchy via ds:ContainsRelations
ds:BooleanProperty a ds:BooleanProperty is a subtype of a ds:SimpleProperty where the
ds:datatypeValue is restricted to accepting only xsd:booleans
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
exactly 1 ds:ComplexPropertyValue via the ds:objectValue property
ds:ComplexPropertyValue entities can be connected to ds:ComplexPropertyValue via a ds:ComplexProperty;
the ds:ComplexProperty denotes the property while the ds:ComplexPropertyValue
contains the actual content of this property; this can comprise of a ds:Entity with
relations and properties
ds:DynamicSemantics a superclass for all ICCD dynamic semantics classes; this class is without any
properties or relations and its only purpose is to distinguish ICDD classes from
other classes
ds:Connection connection between individuals of the class ds:Entity only, since the
ds:hasConnectedEntities property is restricted to ds:Entity
ds:ContainsRelation a ds:ContainsRelation is a subtype of ds:Relation that is connected to exactly 1
ds:Assembly and exactly 1 ds:Part
ds:ContainsRelationGroup a ds:ContainsRelationGroup allows the grouping of ds:ContainsRelations enabling
to distinguish multiple ds:ContainsRelation sets; this forms the basis for advanced
modelling capabilities that deal with multiple decompositions
ds:DateTimeProperty a ds:DateTimeProperty is a subtype of a ds:SimpleProperty where the
ds:datatypeValue is restricted to accepting only xsd:dateTime
ds:DirectedConnection a directed connection is a subtype of ds:Connection and connects 2 ds:Entity
individuals via the ds:fromEntity and ds:toEntity properties, hence giving the
connection a direction
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
contains some relations and properties
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
1 connection to a ds:Concept via ds:propertyBelongsTo
ds:ExpiredConcept Defines individuals that are expired; individuals of class ds:Concept can be made a
member of this class to denote their expiration
ds:FloatProperty a ds:FloatProperty is a subtype of a ds:SimpleProperty where the ds:datatypeValue
is restricted to accepting only xsd:float
14
© ISO 2018 – All rights reserved
---------------------- Page: 17 ----------------------
oSIST prEN ISO 21597-2:2018
ISO/DIS 21597-2:2018(E)
ISO 21597-2:2019
ds:IntegerProperty a ds:IntegerProperty is a subtype of a ds:SimpleProperty where the
ds:datatypeValue is restricted to accepting only xsd:integer
ds:NumericProperty an abstract property (when owl:UnionClass is interpreted as a constraint) for
ds:FloatProperty and ds:IntegerProperty
ds:Entity a generic class to distinguish a ds:Entity from other things like a
ds:AbstractProperty; a ds:Entity is a physical, digital, conceptual, or other kind of
thing with some fixed aspects; entities may be real or imaginary.
ds:Part a ds:Part is a subclass of ds:Concept that can be connected via a
ds:ContainsRelation to a ds:Assembly; an individual of class ds:Part can be a
ds:Entity or any other ds:Concept
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
has a mandatory ds:datatypeValue representing the actual property value.
ds:StringProperty a ds:StringProperty is a subtype of ds:SimpleProperty where the ds:datatypeValue
is restricted to accepting only xsd:string
ds:UriProperty a ds:UriProperty is a subtype of ds:SimpleProperty where the ds:datatypeValue is
restricted accepting only xsd:anyURI
Table 4 - Datatype properties used in the dynamic semantics ontology
Datatype name Description
ds:datatypeValue ds:datatypeValue holds the content for an individual of class ds:SimpleProperty
Table 5 - Object properties used in the dynamic semantics ontology
Object Property name Description
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
relates a ds:Entity to a ds:DirectedConnection
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:groups an object property that relates a ds:ContainsRelationGroup to a
ds:ContainsRelation; this property has ds:groupedBy as an inverse property
ds:hasAssembly ds:hasAssembly is a sub property of ds:hasConnectedEntities and relates an
ds:Assembly to a ds:ContainsRelation
ds:hasConnectedEntities ds:hasConnectedEntities relates any ds:Concept to a ds:Relation
ds:hasConnections ds:hasConnections relates a ds:Entity to a ds:Connection
ds:hasContainsRelation ds:hasContainsRelations relates a ds:ContainsRelation to a ds:Assembly; it is the
inverse of the ds:hasAssembly property
15
© ISO 2018 – All rights reserved
---------------------- Page: 18 ----------------------
oSIST prEN ISO 21597-2:2018
ISO/DIS 21597-2:2018(E)
ISO 21597-2:2019
ds:hasIncomingConnections ds:hasIncomingConnections is a sub property of ds:hasConnections and relates a
ds:Entity to a ds:DirectedConnection; it is the inverse of ds:toEntity
ds:hasOutgoingConnections ds:hasOutgoingConnections is a sub property of ds:hasConnections and relate
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.