ISO/IEC 11179-32:2023

Information technology — Metadata registries (MDR) — Part 32: Metamodel for concept system registration

This document provides a specification for an extension to a metadata registry (MDR), as specified in ISO/IEC 11179-3:2023, in which metadata that describes concept systems can be registered. The specification in this document, together with the relevant clauses of the specification in ISO/IEC 11179-3, provides the ability to record the following metadata: concept systems and associated concepts; relations among concepts in a concept system; assertions about concepts in a concept system. The metamodel in this document is intended to support the full description of a concept system, including ontologies. Where there is a requirement to register an ontology where the details are defined elsewhere, consider using ISO/IEC 19763-3 instead.

Technologies de l'information — Registres de métadonnées (RM) — Partie 32: Métamodèle pour l'enregistrement de systèmes de concepts

General Information

• Status: Published
• Publication Date: 15-Jan-2023
• ICS: 35.040.50 - Automatic identification and data capture techniques
• Technical Committee: ISO/IEC JTC 1/SC 32 - Data management and interchange
• Drafting Committee: ISO/IEC JTC 1/SC 32/WG 2 - MetaData
• Current Stage: 6060 - International Standard published
• Start Date: 16-Jan-2023
• Due Date: 03-Jul-2023
• Completion Date: 16-Jan-2023

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 11179-32
First edition
2023-01
Information technology — Metadata
registries (MDR) —
Part 32:
Metamodel for concept system
registration
Technologies de l'information — Registres de métadonnées (RM) —
Partie 32: Métamodèle pour l'enregistrement de systèmes de concepts
Reference number
ISO/IEC 11179-32:2023(E)
© ISO/IEC 2023

