BS EN 17632-1:2022
$165.47
Building information modelling (BIM). Semantic modelling and linking (SML) – Generic modelling patterns
Published By | Publication Date | Number of Pages |
BSI | 2022 | 100 |
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. 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). 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.
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | undefined |
8 | 1 Scope |
9 | 2 Normative references |
10 | 3 Terms and definitions |
13 | 4 Symbols and abbreviated terms 4.1 Symbols 4.2 Abbreviated terms |
15 | 5 Semantic modelling levels of capability |
16 | 6 L1: Information language 6.1 Conceptual L1: Information language |
18 | 6.2 Concrete L1: Information language bindings |
21 | 6.3 Modelling patterns 6.3.1 General 6.3.2 Identification via URI strategy |
22 | 6.3.3 Combining language bindings |
25 | 6.3.4 Naming |
26 | 6.3.5 Annotation |
27 | 6.3.6 Types |
28 | 6.3.7 Decomposition (instance level) 6.3.8 Quantity kinds & units |
29 | 6.3.9 Complex properties |
30 | 7 M1: Information model 7.1 Top level information model |
32 | 7.2 Systems engineering extension |
34 | 8 Implementing SML in code 9 Conformance 9.1 General 9.2 Conformance on language level |
35 | 9.3 Conformance on semantic level |
36 | Annex A (normative)SML implementation in ‘linked data’ A.1 Introduction A.2 SKOS part |
42 | A.3 RDFS part |
50 | A.4 OWL part |
55 | A.5 SHACL part |
60 | Annex B (normative)Selected W3C RDF language subsets B.1 General B.2 XML schema (XSD), part 2: Datatypes 2nd edition B.3 Resource description framework (RDF) |
61 | B.4 Simple knowledge organization system (SKOS) B.5 Resource description framework schema (RDFS) |
62 | B.6 Web ontology language (OWL) |
63 | B.7 Shape constraint language (SHACL) |
66 | Annex C (informative)SML Example in SKOS/RDFS/OWL/SHACL (Turtle format) C.1 Example description C.2 SKOS part |
68 | C.3 RDFS part |
71 | C.4 OWL part |
72 | C.5 SHACL part |
73 | C.6 Data part |
75 | Annex D (informative)Relationships with other asset/product modelling standards D.1 General D.2 Relationship with the ISO 21597 series D.3 Relationship with EN ISO 23387 D.3.1 Introduction |
76 | D.3.2 Modelling relationship with EN ISO 12006-3 D.3.3 Example Schweizerische Zentralstelle für Baurationalisierung (CRB) |
89 | D.3.4 Full CRB code example in RDFS/SHACL (in Turtle format) |
94 | D.4 Relationship with the ISO 15926 series |
96 | Annex E (informative)Linking information E.1 Types of linking E.2 Language-level language link sets |