SIST EN ISO 12006-3:2022
(Main)Building construction - Organization of information about construction works - Part 3: Framework for object-oriented information (ISO 12006-3:2022)
Building construction - Organization of information about construction works - Part 3: Framework for object-oriented information (ISO 12006-3:2022)
This document specifies a language-independent information model which can be used for the development of dictionaries used to store or provide information about construction works. The model is extended by instantiating content, such as further objects and their relationships, allowing the content to serve as an ontology, taxonomy, meronomy, lexicon and thesaurus.
NOTE 1 Lexicons are resources for comprising lexical entries for a given language
NOTE 2 Meronomies are type of hierarchies which deals with part-whole relationships
NOTE 3 Ontologies are formal, explicit specification of a shared conceptualizationIt enables classification systems, information models, object models, data templates and process models to be cross-referenced from within a common framework.
This document provides the description of an API allowing the interconnection of data dictionaries as described in ISO 23386.
Bauwesen - Organisation von Daten zu Bauwerken - Teil 3: Struktur für den objektorientierten Informationsaustausch (ISO 12006-3:2022)
Construction immobilière - Organisation de l'information des travaux de construction - Partie 3: Schéma pour l'information basée sur l'objet (ISO 12006-3:2022)
Le présent document spécifie un modèle de données indépendant du langage, qui peut être utilisé pour le développement de dictionnaires servant à stocker ou fournir des informations concernant des ouvrages de construction. Le modèle est étendu par l'instanciation de contenu, tel que des objets et leurs relations, pour permettre d'utiliser le contenu sous forme d'ontologie, de taxonomie, de méronomie, de lexique et de thésaurus.
NOTE 1 Les lexiques sont des ressources qui permettent de comprendre les entrées lexicales d'un langage donné.
NOTE 2 Les méronomies sont des types de hiérarchies qui traitent des relations partie-tout.
NOTE 3 Les ontologies sont des spécifications formelles et explicites d'une conceptualisation partagée.
Il permet d'effectuer des références croisées entre des systèmes de classification, des schémas de données, des modèles d'objet, des modèles de données et des modèles de processus à partir d'un cadre commun.
Le présent document fournit la description d'une API permettant d'établir une interconnexion entre des dictionnaires de données décrits dans l'ISO 23386.
Gradnja objektov - Organizacija podatkov o gradbenih delih - 3. del: Okvirna struktura objektno orientiranih podatkov (ISO 12006-3:2022)
Ta dokument določa jezikovno neodvisen informacijski model, ki ga je mogoče uporabiti pri razvoju slovarjev za hrambo ali zagotavljanje podatkov o gradbenih delih. Model je razširjen z vzpostavitvijo vsebine, kot so nadaljnji objekti in njihova razmerja, zaradi česar se lahko vsebina uporablja kot ontologija, taksonomija, meronomija, leksikon in tezaver. OPOMBA 1: Leksikon je vir za vključitev leksikalnih vnosov za določen jezik.
OPOMBA 2: Meronomija je vrsta hierarhije, ki obravnava razmerje med delom in celoto.
OPOMBA 3: Ontologija je formalna, eksplicitna specifikacija skupne konceptualizacije, ki omogoča navzkrižno sklicevanje sistemov razvrščanja, informacijskih modelov, objektnih modelov, podatkovnih predlog in procesnih modelov znotraj skupnega okvirja. Ta dokument podaja opis programskega vmesnika (API), ki omogoča medsebojno povezavo podatkovnih slovarjev, kot je opisano v standardu ISO 23386.
General Information
Relations
Standards Content (Sample)
SLOVENSKI STANDARD
01-oktober-2022
Nadomešča:
SIST EN ISO 12006-3:2016
Gradnja objektov - Organizacija podatkov o gradbenih delih - 3. del: Okvirna
struktura objektno orientiranih podatkov (ISO 12006-3:2022)
Building construction - Organization of information about construction works - Part 3:
Framework for object-oriented information (ISO 12006-3:2022)
Bauwesen - Organisation von Daten zu Bauwerken - Teil 3: Struktur für den
objektorientierten Informationsaustausch (ISO 12006-3:2022)
Construction immobilière - Organisation de l'information des travaux de construction -
Partie 3: Schéma pour l'information basée sur l'objet (ISO 12006-3:2022)
Ta slovenski standard je istoveten z: EN ISO 12006-3: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
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
EN ISO 12006-3
EUROPEAN STANDARD
NORME EUROPÉENNE
August 2022
EUROPÄISCHE NORM
ICS 91.010.01 Supersedes EN ISO 12006-3:2016
English Version
Building construction - Organization of information about
construction works - Part 3: Framework for object-
oriented information (ISO 12006-3:2022)
Construction immobilière - Organisation de Bauwesen - Organisation von Daten zu Bauwerken -
l'information des travaux de construction - Partie 3: Teil 3: Struktur für den objektorientierten
Schéma pour l'information basée sur l'objet (ISO Informationsaustausch (ISO 12006-3:2022)
12006-3:2022)
This European Standard was approved by CEN on 7 June 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 ISO 12006-3:2022 E
worldwide for CEN national Members.
Contents Page
European foreword . 3
European foreword
This document (EN ISO 12006-3:2022) 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 February 2023, and conflicting national standards
shall be withdrawn at the latest by February 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.
This document supersedes EN ISO 12006-3:2016.
Any feedback and questions on this document should be directed to the users’ national standards
body/national committee. A complete listing of these bodies can be found on the CEN website.
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, Türkiye and the
United Kingdom.
Endorsement notice
The text of ISO 12006-3:2022 has been approved by CEN as EN ISO 12006-3:2022 without any
modification.
INTERNATIONAL ISO
STANDARD 12006-3
Second edition
2022-07
Building construction — Organization
of information about construction
works —
Part 3:
Framework for object-oriented
information
Construction immobilière — Organisation de l'information des
travaux de construction —
Partie 3: Schéma pour l'information basée sur l'objet
Reference number
ISO 12006-3:2022(E)
ISO 12006-3:2022(E)
© ISO 2022
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 12006-3:2022(E)
Contents Page
Foreword .v
Introduction . vi
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Language encoding .2
5 Specification . 2
5.1 General . 2
5.2 EXPRESS-G specification . 3
5.3 EXPRESS specification . 7
5.3.1 General . 7
5.3.2 xtdDateTime . 7
5.3.3 xtdUUID . 7
5.3.4 xtdDataTypeEnum . 7
5.3.5 xtdExternalStatusEnum . 8
5.3.6 xtdInternalStatusEnum . 8
5.3.7 xtdNatureOfChangeEnum . 9
5.3.8 xtdPropertyRelationshipTypeEnum . 9
5.3.9 xtdRelationshipKindEnum . 10
5.3.10 xtdRoleEnum . 10
5.3.11 xtdStatusOfActivationEnum . 10
5.3.12 xtdUnitBaseEnum . . 11
5.3.13 xtdUnitScaleEnum . 11
5.3.14 xtdChangeRequest . 11
5.3.15 xtdConcept .12
5.3.16 xtdCountry .13
5.3.17 xtdDictionary . 13
5.3.18 xtdDimension . 13
5.3.19 xtdExpert . 14
5.3.20 xtdExpertWithStatus . 14
5.3.21 xtdExternalDocument . 15
5.3.22 xtdFilter . 15
5.3.23 xtdInterval . 16
5.3.24 xtdLanguage . 16
5.3.25 xtdMedia . 17
5.3.26 xtdMultiLanguageText . 17
5.3.27 xtdObject . 18
5.3.28 xtdOrderedValue . 19
5.3.29 xtdProperty . 19
5.3.30 xtdQuantityKind .20
5.3.31 xtdRational . 21
5.3.32 xtdRelationshipToProperty . 21
5.3.33 xtdRelationshipToSubject . 21
5.3.34 xtdRelationshipType . 22
5.3.35 xtdRoot . .22
5.3.36 xtdSubdivision.23
5.3.37 xtdSubject .23
5.3.38 xtdSymbol. 24
5.3.39 xtdText . 24
5.3.40 xtdUnit . 24
5.3.41 xtdUser . 25
5.3.42 xtdUserWithRoles .25
iii
ISO 12006-3:2022(E)
5.3.43 xtdValue. 26
5.3.44 xtdValueList .26
5.3.45 xtdVisualRepresentation . 27
6 Application programming interface (API) .27
7 XML representations .27
Annex A (normative) EXPRESS long form specification .28
Annex B (normative) Application programming interface specification.29
Annex C (informative) UML representation .30
Annex D (informative) XSD representation of the schema .33
Annex E (informative) Naming conventions .34
Annex F (informative) Examples .35
Bibliography .43
iv
ISO 12006-3:2022(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 of information about construction works, 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).
This second edition cancels and replaces the first edition (ISO 12006:2007), which has been technically
revised.
The main changes are as follows:
— model has been changed and adapted for multiple implementations of dictionaries;
— UML and XML have been introduced in informative annexes;
— API specification has been included;
— relationships among concepts have been made mandatory and concepts have been made more rigid,
specific and object-oriented.
A list of all parts in the ISO 12006 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.
v
ISO 12006-3:2022(E)
Introduction
This document defines a specification for an extensible taxonomy model, which provides the ability
to add concepts like subjects and properties, describe subject by means of properties, and to define
relationships between concepts. The set of properties associated with a subject provide the formal
definition of the subject as well as its typical behaviour. Properties can have predefined values; and
they can be associated with units.
The model makes it possible to describe multiple dictionaries based on the same model. Each concept
belongs to one data dictionary. The concepts in one data dictionary can be related to concepts in another
data dictionary.
Every entity in the model has a universal unique identifier. The model allows users to describe the
development and maintenance of a data dictionary by providing change requests; and it also allows
describing the experts reviewing change requests. The model described in this document is proposed
as a bridge between classification systems as described in ISO 12006-2 and product modelling as
described in ISO 10303-41, ISO 10303-221, ISO 15926-2 and ISO 16739-1.
This document supports the requirements for implementing the concepts described in ISO 23386 and
ISO 23387. Not all the concepts from ISO 23386 are provided by the model described in this document.
To simplify and support implementation of dictionaries based on this framework, This document
[10] [11]
includes UML model and XML schema as Annexes C and D respectively. An API specification is
added as Annex B to standardize and define the minimum functionality to extract and exchange data
between dictionaries based on this document.
vi
INTERNATIONAL STANDARD ISO 12006-3:2022(E)
Building construction — Organization of information
about construction works —
Part 3:
Framework for object-oriented information
1 Scope
This document specifies a language-independent information model which can be used for the
development of dictionaries used to store or provide information about construction works. The model
is extended by instantiating content, such as further objects and their relationships, allowing the
content to serve as an ontology, taxonomy, meronomy, lexicon and thesaurus.
NOTE 1 Lexicons are resources for comprising lexical entries for a given language
NOTE 2 Meronomies are type of hierarchies which deals with part-whole relationships
NOTE 3 Ontologies are formal, explicit specification of a shared conceptualizationIt enables classification
systems, information models, object models, data templates and process models to be cross-referenced from
within a common framework.
This document provides the description of an API allowing the interconnection of data dictionaries as
described in ISO 23386.
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 80000 (all parts), Quantities and units
ISO 639 (all parts), Codes for the representation of names of languages
ISO/IEC 10646, Information technology — Universal coded character set (UCS)
ISO/IEC 9834-8,2014, Information technology — Procedures for the operation of object identifier
registration authorities — Part 8: Generation of universally unique identifiers (UUIDs) and their use in
object identifiers
ISO/IEC 20802-1, Information technology — Open data protocol (OData) v4.0 — Part 1: Core
ISO/IEC 20802-2, Information technology — Open data protocol (OData) v4.0 — Part 2: OData JSON
Format
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminology 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/
ISO 12006-3:2022(E)
3.1
data dictionary
database that contains metadata
[SOURCE: ISO 2382, 2121501, modified — The admitted term "information resource dictionary" has
been removed. The Notes to entry have been removed.]
3.2
classification
process of assigning objects (3.4) to classes according to criteria
[SOURCE: ISO 22274:2013, 3.5]
3.3
data template
data structure used to describe the characteristics of construction objects (3.4)
[SOURCE: ISO 23387:2020, 3.3, modified — Exampless and Notes to entry have been removed.]
3.4
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.
[SOURCE: ISO 12006-2:2015, 3.1.1]
3.5
property
defined characteristic suitable for the description and differentiation of the objects (3.4) in a class
[SOURCE: ISO 22274:2013, 3.25, modified - Example removed.]
3.6
attribute
data element for the computer-sensible description of a property (3.5), a relation or a class
EXAMPLE Creation date of a class object in a computer system.
[SOURCE: ISO ISO 22274:2013, 3.2]
4 Language encoding
All information that is specified as type “String”, or that resolves to type “String”, shall be able to be
expressed using the UNICODE character set (see ISO 23386) as set out in ISO/IEC 10646, preferably
using the UTF-8 encoding form, the UTF-8 encoding scheme and the “UCS Transformation Format 8”.
5 Specification
5.1 General
The model in this document is specified using the EXPRESS data definition language according to
ISO 10303-11.
The model is described informally in 5.2, conforming to the EXPRESS-G notation.
The model is described formally in the EXPRESS language specification presented in 5.3 and as an
EXPRESS long form specification in Annex A.
NOTE ISO 10303-28, ISO/TS 10303-25 and ISO 10303-22 specify mappings to XML and XMI representations
and an API respectively.
ISO 12006-3:2022(E)
5.2 EXPRESS-G specification
The informal EXPRESS-G specification that uses the EXPRESS-G notation is given in three diagrams
(Figures 1 to 3), where each diagram specifies a part of the model. All entities in these diagrams are
specified formally in 5.3.
— Figure 1 shows the diagram with abstact object of xtdRoot, its attributes and its derived types
xtdDictionary, xtdExpertWithStatus, xtdInterval, xtdLanguage, xtdMedia, xtdMultiLanguageText,
xtdObject, xtdRational, xtdSymbol, xtdText, xtdUser and xtdUserWithRoles and its subtypes.
— Figure 2 shows the diagram with abstract object of xtdObject, its attribues and its derived types
xtdConcept, xtdOrderedValue, xtdChangeRequest, xtdValue, xtdRelationahipToSubject and its
subtypes.
— Figure 3 shows the diagram with abstract type of xtdConcept, its attributes and its derived types
xtdFilter, xtdCountry, xtdSubdivision, xtdDimension, xtdRelationshipType, xtdExternalDocument,
xtdVisualRepresentation, xtdUnit, xtdValueList, xtdRelationshipToProperty, xtdSubject,
xtdProperty and its subtypes.
ISO 12006-3:2022(E)
Figure 1 — EXPRESS-G diagram 1 — Top level with root concept
ISO 12006-3:2022(E)
Figure 2 — EXPRESS-G diagram 2 — xtdObject representation
ISO 12006-3:2022(E)
Figure 3 — EXPRESS-G diagram 3 — xtdConcept representation
ISO 12006-3:2022(E)
5.3 EXPRESS specification
5.3.1 General
This formal specification is provided in the EXPRESS language.
The EXPRESS long form specification is provided in Annex A.
Express Specification
(*
ISO_12006_3_VERSION_4
EXPRESS specification:
*)
SCHEMA ISO_12006_3_VERSION_4;
(*
5.3.2 xtdDateTime
xtdDateTime is a defined data type of simple data type STRING that is used to identify a particular
point in time. The date format (the ISO 8601 series) “YYYY -MM -DDThh: mm: ssTZD” should be used.
EXAMPLE The 31st day of May in the year 2000 is written as “2000-05-31T00:00:00Z”.
EXPRESS specification:
*)
Type xtdDateTime = STRING;
END_TYPE;
(*
5.3.3 xtdUUID
xtdUUID is a defined data type of simple data type STRING that holds an identifier that is universally
unique.
xtdUUID shall be generated according to ISO/IEC 9834-8, and it shall be provided according to the
hexadecimal representation ISO/IEC 9834-8:2014, 6.5.
EXAMPLE The 36-character string 1cbeacb2-7449-4671-97d2-3b84def86927 is a universally unique
identifier.
EXPRESS specification:
*)
TYPE xtdUUID = STRING (36) FIXED;
END_TYPE;
(*
5.3.4 xtdDataTypeEnum
xtdDataTypeEnum is an enumeration type giving the range of possible simple data types from which a
selection can be made. Allowed selections are:
XTD_BOOLEAN Datatype associated with two-valued logic.
XTD_INTEGER Datatype to specify a numeric value without a fractional component.
XTD_RATIONAL Datatype to specify a number that can be expressed as the fraction of two integers.
XTD_REAL Datatype to specify a number that may be represented by a finite or infinite numeral
in a fixed radix numeration system.
ISO 12006-3:2022(E)
XTD_COMPLEX Datatype to specify a number that can be expressed in the form a+bi, where a and b
are real numbers, and i is the imaginary unit.
XTD_STRING Datatype to express a sequence of characters.
XTD_DATETIME Datatype to specify a date and a time.
EXPRESS specification:
*)
TYPE xtdDataTypeEnum = ENUMERATION OF
(XTD_BOOLEAN,
XTD_INTEGER,
XTD_RATIONAL,
XTD_REAL,
XTD_COMPLEX,
XTD_STRING,
XTD_DATETIME);
END_TYPE;
(*
5.3.5 xtdExternalStatusEnum
xtdExternalStatusEnum is an enumeration type giving the range of possible values to describe the
status of a change request in its validation’s process. Allowed selections are:
XTD_PENDING_ASSIGNMENT The change request has been created; no expert has been
yet assigned to it.
XTD_UNDERGOING_ANALYSIS The experts assigned to the change request are analysing it.
XTD_PENDING_INFORMATION_REQUEST One or several experts assigned to the change request have
requested more information to be able to give an answer.
XTD_VALIDATED The change request has been validated.
XTD_REJECTED The change request has been rejected.
EXPRESS specification:
*)
TYPE xtdExternalStatusEnum = ENUMERATION OF
(XTD_PENDING_ASSIGNEMENT,
XTD_UNDERGOING_ANALYSIS,
XTD_PENDING_INFORMATION_REQUEST,
XTD_VALIDATED,
XTD_REJECTED);
END_TYPE;
(*
NOTE “XTD_PENDING_INFORMATION_REQUEST” corresponds to “Complementary information request” in
ISO 23386:2020, RA005.
5.3.6 xtdInternalStatusEnum
xtdInternalStatusEnum is an enumeration type giving the range of possible values to describe the
status of a change request for an expert assigned to it. Allowed selections are:
XTD_UNDERGOING_ANALYSIS The expert is currently analysing the change request.
ISO 12006-3:2022(E)
XTD_PENDING_INFORMATION_REQUEST The expert has requested more information before giving
its decision on the change request.
XTD_NOT_COMPETENT The expert has declared itself not competent to analyse
the change request.
XTD_VALIDATED The expert has validated the change request.
XTD_REJECTED The expert has rejected the change request.
EXPRESS specification:
*)
TYPE xtdInternalStatusEnum = ENUMERATION OF
(XTD_UNDERGOING_ANALYSIS,
XTD_PENDING_INFORMATION_REQUEST,
XTD_NOT_COMPETENT,
XTD_VALIDATED,
XTD_REJECTED);
END_TYPE;
(*
5.3.7 xtdNatureOfChangeEnum
xtdNatureOfChangeEnum is an enumeration type giving the range of possible values to describe the
nature of a change request. Allowed selections are:
XTD_SIMPLE_CREATION The creation of a new concept is requested.
XTD_SIMPLE_MODIFICATION The modification of a concept is required.
XTD_SIMPLE_DEACTIVATION The deactivation of a concept is required.
XTD_REPLACEMENT The replacement of a concept by another one is requested.
XTYD_FRAGMENTATION The replacement of a concept by several others is requested.
XTD_MERGING The replacement of several concepts by one concept is requested.
EXPRESS specification:
*)
TYPE xtdNatureOfChangeEnum = ENUMERATION OF
(XTD_SIMPLE_CREATION,
XTD_SIMPLE_MODIFICATION,
XTD_SIMPLE_DEACTIVATION,
XTD_REPLACEMENT,
XTD_FRAGMENTATION,
XTD_MERGING);
END_TYPE;
(*
5.3.8 xtdPropertyRelationshipTypeEnum
xtdPropertyRelationshipTypeEnum is an enumeration type giving the range of possible relationships
between two properties. Allowed selections are:
XTD_DEPENDS A property is dependent on others.
XTD_SPECIALIZES A property is the specialization of another property.
EXPRESS specification:
*)
TYPE xtdPropertyRelationshipTypeEnum = ENUMERATION OF
(XTD_DEPENDS,
ISO 12006-3:2022(E)
XTD_SPECIALIZES);
END_TYPE;
(*
5.3.9 xtdRelationshipKindEnum
Some kinds of relationships are only used for organizing the subjects. The bestknown example is the
classification hierarchy where generic classes (represented as subjects) are specialized in several more
specific classes/subjects. All real-world objects belong to the specific subjects; the generic subjects
are not instantiated. Thus, neither the generic subject nor the (parent) relationship between the
specific subjects and the generic subject are ever instantiated (see example in F.3). Rather, this kind of
relationship is only used at the schema level to organize elements of the data dictionary but not used as
a relationship between instances of the data dictionary.
On the other hand, there are relationships between subjects which may be instantiated. An example is
the part-of relationship between a composite product and its constituents (see example in F.3).
xtdRelationshipKindEnum is an enumeration type that specifies whether the relationship is
instantiatiable or whether it is only visible at the data dictionary level. The two possible values are
SchemaLevel and InstanceLevel.
XTD_INSTANCE_LEVEL The relationship can be instantiated.
XTD_SCHEMA_LEVEL The relationship cannot be instantiated and is used at the data dictionary level.
EXPRESS specification:
*)
TYPE xtdRelationshipKindEnum = ENUMERATION OF
(XTD_INSTANCE_LEVEL,
XTD_SCHEMA_LEVEL);
END_TYPE;
(*
5.3.10 xtdRoleEnum
xtdRoleEnum is an enumeration type giving the range of possible roles that can be attached to a user in
a data dictionary. Allowed selections are:
XTD_READER The user can only read the concepts present in the data dictionary.
XTD_CONTRIBUTOR The user can propose new content in the data dictionary.
XTD_EXPERT The user can validate change requests proposed by contributors.
XTD_ADMINISTRATOR The user can administrate the data dictionary and the users.
EXPRESS specification:
*)
TYPE xtdRoleEnum = ENUMERATION OF
(XTD_READER,
XTD_CONTRIBUTOR,
XTD_EXPERT,
XTD_ADMINISTRATOR);
END_TYPE;
(*
NOTE “XTD_CONTRIBUTOR” corresponds to “applicant” in ISO 23386:2020, 3.2.
5.3.11 xtdStatusOfActivationEnum
xtdStatusOfActivationEnum is an enumeration type giving the range of possible status for a concept
into a data dictionary. Allowed selections are:
ISO 12006-3:2022(E)
XTD_ACTIVE The corresponding concept is active in the data dictionary.
XTD_INACTIVE The corresponding concept is inactive in the data dictionary.
EXPRESS specification:
*)
TYPE xtdStatusOfActivationEnum = ENUMERATION OF
(XTD_ACTIVE,
XTD_INACTIVE);
END_TYPE;
(*
5.3.12 xtdUnitBaseEnum
xtdUnitBaseEnum is an enumeration type giving the list of possible conversion bases, either linear or
logarithmic. This list allows to use irrational values as bases.
See xtdUnit formula and explanations in 5.3.40.
EXPRESS specification:
*)
TYPE xtdUnitBaseEnum = ENUMERATION OF
(XTD_ONE,
XTD_TWO,
XTD_E,
XTD_PI,
XTD_TEN);
END_TYPE;
(*
5.3.13 xtdUnitScaleEnum
xtdUnitScaleEnum is an enumeration type which specifies whether a unit is of linear or logarithmic
scale.
See Formula (1) and (2) and explanations in 5.3.40.
EXPRESS specification:
*)
TYPE xtdUnitScaleEnum = ENUMERATION OF
(XTD_LINEAR,
XTD_LOGARITHMIC);
END_TYPE;
(*
5.3.14 xtdChangeRequest
xtdChangeRequest is a specialization of xtdObject used to provide a change request on any xtdConcept
in a data dictionary. A request corresponds to the creation, modification or deactivation of a concept.
For examples of requests of adding a property to a subject, see Annex F.
EXPRESS specification:
*)
ENTITY xtdChangeRequest
SUBTYPE OF(xtdObject);
Applicant : xtdUser;
NewObjects : SET[1:?] OF xtdObject;
Nature : xtdNatureOfChangeEnum;
RequestExternalStatus : xtdExternalStatusEnum;
Experts : OPTIONAL SET [1:?] OF xtdExpertWithStatus;
ApplicantExplanation : xtdMultiLanguageText;
END_ENTITY;
(*
ISO 12006-3:2022(E)
Attribute definitions:
Applicant User sending the change request.
NewObjects List of the new objects attached to the change request.
Nature Nature of the change request. See 5.3.7.
RequestExternalStatus Status of the request. See 5.3.5.
Experts List of the experts assigned to the change request.
ApplicantExplanation Explicative text of the change request in several languages.
5.3.15 xtdConcept
xtdConcept is a specialization of xtdObject and is the abstract entity from which xtdCountry,
xtdDimension, xtdExternalDocument, xtdProperty, xtdRelationshipType, xtdRelationshipToProperty,
xtdSubdivision, xtdSubject, xtdUnit, xtdValueList, xtdVisualRepresentation xtdFilter and
xtdQuantityKind are derived.
xtdConcept is used to store the common attributes of its derived entities; For example, it is the level
where the definitions and reference documents are described.
EXPRESS specification:
*)
ENTITY xtdConcept
ABSTRACT SUPERTYPE OF (ONEOF(
xtdCountry,
xtdDimension,
xtdExternalDocument,
xtdFilter,
xtdProperty,
xtdQuantityKind,
xtdRelationshipToProperty,
xtdRelationshipType,
xtdSubdivision,
xtdSubject,
xtdUnit,
xtdValueList,
xtdVisualRepresentation))
SUBTYPE OF (xtdObject);
ReferenceDocuments : OPTIONAL SET [1:?] OF xtdExternalDocument;
Definition : xtdMultiLanguageText;
Descriptions : OPTIONAL SET[1:?] of xtdMultiLanguageText;
Examples : OPTIONAL SET[1:?] of xtdMultiLanguageText;
LanguageOfCreator : xtdLanguage;
CountryOfOrigin : OPTIONAL xtdCountry;
SimilarTo : OPTIONAL SET [1:?] OF xtdConcept;
VisualRepresentations : OPTIONAL SET [1:?] OF xtdVisualRepresentation;
END_ENTITY;
(*
Attribute definitions:
Definition A list of instances of xtdMultiLanguageText that holds the definition of the
concept in several languages.
Descriptions A list of instances of xtdMultiLanguageText that holds descriptions of the con-
cept in several languages.
Examples A list of instances of xtdMultiLanguageText that holds examples of the concept
in several languages.
ISO 12006-3:2022(E)
LanguageOfCreator Language of the creator of the concept.
CountryOfOrigin Country from where the requirement for this concept originated.
SimilarTo Used to link similar concepts.
ReferenceDocuments List of attached reference documents.
VisualRepresentations Visual representation of the concept through sketches, photos, videos or other
multimedia objects.
5.3.16 xtdCountry
xtdCountry is a specialization of xtdConcept used to describe a country by its code according to
ISO 3166-1 and its list of subdivisions.
EXPRESS specification:
*)
ENTITY xtdCountry
SUBTYPE OF (xtdConcept);
Code : STRING;
Subdivisions : OPTIONAL SET [1:?] OF xtdSubdivision;
END_ENTITY;
*)
Attribute definitions:
Code Alpha-2 code used for the representation of name of countries from ISO 3166-1.
EXAMPLE 1 For Belgium Code = BE
EXAMPLE 2 For France Code = FR
Subdivisions List of subdivisions of a country according to ISO 3166-2.
5.3.17 xtdDictionary
xtdDictionary is a specialization of xtdRoot used to represent a data dictionary.
EXPRESS specification:
*)
ENTITY xtdDictionary
SUBTYPE OF (xtdRoot);
Name : xtdMultiLanguageText;
END_ENTITY;
(*
Attribute definitions:
Name Language-dependant name of the data dictionary.
5.3.18 xtdDimension
Dimension shall be defined according to the ISO 80000 series, defined from the 7 base quantities.
Any dimension is defined in a complete and unique way by its decomposition in basic physical quantities
in the form of a septuplet of rational numbers.
To allow distinction between “dimension one” and dimensionless, the definitions to be used are:
— Dimension one: all values = 0.
ISO 12006-3:2022(E)
— Dimensionless: At least one of the rationals shall be undefined (denominator=0).
-2
EXAMPLE 1 Acceleration is a dimension defined by LT
.
−2
EXAMPLE 2 Force is a dimension defined by LMT .
EXPRESS specification:
*)
ENTITY xtdDimension
SUBTYPE OF (xtdConcept);
LengthExponent : xtdRational;
Ma
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...