---------------------- Page: 1 ----------------------
ISO/IEC 11179-32:2023(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2023
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: [phone]
Email: [e-mail]
Website: www.iso.org
Published in Switzerland
ii
  © ISO/IEC 2023 – All rights reserved

---------------------- Page: 2 ----------------------
ISO/IEC 11179-32:2023(E)
Contents Page
Foreword .vii
Introduction .viii
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms . 4
5 Conformance . 5
5.1 Overview of conformance . . 5
5.2 Degree of conformance . 5
5.2.1 General . 5
5.2.2 Strictly conforming implementations . 5
5.2.3 Conforming implementations . 6
5.3 Conformance by feature . 6
5.4 Registry conformance . . 6
5.4.1 Standard registry profiles . 6
5.4.2 Conformance labels . . 6
5.5 Implementation conformance statement (ICS) . 7
5.6 Obligation . 7
6 Relationship to ISO/IEC 11179-3 .7
6.1 Metamodel for a metadata registry . 7
6.2 Specification of the metamodel . 7
6.3 Use of UML Class diagrams and textual description . 8
6.4 Package dependencies . 8
6.5 Subclassing the Constraint_Set class . 9
6.6 Relationship to Classification region in ISO/IEC 11179-3:2023 . 9
7 Concept_System package . 9
7.1 Overview of the Concept_System package . 9
7.2 Concept System metamodel region . 9
7.2.1 Overview . 9
7.2.2 Classes in the Concept System metamodel region . 10
7.2.3 Associations of the Concept System metamodel region . 18
8 Binary_Relations package .21
8.1 Overview of Binary_Relations package . 21
8.2 Binary Relations metamodel region. 21
8.2.1 Overview . 21
8.2.2 Classes in the Binary Relations metamodel region . 21
8.2.3 Datatypes in the Binary_Relation metamodel region .22
Annex A (informative) Consolidated Class Hierarchy .24
Annex B (informative) Concept System Examples .25
Annex C (informative) Mapping ISO/IEC 11179-3:2023 Classification_Scheme to ISO/IEC
11179-32:2023 Concept_System .54
Bibliography .55
iii
© ISO/IEC 2023 – All rights reserved

---------------------- Page: 3 ----------------------
ISO/IEC 11179-32:2023(E)
List of Figures
Figure 1 — Package dependencies . 8
Figure 2 — Subclassing Constraint_Set. 9
Figure 3 — Concept system metamodel region .10
Figure 4 — Binary Relations metamodel region .21
Figure A.1 — Consolidated Class Hierarchy .24
Figure B.1 — Car Registration Model in ORM.30
Figure B.2 — Car Registration Ontology in OWL .39
iv
  © ISO/IEC 2023 – All rights reserved

---------------------- Page: 4 ----------------------
ISO/IEC 11179-32:2023(E)
List of Tables
Table 1 — Attributes of Concept_System.12
Table 2 — Attributes of Relation .13
Table 3 — Attributes of Relation_Role .13
Table 4 — Attributes of Assertion.14
Table 5 — Attributes of Concept_Constraint_Set .16
Table 6 — Attributes of Relation_Constraint_Set .17
Table 7 — Examples of binary relations and their characterization .22
Table 8 — Attributes of Binary_Relation .22
Table 9 — Values of Reflexivity enumeration .22
Table 10 — Values of Symmetry enumeration .23
Table 11 — Values of Reflexivity enumeration .23
Table B.1 — Correspondences of ISO/IEC 11179-32 concept system metamodel to selected
notations .25
Table B.2 — SKOS-CORE as an ISO/IEC 11179-32 Concept System .26
Table B.3 — SKOS relations as ISO/IEC 11179-32 Binary Relations .26
Table B.4 — SKOS Thesaurus example — ISO/IEC 11179-32 Concept System .27
Table B.5 — SKOS Thesaurus Example — ISO/IEC 11179-32 Concepts .27
Table B.6 — SKOS Thesaurus Example — ISO/IEC 11179-32 Links .27
Table B.7 — SKOS Thesaurus Example — ISO/IEC 11179-31 Conceptual Domains .28
Table B.8 — SKOS Thesaurus Example — ISO/IEC 11179-31 Value Domains .28
Table B.9 — ORM as an ISO/IEC 11179-32 Concept System .29
Table B.10 — ORM Relations as ISO/IEC 11179-32 Binary Relations .29
Table B.11 — ORM Roles as ISO/IEC 11179-32 Relation Roles .29
Table B.12 — Car Registration Model in ORM — ISO/IEC 11179-32 Concept System .32
Table B.13 — Car Registration Model in ORM — ISO/IEC 11179-32 Concepts .32
Table B.14 — Car Registration Model in ORM — ISO/IEC 11179-32 Binary Relations .32
Table B.15 — Car Registration Model in ORM — ISO/IEC 11179-32 Links .33
Table B.16 — OWL constructs with directly corresponding ISO/IEC 11179-32 metamodel
elements .34
Table B.17 — OWL built-in constructs described in OWL metamodel .34
Table B.18 — OWL as an ISO/IEC 11179-32 Concept System .35
Table B.19 — OWL Concepts as ISO/IEC 11179-32 Concepts .35
Table B.20 — OWL Binary Relations as ISO/IEC 11179-32 Binary Relations.35
Table B.21 — OWL Relations (except Binary Relations) as ISO/IEC 11179-32 Relations .36
Table B.22 — OWL Constructs as ISO/IEC 11179-32 Relation Roles .36
Table B.23 — OWL Constructs as ISO/IEC 11179-32 Links.37
Table B.24 — Car Registration Model in OWL — ISO/IEC 11179-32 Concept System .43
Table B.25 — Car Registration Model in OWL — ISO/IEC 11179-32 Concepts .43
v
© ISO/IEC 2023 – All rights reserved

---------------------- Page: 5 ----------------------
ISO/IEC 11179-32:2023(E)
Table B.26 — Car Registration Model in OWL — ISO/IEC 11179-32 Binary Relations .43
Table B.27 — Car Registration Model in OWL — ISO/IEC 11179-32 Relation Roles . 44
Table B.28 — Car Registration Model in OWL — ISO/IEC 11179-32 Links . 44
Table B.29 — Car Registration Model in OWL — ISO/IEC 11179-32 Assertions .48
Table B.30 — CL Metamodel – ISO/IEC 11179-32 Concept System .51
Table B.31 — CL Metamodel – ISO/IEC 11179-32 Binary Relations .51
Table B.32 — CLIF Units Example — ISO/IEC 11179-32 Concept System .51
Table B.33 — CLIF Units Example — ISO/IEC 11179-32 Concepts .52
Table B.34 — CLIF Units Example — ISO/IEC 11179-32 Binary Relations .52
Table B.35 — CLIF Units Example — ISO/IEC 11179-32 Relations Roles .52
Table B.36 — CLIF Units Example — ISO/IEC 11179-32 Links .52
Table B.37 — CLIF Units Example — ISO/IEC 11179-32 Assertions .53
Table C.1 — Summary view of the mapping of Classification_Scheme to Concept_System .54
vi
  © ISO/IEC 2023 – All rights reserved

---------------------- Page: 6 ----------------------
ISO/IEC 11179-32:2023(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are
members of ISO or IEC participate in the development of International Standards through technical
committees established by the respective organization to deal with particular fields of technical
activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international
organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the
work.
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 document 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 or
www.iec.ch/members_experts/refdocs).
Attention is drawn to the possibility that some of the elements of this document may be the subject
of patent rights. ISO and IEC 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) or the IEC
list of patent declarations received (see https://patents.iec.ch).
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. In the IEC, see www.iec.ch/understanding-standards.
This document was prepared by Joint Technical Committee ISO/IEC/JTC 1, Information technology,
Subcommittee SC 32, Data management and interchange.
A list of all parts in the ISO/IEC 11179 series can be found on the ISO and IEC websites.
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 and
www.iec.ch/national-committees.
vii
© ISO/IEC 2023 – All rights reserved

---------------------- Page: 7 ----------------------
ISO/IEC 11179-32:2023(E)
Introduction
ISO/IEC 11179-3 specifies the structure of a Metadata Registry (MDR) and provides a metamodel for
registry common facilities. That metamodel is intended to be extended by other parts of ISO/IEC 11179
for specific purposes.
This first edition of ISO/IEC 11179-32, is part of a restructuring of ISO/IEC 11179-3:2013, which has
now been broken into multiple parts. This document provides a metamodel for registering metadata
about concept systems and binary relations in a Metadata Registry (MDR), as extensions to the registry
metamodel specified in ISO/IEC 11179-3.
In Clauses 7 and 8, this document uses:
— bold font to highlight terms which represent metadata objects specified by the metamodel;
— normal text for terms which represent concepts defined in Clause 3.
EXAMPLE Concept (7.2.2.1) is a class each instance of which models a concept.
viii
  © ISO/IEC 2023 – All rights reserved

---------------------- Page: 8 ----------------------
INTERNATIONAL STANDARD ISO/IEC 11179-32:2023(E)
Information technology — Metadata registries (MDR) —
Part 32:
Metamodel for concept system registration
1 Scope
This document provides a specification for an extension to a metadata registry (MDR), as specified in
ISO/IEC 11179-3:2023, in which metadata that describes concept systems can be registered.
The specification in this document, together with the relevant clauses of the specification in
ISO/IEC 11179-3, provides the ability to record the following metadata:
— concept systems and associated concepts;
— relations among concepts in a concept system;
— assertions about concepts in a concept system.
The metamodel in this document is intended to support the full description of a concept system,
including ontologies.
Where there is a requirement to register an ontology where the details are defined elsewhere, consider
[8]
using ISO/IEC 19763-3 instead.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
ISO/IEC 11179-3:2023, Information technology — Metadata registries (MDR) — Part 3: Metamodel for
registry common facilities
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO/IEC 11179-3 and the following
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/
3.1
concept
unit of knowledge created by a unique combination of characteristics
Note 1 to entry: Concepts are not necessarily bound to particular natural languages. They are, however,
influenced by the social or cultural background which often leads to different categorizations.
Note 2 to entry: This is the concept “concept” as used and designated by the term “concept” in terminology work.
It is a very different concept from that designated by other domains such as industrial automation or marketing.
1
© ISO/IEC 2023 – All rights reserved

---------------------- Page: 9 ----------------------
ISO/IEC 11179-32:2023(E)
Note 3 to entry: A concept is independent of its representation.
[SOURCE: ISO 1087:2019, 3.2.7, modified — Reference to definition of characteristics removed. Note 3 to
entry added.]
3.2
concept system
system of concepts
set of concepts (3.1) structured in one or more related domains according to the concept relations (3.3)
among its concepts
[SOURCE: ISO 1087:2019, 3.2.28]
3.3
relation
concept relation
sense in which concepts (3.1) may be connected, via constituent relation roles (3.4)
EXAMPLE Causality is a relation with two constituent roles: cause and effect.
Note 1 to entry: The related concepts may be general or individual concepts.
3.4
relation role
role (3.5) that a concept (3.1) plays in a relation (3.3)
3.5
role
specified responsibilities
3.6
link
member of a relation (3.3)
3.7
link end
end of a link (3.6), identifying the relation role (3.4) played by a concept (3.1) in the link
3.8
binary relation
relation (3.3) with arity (3.9) equal to 2 (i.e. whose members all have two ends)
Note 1 to entry: Most common semantic relations are binary, e.g. “equals”, “less than”, “greater than”, “is part of”,
etc. An example of a relation which is not binary is “betweenness” (e.g. A is between B and C.).
3.9
arity
number of arguments that a function takes
3.10
reflexivity
characterization of a binary relation (3.8) as reflexive, irreflexive or antireflexive
Note 1 to entry: A binary relation, R, is reflexive if for all x, R(x,x) is true. Equality is an example of a reflexive
relation.
Note 2 to entry: A binary relation, R, is irreflexive if it is not reflexive. i.e., R(x,x) is not necessarily true for all x.
Note 3 to entry: A binary relation, R, is antireflexive if for all x, R(x,x) is false. Inequality is an example of
an antireflexive relation. An antireflexive relation is also irreflexive, but antireflexive is a more specific
characterization.
2
  © ISO/IEC 2023 – All rights reserved

---------------------- Page: 10 ----------------------
ISO/IEC 11179-32:2023(E)
3.11
symmetry
characterization of a binary relation (3.8) as symmetric, asymmetric or antisymmetric
Note 1 to entry: A binary relation, R, is symmetric if for all x, y: R(x,y) implies R(y,x).
EXAMPLE 1 Symmetric relations include: “equals”, “not equals”, “within-2-miles-of”, etc.
Note 2 to entry: Symmetry does not imply reflexivity (3.18).
EXAMPLE 2 the “inequality” relation is symmetric, but antireflexive.
Note 3 to entry: A binary relation, R, is asymmetric if for all x,y: R(x,y) does not imply R(y,x).
EXAMPLE 3 Asymmetric relations include: “less than”, “likes”, “father of”, etc.
Note 4 to entry: A binary relation, R, is anti-symmetric if for all x,y: R(x,y) implies not R(y,x). An antisymmetric
relation is also asymmetric, but antisymmetric is a more specific characterization.
EXAMPLE 4 “less than” is an antisymmetric relation.
Note 5 to entry: An asymmetric relation is not necessarily antisymmetric.
EXAMPLE 5 Less than or equals.
3.12
transitivity
characterization of a binary relation (3.8) as: transitive, intransitive or antitransitive
Note 1 to entry: A binary relation, R, is transitive, if for all x,y,z: R(x,y) and R(y,z) implies R(x,z). Examples of
transitive relations include equality, less than and less than or equals.
Note 2 to entry: A binary relation, R, is intransitive if it is not transitive i.e. R(x,y) and R(y,z) does not imply R(x,z).
Note 3 to entry: A binary relation, R, is antitransitive if for all x,y,z: R(x,y) and R(y,z) implies not R(x,z).
Note 4 to entry: An antitransitive relation is also intransitive, but antitransitive is a more specific characterization.
3.13
object
anything perceivable or conceivable
Note 1 to entry: Objects can be material (e.g. “engine”, “sheet of paper”, “diamond”), immaterial (e.g. “conversion
ratio”, “project plan”) or imagined (e.g. “unicorn”, “scientific hypothesis”).
[SOURCE: ISO 1087:2019, 3.1.1]
3.14
property
feature of an object (3.13)
EXAMPLE 1 “Being made of wood” as a property of a given “table”.
EXAMPLE 2 “Belonging to person A” as a property of a given “pet”.
2
EXAMPLE 3 “Having been formulated by Einstein” as a property of the equation “E = mc ”.
EXAMPLE 4 “Being compassionate” as a property of a given “person”.
EXAMPLE 5 “Having a given cable” as a property of a given “computer mouse”.
Note 1 to entry: One or more objects can have the same property.
[SOURCE: ISO 1087:2019, 3.1.3]
3
© ISO/IEC 2023 – All rights reserved

---------------------- Page: 11 ----------------------
ISO/IEC 11179-32:2023(E)
3.15
characteristic
abstraction of a property (3.14)
EXAMPLE “Having a cable for connecting with a computer” as a characteristic of the concept “cord mouse”.
Note 1 to entry: Characteristics are used for describing concepts (3.6).
[SOURCE: ISO 1087:2019, 3.2.1]
3.16
notation
formal syntax and associated semantics for the representation of information
[5],[6],[7] [11] [12] [13] [9] [9] [17] [4]
EXAMPLE UML, MOF, OCL, OWL /RDF, SKOS, CGIF, XCL, XTM or ISO/IEC 11404
Note 1 to entry: A formal syntax consists of a set of symbols and the rules for their use.
Note 2 to entry: Formal syntax is often intended for machine processing.
[SOURCE: ISO/IEC 11179-3:2023, 3.2.36]
3.17
assertion
sentence or proposition in logic which is asserted (or assumed) to be true
3.18
cardinality
number of elements in a set
Note 1 to entry: cf. multiplicity (3.19)
[5]
Note 2 to entry: Adapted from ISO/IEC 19501:2005, Glossary.
3.19
multiplicity
specification of the range of allowable cardinalities (3.18) that a set may assume
Note 1 to entry: Multiplicity specifications may be given for roles within associations (ISO/IEC 11179-3:2023,
3.1.5)
Note 2 to entry: A multiplicity is a (possibly infinite) subset of the nonnegative integers
[5]
Note 3 to entry: Adapted from ISO/IEC 19501:2005, Glossary.
3.20
taxonomy
type of hierarchy which deals with generalization/specialization relationships
Note 1 to entry: cf. meronomy (3.21)
3.21
meronomy
type of hierarchy which deals with part-whole rel
...