SIST EN 17632-1:2023
(Main)Building Information Modelling (BIM) - Semantic Modelling and Linking (SML) - Part 1: Generic modelling patterns
Building Information Modelling (BIM) - Semantic Modelling and Linking (SML) - Part 1: Generic modelling patterns
This document discusses an integrated and unified approach for data aspects, specifically for assets in the built environment, using EIF terminology.
The following data architecture (Figure 1) applies within each category.
Figure 1 - Data architecture with typology (grey areas indicating the scope of this document)
...
This document specifies:
- a generic Top Level "M1: Data model" as common form;
- a conceptual "L1: Data language" as common meta-model with four ‘linked data’-based concrete language bindings (SKOS, RDFS, OWL and SHACL), including:
- a choice of RDF-based formats (to be used for all modelling and language levels);
- a set of data modelling patterns (for identification, naming, handling of enumeration types, quantity modelling, asset decomposition, grouping, etc.).
- a linking approach for interlinking data sets, interlinking data models and linking data sets and data models which are relevant within the built environment from many perspectives such as:
- Building information modelling (BIM);
- Geo-spatial information systems (GIS);
- Systems engineering (SE) );
- Monitoring & control (M&C);
- Electronic document management (EDM).
This document does not specify a knowledge model since this is already available in ISO 12006-3.
This document does not specify a meta-‘data language’ since this is already provided by the concrete RDF language bindings (being RDFS).
The scope of this document in general excludes the following:
- Business process modelling;
- Software implementation aspects;
- Data packaging and transportation/transaction aspects (handled by ISO TC59/SC13 Information container for document delivery (ICDD) respectively various information delivery manual (IDM) / information exchange requirements (EIR)-related initiatives);
- Domain-specific (here: built environment-specific) content modelling in the form of concepts, attributes and relations at end-user level (the actual ontologies themselves) beyond a generic upper ontology and modelling patterns.
Semantischer Modellierungs- und Verknüpfungsstandard (SMLS) für die Datenintegration in der gebauten Umwelt
Dieses Dokument behandelt einen integrierten Ansatz und eine vereinheitlichte Vorgehensweise für Datenaspekte und insbesondere für Assets und gebaute Umwelt unter Verwendung der EIF Terminologie.
Die folgende Datenarchitektur (Bild 1) gilt innerhalb jeder Kategorie.
Dieses Dokument legt fest:
- eine oberste Ebene „M1: Datenmodell“ als gemeinsame Form;
- eine konzeptionelle Ebene „L1: Datensprache“ als gemeinsames Meta-Modell mit vier auf „vernetzten Daten“ basierenden konkreten Sprachbindungen (SKOS, RDFS, OWL und SHACL), einschließlich:
- einer Auswahl RDF basierter Formate (anzuwenden für alle Modellierungs- und Sprachebenen);
- ein Satz von Datenmodellierungsmustern (zur Kennzeichnung, Benennung, Handhabung von Aufzählungstypen, Größenmodellierung, Asset-Zergliederung usw.).
- ein Vernetzungsansatz für die Vernetzung von Datensätzen, die Vernetzung von Datenmodellen und die Vernetzung von Datensätzen und Datenmodellen, die innerhalb der gebauten Umwelt aus verschiedenen Perspektiven relevant sind, wie etwa:
- Bauwerksinformationsmodellierung (BIM);
- Geoinformationssysteme (GIS);
- Systems Engineering (SE) ;
- Überwachung und Steuerung (M&C);
- elektronisches Dokumentenmanagement (EDM).
Dieses Dokument legt kein Wissensmodell fest, da dies bereits in ISO 12006 3 verfügbar ist.
Dieses Dokument legt keine Metadatensprache fest, da diese bereits durch die konkreten RDF Sprachbindungen (die RDFS) bereitgestellt ist.
Der Anwendungsbereich dieses Dokuments schließt grundsätzlich Folgendes aus:
- Modellierung von Geschäftsprozessen;
- Aspekte der Softwareimplementierung;
- Datenbündelungs- und Transport /Transaktionsaspekte [gehandhabt durch ISO TC59/SC13 Information container for document delivery (ICDD), respektive verschiedene Initiativen in Verbindung mit dem Handbuch der Informationslieferungen (IDM)/Informationsaustausch-Anforderungen (EIR)];
- bereichsspezifische (hier: spezifisch für gebaute Umwelt) Inhaltsmodellierung in Form von Konzepten, Attributen und Relationen auf Endnutzer-Ebene (die tatsächlichen Ontologien selbst) über eine generische obere Ontologie und Modellierungsmuster hinaus.
Modélisation d'informations de la construction (BIM) - Modélisation et liens sémantiques (SML) - Partie 1 : Schémas de modélisation génériques
Le présent document décrit une approche intégrée et unifiée pour les aspects liés aux données, qui s'applique plus spécifiquement aux actifs de l'environnement bâti, en s'appuyant sur la terminologie de l'EIF.
L'architecture de données suivante (Figure 1) s'applique dans chaque catégorie.
Le présent document spécifie :
- un haut niveau générique « M1 : Modèle de données » en tant que forme commune ;
- un niveau conceptuel « L1 : Langage de données » en tant que métamodèle commun, avec quatre liaisons de langage concrètes (SKOS, RDFS, OWL et SHACL) basées sur des « données liées » et comprenant :
- un choix de formats RDF (à utiliser pour tous les niveaux de modélisation et de langage) ;
- un ensemble de schémas de modélisation des données (pour l'identification, le nommage, le traitement des types d'énumérations, la modélisation des quantités, la décomposition des actifs, le regroupement, etc.) ;
- une approche de liaison pour lier des ensembles de données entre eux, lier des modèles de données entre eux et lier des ensembles de données et des modèles de données pertinents dans le contexte de l'environnement bâti, selon diverses perspectives, notamment :
- la modélisation d'informations de la construction (BIM) ;
- les systèmes d'information géospatiaux (SIG) ;
- l'ingénierie des systèmes (SE) ) ;
- la surveillance et le contrôle (M&C) ;
- la gestion électronique de documents (GED).
Le présent document ne spécifie pas de modèle de connaissances, celui-ci étant déjà couvert par l'ISO 12006-3.
Le présent document ne spécifie pas de « méta-Langage de données», car il est déjà fourni par les liaisons de langage RDF concrètes (à savoir RDFS).
D'une manière générale, le domaine d'application du présent document exclut les aspects suivants :
- la modélisation des processus métier ;
- les aspects liés à l'implémentation de logiciels ;
- les aspects liés au paquetage et au transport/à la transaction de données (traités par l'ISO TC59/SC 13 Conteneur d'informations pour la livraison de documents (ICDD), par le biais de divers manuels de livraison d'informations (IDM) et d'initiatives en lien avec les exigences d'échange d'informations (EIR), respectivement) ;
- la modélisation de contenus propres à un domaine spécifique (ici, propres à l'environnement bâti), sous la forme de concepts, d'attributs et de relations au niveau de l'utilisateur final (les ontologies réelles proprement dites), au-delà des schémas d'ontologie et de modélisation génériques de niveau supérieur.
Informacijsko modeliranje gradenj (BIM) - Semantični standard za modeliranje in povezovanje (SML) - 1. del: Generični vzorci modeliranja
Ta dokument obravnava celovit in enoten pristop k podatkovnim vidikom, zlasti za sredstva v grajenem okolju, z uporabo terminologije EIF.
Spodnja podatkovna arhitektura (Slika 1) se uporablja v vsaki kategoriji.
Slika 1: Podatkovna arhitektura s tipologijo (siva območja označujejo področje uporabe tega dokumenta)
...
Ta dokument določa:
– splošno najvišjo raven "M1: Podatkovni model" kot skupna oblika;
– konceptualni "L1: Podatkovni jezik" kot skupni meta-model s štirimi konkretnimi jezikovnimi vezavami na podlagi "povezanih podatkov" (SKOS, RDFS, OWL in SHACL), vključno z:
– izbiro formatov, ki temeljijo na RDF (ki se uporabljajo za vse ravni modeliranja in jezikov);
– nabor vzorcev modeliranja podatkov (za identifikacijo, poimenovanje, obravnavo naštevalnih tipov, modeliranje količine, razčlenitev sredstev, združevanje v skupine itd.).
– povezovalni pristop za medsebojno povezovanje podatkovnih nizov, medsebojno povezovanje podatkovnih modelov ter povezovanje podatkovnih nizov in podatkovnih modelov, ki so v grajenem okolju pomembni z več vidikov, kot so:
– informacijsko modeliranje stavb (BIM);
– geoprostorski informacijski sistemi (GIS);
– sistemski inženiring (SE) );
– spremljanje in nadzor (M&C);
– elektronsko upravljanje dokumentov (EDM).
Ta dokument ne določa modela znanja, saj je ta že na voljo v standardu ISO 12006-3.
Ta dokument ne določa meta-"podatkovnega jezika", saj je ta že na voljo v konkretnih jezikovnih povezavah RDF (RDFS).
Področje uporabe tega dokumenta na splošno izključuje naslednje:
– modeliranje poslovnih procesov;
– vidiki izvajanja programske opreme;
– vidike ustvarjanja podatkovnih paketov in prenosa/transakcij (ki jih obravnava ISO TC59/SC13 Informacijski vsebnik za dostavo dokumentov (ICDD) oziroma različne pobude, povezane s priročnikom z informacijami (IDM) / zahtevami za izmenjavo informacij (EIR));
– modeliranje vsebine, specifične za posamezno področje (v tem primeru: specifične za grajeno okolje), v obliki konceptov, atributov in odnosov na ravni končnega uporabnika (njihove dejanske ontologije), ki presegajo splošno zgornjo ontologijo in vzorce modeliranja.
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
SIST EN 17632-1:2023
01-april-2023
Informacijsko modeliranje gradenj (BIM) - Semantični standard za modeliranje in
povezovanje (SML) - 1. del: Generični vzorci modeliranja
Building Information Modelling (BIM) - Semantic Modelling and Linking (SML) - Part 1:
Generic modelling patterns
Semantischer Modellierungs- und Verknüpfungsstandard (SMLS) für die
Datenintegration in der gebauten Umwelt
Modélisation d'informations de la construction (BIM) - Modélisation et liens sémantiques
(SML) - Partie 1 : Schémas de modélisation génériques
Ta slovenski standard je istoveten z: EN 17632-1:2022
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 17632-1:2023 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST EN 17632-1:2023
---------------------- Page: 2 ----------------------
SIST EN 17632-1:2023
EN 17632-1
EUROPEAN STANDARD
NORME EUROPÉENNE
December 2022
EUROPÄISCHE NORM
ICS 35.240.67
English Version
Building information modelling (BIM) - Semantic
modelling and linking (SML) - Part 1: Generic modelling
patterns
Modélisation d'informations de la construction (BIM) - Semantischer Modellierungs- und
Modélisation et liaisons sémantiques (SML) - Partie 1 : Verknüpfungsstandard (SMLS) für die
Schémas de modélisation génériques Datenintegration in der gebauten Umwelt
This European Standard was approved by CEN on 12 September 2022.
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, Türkiye 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
© 2022 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN 17632-1:2022 E
worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
SIST EN 17632-1:2023
EN 17632-1:2022 (E)
Contents Page
European foreword . 4
Introduction . 5
1 Scope . 6
2 Normative references . 7
3 Terms and definitions . 8
4 Symbols and abbreviated terms .11
4.1 Symbols .11
4.2 Abbreviated terms .11
5 Semantic modelling levels of capability .13
6 L1: Information language .14
6.1 Conceptual L1: Information language.14
6.2 Concrete L1: Information language bindings .16
6.3 Modelling patterns .19
7 M1: Information model .28
7.1 Top level information model .28
7.2 Systems engineering extension.30
8 Implementing SML in code .32
9 Conformance .32
9.1 General .32
9.2 Conformance on language level .32
9.3 Conformance on semantic level .33
Annex A (normative) SML implementation in ‘linked data’ .34
A.1 Introduction .34
A.2 SKOS part .34
A.3 RDFS part .40
A.4 OWL part .48
A.5 SHACL part .53
Annex B (normative) Selected W3C RDF language subsets .58
B.1 General .58
nd
B.2 XML schema (XSD), part 2: Datatypes 2 edition .58
B.3 Resource description framework (RDF).58
B.4 Simple knowledge organization system (SKOS) .59
B.5 Resource description framework schema (RDFS) .59
B.6 Web ontology language (OWL) .60
B.7 Shape constraint language (SHACL) .61
Annex C (informative) SML Example in SKOS/RDFS/OWL/SHACL (Turtle format) .64
C.1 Example description .64
C.2 SKOS part .64
2
---------------------- Page: 4 ----------------------
SIST EN 17632-1:2023
EN 17632-1:2022 (E)
C.3 RDFS part . 66
C.4 OWL part . 69
C.5 SHACL part . 70
C.6 Data part . 71
Annex D (informative) Relationships with other asset/product modelling standards . 73
D.1 General . 73
D.2 Relationship with the ISO 21597 series . 73
D.3 Relationship with EN ISO 23387 . 73
D.4 Relationship with the ISO 15926 series . 92
Annex E (informative) Linking information . 94
E.1 Types of linking . 94
E.2 Language-level language link sets . 94
Bibliography . 96
3
---------------------- Page: 5 ----------------------
SIST EN 17632-1:2023
EN 17632-1:2022 (E)
European foreword
This document (EN 17632-1:2022) has been prepared by Technical Committee CEN/TC 422 “Building
information modelling (BIM)”, the secretariat of which is held by SN - Norway.
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 June 2023, and conflicting national standards shall be
withdrawn at the latest by June 2023.
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.
Any feedback and questions on this document should be directed to the users’ national standards body.
A complete listing of these bodies can be found on the CEN website.
According to the CEN-CENELEC Internal Regulations, the national standards organisations 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, Türkiye and the United
Kingdom.
4
---------------------- Page: 6 ----------------------
SIST EN 17632-1:2023
EN 17632-1:2022 (E)
Introduction
This document is about the built environment. In the built environment, assets relating to buildings and
infrastructures need to be managed across their entire life cycle, involving programming, design,
construction, operation, modification and demolition or disassembly. Vast amounts of valuable
information about them are created or captured, stored and communicated according to a diverse range
of forms and structures - and often lost again.
To manage these projects and their resulting assets more efficiently and effectively, information needs to
be findable, accessible, interoperable and reusable (FAIR). The world wide web consortium (W3C)
provides open and generic linked data (LD) and semantic web (SW) technologies [1] which are capable
of providing this ‘FAIRness’ giving information a common form (‘syntax’) and structure (‘semantics’).
Using the ‘new European Interoperability Framework’ (EIF) [9] terminology, this document focuses on
syntactic and semantic interoperability.
This document specifies how organizations in the built environment can apply this W3C technology to
best suit their needs. For example, it can be used within organizations to communicate information
internally between various business departments and software, or it can be used externally to publish
information across the multitude of databases and organizations in the sector.
Application of this document will in particular help to align and integrate relevant ‘modelling worlds’ for
the built environment, typically involving already existing complex information models, like in Building
Information Modelling (BIM), Geographical Information Systems (GIS), Systems Engineering (SE),
Monitoring & Control (M&C) and Electronic Document Management (EDM).
Regarding to BIM Building Information Modelling, this document has been prepared with the
EN ISO 16739-1 [11] Industry Foundation Classes (IFC) information model in mind, and it has been
aligned with the revision work of EN ISO 12006-3 [17] (used to extend IFC via a buildingSmart data
dictionary (bSDD)). More specifically, this document offers a ‘linked data’ view on the ‘data templates’
related to CEN TC442/WG4. It provides a way to represent the ‘attributes’ for ‘properties’ of
EN ISO 23386:2020 [15] implemented according to EN ISO 23387:2020 [16], again involving
EN ISO 12006-3.
As any other technical specification, this document requires expertise and experience in specifying,
procuring and delivering work results. As semantic modelling and linking is in the domain of computer
science, the content is aimed at those professionals. This document however, provides a standardized
approach for the built environment, and thus this introduction addresses the sector and its decision
makers.
Wherever the sector could benefit from better ways of searching, finding and (re)using information, this
document specifies how to store, model, publish and link this information, with the aim of modelling
information once in a standardized way, instead of adapting and transforming information on an ad hoc
basis. In other words, it is not a matter of shifting information structures already in place, but a matter of
modelling them for publishing on the Web/internet in more cloud-native ways.
The key principle of this document is to keep semantic modelling as simple and standardized as possible.
The objectives for capability range from machine-readable information (interpreted by humans) via (as
far as possible) machine-interpretable information to fully integrated and interlinked information
sources.
This document is complementary to other ISO standards. In the Annex D, related ISO standards are listed
and the exact relationships are described.
The standardized modelling patterns introduced in this document may be applicable to other industry
sectors as well.
5
---------------------- Page: 7 ----------------------
SIST EN 17632-1:2023
EN 17632-1:2022 (E)
1 Scope
This document addresses syntactic and semantic interoperability for information describing assets going
through their life cycle in the built environment. It assumes the underlying technical interoperability
provided already by the Internet/World Wide Web (WWW) technology-stack. The syntactic aspects
relate to the Linked Data (LD)/Semantic Web (SW) formats and the SPARQL direct access method
provided. The semantic aspects relate to the LD/SW-based information models in the form of thesauri
and ontologies giving meaning to the information.
The following information architecture (Figure 1) applies.
Figure 1 — Information architecture with (grey areas indicating the scope of this document)
This document specifies:
— a conceptual “L1: Information language” with four RDF-based language bindings being SKOS, RDFS,
OWL and SHACL, including:
— a choice of ‘linked data’/RDF-based formats (to be used for all modelling and language levels);
and
— a generic Top Level Information Model of a total “M1: Information model”, here “an upper ontology”,
including:
— a set of generic information modelling patterns for identification, annotation, enumeration
datatypes, complex quality/quantity modelling, decomposition and grouping.
This modelling approach for information models and information sets is relevant within the built
environment from multiple perspectives such as:
— Building information modelling (BIM);
— Geographical information systems (GIS);
— Systems engineering (SE);
— Monitoring & control (M&C); and
— Electronic document management (EDM).
6
---------------------- Page: 8 ----------------------
SIST EN 17632-1:2023
EN 17632-1:2022 (E)
Annex E discusses in an informative way how the information models and sets relevant for these different
worlds can be linked together using LD/SW technology.
This document does not specify a full meta-‘information model’, sometimes referred to as a ‘Knowledge
Model (KM)’. EN ISO 12006-3 provides such an often used model for the built environment. In Annex D,
Subclause D.3 it is shown how this existing model can be made compliant to this document. The only
direct support for this meta level comes in the form of the possibility to define ‘types’ (enumeration types
or concept types) and ‘objectifications’ as metaconcepts.
This document does not specify a meta-‘information language’ since this is already provided by the
concrete RDF-based language bindings (being RDFS).
The scope of this document in general excludes the following:
— Business process modelling;
— Software implementation aspects;
— Information packaging and transportation/transaction aspects already handled by ISO TC59/SC13
Information container for linked document delivery (ICDD) ([13]) respectively various information
delivery manual (IDM) / information exchange requirements (EIR)-related initiatives; and
— Domain-specific (here: ‘built environment’-specific) content modelling in the form of concepts,
attributes and relations at end-user level (the actual ontologies themselves) beyond a generic top
level information model (‘upper ontology’) and modelling and linking patterns.
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 for this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
JSON-LD 1.1, A JSON-based Serialization for Linked Data, W3C Recommendation, 16 July 2020,
https://www.w3.org/TR/json-ld11/
1
OWL 2 Web Ontology Language, Document Overview (Second Edition), W3C Recommendation,
11 December 2012, https://www.w3.org/TR/2012/REC-owl2-overview-20121211/
RDF 1.1 Concepts and Abstract Syntax, W3C Recommendation, 25 February 2014,
https://www.w3.org/TR/rdf11-concepts/
RDF 1.1 Turtle, W3C Recommendation, 25 February 2014, https://www.w3.org/TR/turtle/
RDF 1.1 XML Syntax, W3C Recommendation 25 February 2014, https://www.w3.org/TR/rdf-syntax-
grammar/
RDF Schema 1.1, W3c Recommendation, 25 February 2014, https://www.w3.org/TR/rdf-schema/
SHACL (Shapes Constraint Language). W3C Recommendation, 20 July 2017,
https://www.w3.org/TR/shacl/
SKOS Simple Knowledge Organization System Reference. W3C Recommendation, 18 August 2009,
https://www.w3.org/TR/skos-reference/
1
Hereafter referred to as just “OWL”.
7
---------------------- Page: 9 ----------------------
SIST EN 17632-1:2023
EN 17632-1:2022 (E)
SPARQL 1.1 Overview, 21 March 2013, W3C Recommendation, https://www.w3.org/TR/sparql11-
overview/ (referencing, among others, the next two, more specific, references)
SPARQL 1.1 Query Language, W3C Recommendation, 21 March 2013,
https://www.w3.org/TR/2013/REC-sparql11-query-20130321/
SPARQL 1.1 Protocol, W3C Recommendation, 21 March 2013, https://www.w3.org/TR/sparql11-
protocol/
XML Schema Part 2: Datatypes, Second Edition, W3C Recommendation, 28 October 2004,
https://www.w3.org/TR/xmlschema-2/
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 6707-1 and the following 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 https://www.electropedia.org/
3.1
asset
item, thing or entity that has potential or actual value to an organization
[SOURCE: ISO 55000:2014, 3.2.1, modified – Note 1, 2 and 3 to entry have been removed.]
3.2
attribute
inherent characteristic
Note 1 to entry: The term used in EN ISO 12006-3 is xtdProperty.
[SOURCE: EN ISO 9241-302:2008, 3.4.2, modified – Note 1 to entry has been added.]
3.3
built environment
collection of man-made or induced physical objects located in a particular area or region
[SOURCE: ISO 6707-3:2017, 3.1.3]
3.4
closed-world assumption
CWA
assumption, in a formal system of logic used for knowledge representation that a statement that is true
is also known to be true; therefore, conversely, what is not currently known to be true is false
Note 1 to entry: Typically combined with the Unique Name Assumption (UNA).
3.5
concept
abstract entity for determining category membership
[SOURCE: ISO/IEC 2382:2015, 2122971]
8
---------------------- Page: 10 ----------------------
SIST EN 17632-1:2023
EN 17632-1:2022 (E)
3.6
data format
predetermined arrangement of data on a data medium
[SOURCE: ISO 5127:2017, 3.1.13.12]
3.7
exchange information requirement
EIR
information requirement in relation to an appointment
[SOURCE: EN ISO 19650-1:2018, 3.3.6]
3.8
hierarchy
concept system in which all concepts are related in hierarchical relations that form a partial ordering
[SOURCE: ISO/IEC TR 11179-2:2019, 3.8]
3.9
information model
data model
description of the organization of information giving structure/meaning (‘semantics’) to an information
set
3.10
information set
data set
named collection of information describing or specifying something you can or could point at in reality
3.11
level of capability
LoC
semantic modelling power provided by the ‘linked data’ languages related to the needs of a specific use
case type
3.12
machine-interpretable
able to (to a certain extent) be semantically interpreted by a computer
3.13
machine-readable
able to be read and processed by a computer
3.14
meronomy
type of hierarchy which deals with part-whole relationships
[SOURCE: ISO/IEC 11179-3:2013, 3.2.73]
3.15
metadata
data about data (documents, information sets, information models or elements in those)
9
---------------------- Page: 11 ----------------------
SIST EN 17632-1:2023
EN 17632-1:2022 (E)
3.16
n-ary
having an arity of n
3.17
object
any part of the perceivable or conceivable world
Note 1 to entry: An object is something abstract or physical toward which thought, feeling, or action is directed.
Note 2 to entry: Within this document, the term individual is used as synonym of object.
[SOURCE: EN ISO 12006-2:2020, 3.1.1, modified – added Note 1 and Note 2 to entry.]
3.18
ontology
formal, explicit specification of a shared conceptualization
Note 1 to entry: An ontology typically includes definitions of concepts and specified relationships between them,
set out in a formal way so that a machine can use them for reasoning.
[SOURCE: ISO 25964-2:2013, definition 3.57]
Note 2 to entry: See also ISO/TR 13054:2012, definition 2.6; ISO/TS 13399-4:2014, definition 3.20;
ISO 19101-1:2014, definition 4.1.26; ISO 18435-3:2015, definition 3.1; ISO/IEC 19763-3:2010, definition 3.1.1.1.
Note 3 to entry: Applied in this document as a set of concepts, reference individuals, value types, reference values,
attributes, relations, constraints and derivations.
[SOURCE: ISO 5127:2017, 3.1.2.03, modified – added Note 3 to entry.]
3.19
open-world assumption
OWA
opposite of the closed-world assumption stating that lack of knowledge does not imply falsity
Note 1 to entry: typically combined with the No Unique Name Assumption (NO-UNA).
3.20
property
attribute or a relation
Note 1 to entry: This is also the term used in RDF (rdf:Property).
3.21
relation
relationship
sense in which concepts can be connected, via constituent roles
Note 1 to entry: The related concepts may be general or individual concepts.
Note 2 to entry: The term used in EN ISO 12006-3 is xtdRelationshipToSubject.
EXAMPLE Causality is a relation with two constituent roles: cause and effect.
[SOURCE: ISO/IEC 11179-3:2013, 3.2.119, modified – added Note 2 to entry.]
10
---------------------- Page: 12 ----------------------
SIST EN 17632-1:2023
EN 17632-1:2022 (E)
3.22
systems engineering
SE
interdisciplinary approach governing the total technical and managerial effort required to transform a
set of stakeholder needs, expectations, and constraints into a solution and to support that solution
throughout its life
[SOURCE: ISO/IEC/IEEE 12207:2017, 3.1.65]
3.23
taxonomy
type of hierarchy which deals with generalization/specialization relationships
[SOURCE: ISO/IEC 11179-3:2013, 3.2.135]
3.24
top level information model
generic part of an information model (typically a generic taxonomy)
3.25
triple
statement in the form subject-predicate-object that expresses a fact
3.26
typology
type of hierarchy which deals with classification/instantiation relationships
3.27
use case
sequence of actions that an actor (usually a person, but perhaps an external entity, such as another
system) performs within a system to achieve a particular goal
[SOURCE: ISO/TR 17185-3:2015, 3.17; ISO/TR 25102, modified]
4 Symbols and abbreviated terms
4.1 Symbols
This document does not contain any symbols.
4.2 Abbreviated terms
For the purposes of this document, the following abbreviated terms apply.
API application programming interface
BIM building information modelling
bSDD buildingSmart data dictionary
CWA closed world assumption
ECMA European computer manufacturers association international
EDM electronic document management
EIF European interoperability framework
11
---------------------- Page: 13 ----------------------
SIST EN 17632-1:2023
EN 17632-1:2022 (E)
EIR exchange information requirements
FAIR findable, accessible, interoperable, reusable [go-fair.org]
GIS geographical information systems
GUID globally unique identifier (typically assigned)
ICDD information container for linked document delivery [ISO]
IDM information delivery manual
IFC industry foundation classes [ISO]
IETF internet engineering task force
JSON JavaScript object notation [ECMA]
JSON-LD JavaScript object notation - linked data [W3C]
LD linked data (technology) [W3C]
LoC level of capability
M&C monitoring & control
OMG object management group
OWA open world assumption
OWL web ontology language [W3C]
QUDT quantities, units, dimensions and data types [qudt.org]
RDF resource description framework [W3C]
RDFS resource description framework schema [W3C]
RFC request for comments [IETF]
SE systems engineering
SHACL shapes constraints language [W3C]
SML semantic modelling and linking [CEN]
SPARQL sparql protocol and RDF query language [W3C]
SPFF step physical file format [STEP]
SSoF single source of facts
STEP standard for the exchange of product model data [ISO]
SW semantic web (technology) [W3C]
UML unified modelling language [OMG]
URI uniform resource identifier [W3C]
UUID universally unique identifier [IETF]
XML extensible markup language [W3C]
XSD extensible markup language schema definition [W3C]
W3C world wide web consortium
WWW world wide web [W3C]
12
---------------------- Page: 14 ----------------------
SIST EN 17632-1:2023
EN 17632-1:2022 (E)
5 Semantic modelling levels of capability
An appointing party shall define the levels of capability required for each use case.
Different use case types need different ‘levels of (semantic modelling) capability’ (LoC) related to the
required modelling power. This document specifies three main LoCs (Figure 2).
Figure 2 — Three use case types and related 'Levels of (semantic modelling) Capability’ (LoCs)'
The left part of Figure 2 represents the organizational use case type activity, the right side the related
(linked data) modelling languages available. The simplest use case type, requiring the weakest semantic
modelling, is the common understanding and alignment of terms and definitions used to describe assets,
their environment and internal structure. Weak modelling is sufficient here as a first step especially
targeted towards human in
...
SLOVENSKI STANDARD
oSIST prEN 17632:2021
01-maj-2021
Informacijsko modeliranje gradenj (BIM) - Semantični standard za modeliranje in
povezovanje (SML)
Building Information Modelling (BIM) - Semantic Modelling and Linking (SML)
Semantischer Modellierungs- und Verknüpfungsstandard (SMLS) für die
Datenintegration in der gebauten Umwelt
Modélisation d'informations de la construction (BIM) - Modélisation et liens sémantiques
(SML)
Ta slovenski standard je istoveten z: prEN 17632
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 17632:2021 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
oSIST prEN 17632:2021
---------------------- Page: 2 ----------------------
oSIST prEN 17632:2021
DRAFT
EUROPEAN STANDARD
prEN 17632
NORME EUROPÉENNE
EUROPÄISCHE NORM
March 2021
ICS 35.240.67
English Version
Building Information Modelling (BIM) - Semantic
Modelling and Linking (SML)
Modélisation d'informations de la construction (BIM) - Semantischer Modellierungs- und
Modélisation et liens sémantiques (SML) Verknüpfungsstandard (SMLS) für die
Datenintegration in der gebauten Umwelt
This draft European Standard is submitted to CEN members for enquiry. It has been drawn up by the Technical Committee
CEN/TC 442.
If this draft becomes a European Standard, 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.
This draft European Standard was established by CEN 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.
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.
Warning : This document is not a European Standard. It is distributed for review and comments. It is subject to change without
notice and shall not be referred to as a European Standard.
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
© 2021 CEN All rights of exploitation in any form and by any means reserved Ref. No. prEN 17632:2021 E
worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
oSIST prEN 17632:2021
prEN 17632:2021 (E)
Contents Page
European foreword . 4
Introduction . 5
1 Scope . 7
2 Normative references . 8
3 Terms and definitions . 9
4 Symbols and abbreviated terms . 12
4.1 Symbols . 12
4.2 Abbreviated terms . 12
5 Levels of Capability . 14
6 Conceptual L1: Data language . 15
7 Concrete L1: Data language bindings . 17
7.1 Introduction . 17
7.2 Identification: URI strategy . 20
7.3 Naming conventions . 22
7.4 Annotation . 22
7.5 Enumeration datatypes . 23
7.6 Decomposition (instance level) . 24
7.7 Quantity kinds & units . 24
7.8 Quantity modelling . 24
7.9 Grouping. 25
8 Generic M1: Top level data model . 25
8.1 Top level model . 25
8.2 Systems engineering extension . 29
9 Implementing SML in code . 31
10 Linking data . 31
10.1 Types of linking . 31
10.2 Language-level language link sets . 32
11 Conformance . 33
11.1 General. 33
11.2 Conformance on language level . 33
11.3 Conformance on semantic level . 33
Annex A (normative) Conceptual data language and top level data model . 34
A.1 General. 34
A.2 in SKOS (Turtle format) . 34
A.3 in RDFS (Turtle format) . 41
A.4 in OWL (Turtle format) . 51
A.5 in SHACL (Turtle format) . 64
Annex B (normative) Selected W3C RDF language subsets . 80
B.1 General. 80
B.2 XML schema part 2: Datatypes 2nd edition . 80
2
---------------------- Page: 4 ----------------------
oSIST prEN 17632:2021
prEN 17632:2021 (E)
B.3 Resource description framework (RDF) . 80
B.4 Simple knowledge organization system (SKOS) . 81
B.5 Resource description framework schema (RDFS) . 81
B.6 Web ontology language (OWL) . 82
B.7 Shape constraint language (SHACL) . 83
Annex C (informative) Example in SKOS . 86
C.1 General . 86
C.2 Example in SKOS (RDF/XML format) . 86
C.3 Example in SKOS (Turtle format) . 87
C.4 Example in SKOS (JSON-LD format) . 89
Annex D (informative) Example in RDFS . 93
D.1 General . 93
D.2 Example in RDFS (RDF/XML format) . 93
D.3 Example in RDFS (Turtle format) . 96
D.4 Example in RDFS (JSON-LD format) . 100
Annex E (informative) Example in OWL . 106
E.1 General . 106
E.2 Example in OWL (RDF/XML format) . 106
E.3 Example in OWL (Turtle format) . 109
E.4 Example in OWL (JSON-LD format) . 112
Annex F (informative) Example in SHACL . 120
F.1 General . 120
F.2 Example in SHACL (RDF/XML format) . 120
F.3 Example in SHACL (Turtle format) . 123
F.4 Example in SHACL (JSON-LD format) . 127
Annex G (informative) Relationships with other asset/product modelling standards . 136
G.1 General . 136
G.2 Relationship with ISO 21597 . 136
G.3 Relationship with ISO 23387 . 136
Bibliography . 155
3
---------------------- Page: 5 ----------------------
oSIST prEN 17632:2021
prEN 17632:2021 (E)
European foreword
This document (prEN 17632:2021) has been prepared by Technical Committee CEN/TC 422 “Building
Information Modelling (BIM)”, the secretariat of which is held by SN - Norway.
This document is currently submitted to the CEN Enquiry.
4
---------------------- Page: 6 ----------------------
oSIST prEN 17632:2021
prEN 17632:2021 (E)
Introduction
The built environment is the context of this document. In the life cycle of buildings or infrastructure its
assets need to be managed across their entire life cycle, involving programming, design, building and
operation (as defined by ISO 19650 series), and the supply chain producing and delivering them. Vast
amounts of valuable data about them are created, communicated in a diverse range of formats and data
structures - and often lost again. In order to manage the assets efficiently and effectively according to the
standards practised in asset management (as defined by ISO 55000 series), data needs to be findable,
1)
accessible, interoperable end reusable (FAIR) .
The world wide web consortium (W3C) provides so-called linked data (LD) and semantic web (SW)
technologies [1] which are capable of giving data common form (syntax) and meaning (semantics),
making data FAIR in a vendor neutral fashion.
The aim of this document is to standardize the application of this technology for the built environment in
order to enable the data becoming FAIR. This document specifies how the construction and software
industries apply this linked data and semantic web technology.
It hereby follows the principle to keep semantic modelling as simple and as standard as possible
(Table 1).
Table 1 — Aiming for standard and simple semantics
Semantic Standard Proprietary
Simple OK IF NEEDED
Complex IF NEEDED NOT OK
In others words, it is not the intention of this document to persuade anyone to shift the data structures
they already have in place. On the contrary, it is the suggestion of this document to store, model, publish
and link these data in a findable, accessible, interoperable and reusable manner (FAIR). To benefit the
industry from planning and design to construction and operation.
This document complements other ISO standards without any overlap. In the Annex G, related ISO
standards are listed and the exact relationship is described.
Application of this document to new or existing software will result in future proof, semantic data
interoperability that is interoperability so that the meaning of the data model within the context of a
subject area is understood by the participating systems [SOURCE: ISO/IEC 19941].
Furthermore, the data sets and data models become compatible, reusable, combinable and thereby
integrally applicable. This document enables decision making in and over every life cycle phase and the
supply chain involved.
1) A common principle by go-fair.org in today’s data management.
5
---------------------- Page: 7 ----------------------
oSIST prEN 17632:2021
prEN 17632:2021 (E)
Data management in the built environment is characterized by three main categories:
• Terms and definitions of data (on object level and attribute level);
• Data exchange (transfer of data from one party to another party) and data sharing (publishing of data
by one party where it can be accessed by other parties);
• Data integration involving linking all data together.
For each of these categories the interoperability approaches apply, as defined by the enterprise
interoperability framework (EIF) (ISO 11354-1):
1. Unified approach, featuring some common meta-model;
2. Integrated approach, featuring some common forms;
3. Federated approach, no common forms or meta-model but dynamic accommodation/adjustment.
These approaches, according to the EIF, are valid for business, process, service and data aspects.
6
---------------------- Page: 8 ----------------------
oSIST prEN 17632:2021
prEN 17632:2021 (E)
1 Scope
This document discusses an integrated and unified approach for data aspects, specifically for assets in
the built environment, using EIF terminology.
The following data architecture (Figure 1) applies within each category.
Figure 1 — Data architecture with typology (grey areas indicating the scope of this document)
This document specifies:
• a generic Top Level “M1: Data model” as common form;
• a conceptual “L1: Data language” as common meta-model with four ‘linked data’-based concrete
language bindings (SKOS, RDFS, OWL and SHACL), including:
• a choice of RDF-based formats (to be used for all modelling and language levels);
• a set of data modelling patterns (for identification, naming, handling of enumeration types,
quantity modelling, asset decomposition, grouping, etc.).
• a linking approach for interlinking data sets, interlinking data models and linking data sets and data
models which are relevant within the built environment from many perspectives such as:
• Building information modelling (BIM);
• Geo-spatial information systems (GIS);
2)
• Systems engineering (SE) ;
• Monitoring & control (M&C);
• Electronic document management (EDM).
This document does not specify a knowledge model since this is already available in ISO 12006-3.
2) The interdisciplinary approach governing the total technical and managerial effort required to transform a set of
stakeholder needs, expectations, and constraints into a solution and to support that solution throughout its life
[SOURCE: ISO/IEC/IEEE 12207:2017(en), 3.1.65].
7
---------------------- Page: 9 ----------------------
oSIST prEN 17632:2021
prEN 17632:2021 (E)
This document does not specify a meta-‘data language’ since this is already provided by the concrete RDF
language bindings (being RDFS).
The scope of this document in general excludes the following:
• Business process modelling;
• Software implementation aspects;
• Data packaging and transportation/transaction aspects (handled by ISO TC59/SC13 Information
container for document delivery (ICDD) respectively various information delivery manual (IDM) /
information exchange requirements (EIR)-related initiatives);
• Domain-specific (here: built environment-specific) content modelling in the form of concepts,
attributes and relations at end-user level (the actual ontologies themselves) beyond a generic upper
ontology and modelling patterns.
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 for this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
JSON-LD 1.1, A JSON-based Serialization for Linked Data, W3C Candidate Recommendation, 17 April
2020, https://www.w3.org/TR/json-ld11/
3)
OWL 2 Web Ontology Language, Document Overview (Second Edition), W3C Recommendation,
11 December 2012, https://www.w3.org/TR/2012/REC-owl2-overview-20121211/
RDF 1.1 Concepts and Abstract Syntax, W3C Recommendation, 25 February 2014,
https://www.w3.org/TR/rdf11-concepts/
RDF 1.1 Turtle, W3C Recommendation, 25 February 2014, https://www.w3.org/TR/turtle/
RDF 1.1 XML Syntax, W3C Recommendation 25 February 2014, https://www.w3.org/TR/rdf-syntax-
grammar/
RDF Schema 1.1, W3C Recommendation, 25 February 2014, https://www.w3.org/TR/rdf-schema/
SHACL (Shapes Constraint Language), W3C Recommendation, 20 July 2017,
https://www.w3.org/TR/shacl/
SKOS Simple Knowledge Organization System Reference, W3C Recommendation, 18 August 2009,
https://www.w3.org/TR/skos-reference/
SPARQL 1.1 Overview, 21 March 2013, W3C Recommendation,
https://www.w3.org/TR/sparql11-overview/ (referencing, among others, the next two, more specific,
references)
SPARQL 1.1 Query Language, W3C Recommendation, 21 March 2013,
https://www.w3.org/TR/2013/REC-sparql11-query-20130321/
3) From now referred to as just “OWL”.
8
---------------------- Page: 10 ----------------------
oSIST prEN 17632:2021
prEN 17632:2021 (E)
SPARQL 1.1 Protocol, W3C Recommendation, 21 March 2013, https://www.w3.org/TR/sparql11-
protocol/
XML Schema Part 2: Datatypes, Second Edition, W3C Recommendation, 28 October 2004,
https://www.w3.org/TR/xmlschema-2/
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 6707-1 and the following 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.1
asset
item, thing or entity that has potential or actual value to an organization
[SOURCE: ISO 55000:2014, 3.2.1, modified — Note 1, 2 and 3 to entry have been removed.]
3.2
machine-readable
able to be read and processed by a computer
3.3
machine-interpretable
able to be semantically interpreted by a computer
3.4
level of capability
LoC
level of semantic level modelling power within a data model to fulfil a use case type
3.5
format
predetermined arrangement of data on a data medium
[SOURCE: ISO 5127:2017, 3.1.13.12]
3.6
ontology
formal, explicit specification of a shared conceptualization
Note 1 to entry: An ontology typically includes definitions of concepts and specified relationships between them,
set out in a formal way so that a machine can use them for reasoning.
Note 2 to entry: Applied in this document as a set of concepts, (reference) individuals, value types, (reference)
values, attributes, relations, constraints and derivations.
[SOURCE: ISO 5127:2017, 3.1.2.03, modified — added Note 2 to entry]
9
---------------------- Page: 11 ----------------------
oSIST prEN 17632:2021
prEN 17632:2021 (E)
3.7
typology
hierarchy related to classification/instantiation relations
[SOURCE: ISO/IEC 11179-3:2013, 3.2.135, modified — The words "type of" have been removed. The
words "which deals with" have been changed to "related to". The word relationships has been changed
to relations.]
3.8
taxonomy
hierarchy related to generalization/specialization relations
[SOURCE: ISO/IEC 11179-3:2013, 3.2.135, modified — The words "type of" have been removed. The
words "which deals with" have been changed to "related to". The word relationships has been changed
to relations. Not mixing concepts, attributes and relations.]
3.9
meronomy
hierarchy related to part-whole (decomposition) relations
[SOURCE: ISO/IEC 11179-3:2013, 3.2.135, modified — The words "type of" have been removed. The
words "which deals with" have been changed to "related to". The word relationships has been changed
to relations.]
3.10
built environment
collection of man-made or induced physical objects located in a particular area or region
[SOURCE: ISO 6707-3:2017, 3.1.3]
3.11
triple
statement in the form subject-predicate-object that expresses a relation
3.12
level of capability
modelling power related to the needs of a specific use case type, provided by the linked data languages
3.13
object
any part of the perceivable or conceivable world
Note 1 to entry: An object is something abstract or physical toward which thought, feeling, or action is directed.
Note 2 to entry: Within this draft, the terms instance and individual, are used as synonyms of object.
[SOURCE: ISO 12006-2:2015, 3.1.1, modified — added Note 2 to entry.]
10
---------------------- Page: 12 ----------------------
oSIST prEN 17632:2021
prEN 17632:2021 (E)
3.14
concept
abstract entity for determining category membership
[SOURCE: ISO/IEC 2382 :2015, 2122971]
3.15
property
inherent or acquired feature of an object
3.16
attribute
data element for the computer-sensible description of a property, a relation or a class
[SOURCE ISO 22274:2013, 3.2]
3.17
relation
sense in which concepts can be connected, via constituent roles
EXAMPLE Causality is a relation with two constituent roles: cause and effect.
[SOURCE: ISO/IEC 11179-3:2013, 3.2.119]
3.18
data set
group of data instances directly specifying or describing something you can or could point at in reality
3.19
data model
specification/description of the organization of data giving meaning (semantics) to a data set
3.20
exchange information requirement
EIR
information requirement in relation to an appointment
[SOURCE: ISO 19650-1:2018. 3.3.6]
3.21
systems engineering
SE
interdisciplinary approach governing the total technical and managerial effort required to transform a
set of stakeholder needs, expectations, and constraints into a solution and to support that solution
throughout its life
[SOURCE: ISO/IEC/IEEE 12207:2017, 3.1.65]
11
---------------------- Page: 13 ----------------------
oSIST prEN 17632:2021
prEN 17632:2021 (E)
3.22
metadata
data about data (documents, data sets, data models or elements in those)
3.23
top level data model
most generic taxonomy as part of a data model
4 Symbols and abbreviated terms
4.1 Symbols
This document does not contain any symbols.
4.2 Abbreviated terms
For the purposes of this document, the following abbreviated terms apply.
API application programming interface
BIM building information modelling
DT data template [CEN TC 442]
ECMA European computer manufacturers association international
EDM electronic data management
EIF enterprise interoperability framework
EIR exchange information requirements
FAIR findable, accessible, interoperable, reusable [go-fair.org]
FO functional object
GIS geo-spatial information systems
GUID globally unique identifier (typically assigned)
ICDD information container for linked document delivery [ISO]
ID identifier
IDM information delivery manual
IFC industry foundation classes [ISO]
IETF internet engineering task force
IO imaginary object
JSON JavaScript object notation [ECMA]
JSON-LD JavaScript object notation - linked data [W3C]
LBD CG linked building data community group [W3C]
12
---------------------- Page: 14 ----------------------
oSIST prEN 17632:2021
prEN 17632:2021 (E)
LD linked data technology [W3C]
LoC level of capability
M&C monitoring & control
OMG object management group
OWL web ontology language [W3C]
QUDT quantities, units & data types [qudt.org]
RDF resource description framework [W3C]
RDFS resource description framework schema [W3C]
RFC request for comments [IETF]
RO real object
SE systems engineering
SHACL shapes constraints language [W3C]
SML semantic modelling and linking [CEN]
SPARQL SPARQL protocol and RDF query language [W3C]
SPFF STEP physical file format [STEP]
STEP standard for the exchange of product model data [ISO]
SSoF single source of facts
SW semantic web technology [W3C]
TO technical object
UML unified modelling language [OMG]
URI uniform resource identifier [W3C]
UUID universally unique identifier [IETF]
XML extensible markup language [W3C]
XSD extensible markup language schema definition [W3C]
W3C world wide web consortium
WWW world wide web [W3C]
13
---------------------- Page: 15 ----------------------
oSIST prEN 17632:2021
prEN 17632:2021 (E)
5 Levels of Capability
Different use case types need a specification for different levels of capability (LoC) related to the required
modelling power. This document specifies three main LoCs (Figure 2):
Figure 2 — Three main use case types and related 'Levels of Capability (LoCs)'
The left/grey part of the figure represents the business side, the right/orange side the modelling language
used. The simplest use case type requiring the weakest semantic modelling is the common understanding
and alignment of terms and definitions used to describe assets, their environment and internal structure.
Weak modelling is sufficient here as a first step for human interpretation. A good definition gives an end
user guidance on how to later classify and instantiate their data according to these terms. This level
targets mainly uniformity in human understanding of terms and definitions and at least making sure the
data is machine-processable, with the lowest level of capabilit
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.