ISO/IEC 11179-35:2023

INTERNATIONAL ISO/IEC
STANDARD 11179-35
First edition
Information technology — Metadata
registries (MDR) —
Part 35:
Metamodel for model registration
Technologies de l'information — Registres de métadonnées (RM) —
Partie 35: Métamodèle pour l'enregistrement du modèle
PROOF/ÉPREUVE
Reference number
ISO/IEC 11179-35:2022(E)
© ISO/IEC 2022

---------------------- Page: 1 ----------------------
ISO/IEC 11179-35:2022(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 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
PROOF/ÉPREUVE © ISO/IEC 2022 – All rights reserved

---------------------- Page: 2 ----------------------
ISO/IEC 11179-35:2022(E)
Contents Page
Foreword .vii
Introduction .viii
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms . 2
5 Conformance . 3
5.1 Overview of conformance . . 3
5.2 Degree of conformance . 3
5.2.1 General . 3
5.2.2 Strictly conforming implementations . 3
5.2.3 Conforming implementations . 3
5.3 Conformance by feature . 4
5.4 Standard profiles for edition 4 registries . 4
5.5 Implementation conformance statement (ICS) . 4
5.6 Obligation . 4
6 Relationship to ISO/IEC 11179-3 .5
6.1 Metamodel for a metadata registry . 5
6.2 Specification of the metamodel . 5
6.3 Use of UML Class diagrams and textual description . 5
6.4 Package dependencies . 6
7 Model package . 6
7.1 Overview of the Model package. 6
7.2 Model metamodel region . 6
7.2.1 Overview of the Model metamodel region . 6
7.2.2 Classes in the Model metamodel region . 7
7.2.3 Associations in the Model metamodel region . 16
Annex A (informative) Consolidated Class Hierarchy .20
Annex B (informative) Use of the model registration facilities .21
Annex C (informative) Examples of model registration .23
Annex D (informative) Relationship to ISO/IEC 19763.64
Bibliography .66
iii
© ISO/IEC 2022 – All rights reserved PROOF/ÉPREUVE

---------------------- Page: 3 ----------------------
ISO/IEC 11179-35:2022(E)
List of Figures
Figure 1 — Package dependencies . 6
Figure 2 — Model metamodel region .7
Figure A.1 — Consolidated Class Hierarchy .20
Figure B.1 — Registration of models and metamodels .21
Figure C.1 — Create Repair Order example in BPMN .23
Figure C.2 — Sales order processing example expressed as a UML Class Diagram .27
Figure C.3 — Example form design.35
Figure C.4 — Form design metamodel (from ISO/IEC TS 19763-13:2016) .36
Figure C.5 — UML class diagram for the student registration scenario .46
Figure C.6 — JSON schema for the student registration scenario (3 of 3) .48
Figure C.7 — Metamodel for the Ellis-Barker entity-relationship notation .53
iv
PROOF/ÉPREUVE © ISO/IEC 2022 – All rights reserved

---------------------- Page: 4 ----------------------
ISO/IEC 11179-35:2022(E)
List of Tables
Table 1 — Attributes of the Model_Element_Characteristic class .11
Table 2 — Attribute of the Concept_Annotation class .13
Table C.1 — Modelling_Language class for the BPMN example .24
Table C.2 — Model class for the BPMN example .24
Table C.3 — Model_Element_Type class for the BPMN example .24
Table C.4 — Model_Element class for the BPMN example .24
Table C.5 — Model_Element_Characteristic_Type class for the BPMN example .25
Table C.6 — Model_Element_Characteristic class for the BPMN example .25
Table C.7 — Model_Element_Model_Relationship_Type class for the BPMN example .26
Table C.8 — Model_Element_Model_Relationship class for the BPMN example .26
Table C.9 — Model_Element_Relationship_Type class for the BPMN example .26
Table C.10 — Model_Element_Relationship class for the BPMN example .26
Table C.11 — Modelling_Language class for the UML Class Diagram example .27
Table C.12 — Model class for the UML Class Diagram example .27
Table C.13 — Concept class for the UML Class Diagram example .28
Table C.14 — Concept_Annotation class for the UML Class Diagram example .28
Table C.15 — Model_Element_Type class for the UML Class Diagram example .28
Table C.16 — Model_Element class for the UML Class Diagram example .28
Table C.17 — Model_Element_Characteristic_Type class for the UML Class Diagram
example .29
Table C.18 — Model_Element_Characteristic class for the UML Class Diagram example .30
Table C.19 — Model_Element_Relationship_Type class for the UML Class Diagram example .33
Table C.20 — Model_Element_Relationship class for the UML Class Diagram example .33
Table C.21 — Model class for the Form Design example .36
Table C.22 — Model_Element_Type class for the Form Design example .37
Table C.23 — Model_Element class for the Form Design example .37
Table C.24 — Model_Element_Characteristic_Type class for the Form Design example .39
Table C.25 — Model_Element_Characteristic_Type_Acceptability class for the Form
Design example .40
Table C.26 — Model_Element_Characteristic class for the Form Design example .40
Table C.27 — Model_Element_Relationship_Type class for the Form Design example .43
Table C.28 — Model_Element_Relationship class for the Form Design example . 44
Table C.29 — Modelling_Language class for the JSON Schema example .48
Table C.30 — Model class for the JSON Schema example .48
Table C.31 — Model_Element_Type class for the JSON Schema example .49
Table C.32 — Model_Element class for the JSON Schema example.49
Table C.33 — Model_Element_Characteristic_Type class for the JSON Schema example .49
Table C.34 — Model_Element_Characteristic class for the JSON Schema example.50
v
© ISO/IEC 2022 – All rights reserved PROOF/ÉPREUVE

---------------------- Page: 5 ----------------------
ISO/IEC 11179-35:2022(E)
Table C.35 — Model_Element_Relationship_Type class for the JSON Schema example .51
Table C.36 — Model_Element_Relationship class for the JSON Schema example .51
Table C.37 — Modelling_Language class for the Ellis-Barker metamodel example .53
Table C.38 — Model class for the Ellis-Barker metamodel example .53
Table C.39 — Model_Element_Type class the Ellis-Barker metamodel example .54
Table C.40 — Model_Element class for the Ellis-Barker metamodel example .54
Table C.41 — Model_Element_Characteristic_Type class for the Ellis-Barker metamodel
example .56
Table C.42 — Model_Element_Characteristic class for the Ellis-Barker metamodel example .56
Table C.43 — Model_Element_Relationship_Type class for the Ellis-Barker metamodel
example .61
Table C.44 — Model_Element_Relationship class for the Ellis-Barker metamodel example .61
vi
PROOF/ÉPREUVE © ISO/IEC 2022 – All rights reserved

---------------------- Page: 6 ----------------------
ISO/IEC 11179-35:2022(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.
This first edition of ISO/IEC 11179-35 is part of the 4th Edition modularization of ISO/IEC 11179. This
document brings into ISO/IEC 11179 the ability to register models and metamodels. As such, it provides
alternative facilities to those specified in ISO/IEC 19763 (see References [4] to [14]).
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 2022 – All rights reserved PROOF/ÉPREUVE

---------------------- Page: 7 ----------------------
ISO/IEC 11179-35:2022(E)
Introduction
In the ISO/IEC 11179 series, the structure of a Metadata Registry is specified in the form of a conceptual
data model. ISO/IEC 11179-3 specifies a metamodel for registry common facilities, which is intended to
be extended by other parts of ISO/IEC 11179 for specific purposes.
This document provides a specification of the extensions to the registry metamodel specified in
ISO/IEC 11179-3 to enable the registration of metadata about models and their associated metamodels.
These models can be information or data models, process models, models of web services or any
other type of models used in software engineering or information processing. All such models can be
considered as metadata.
In Clauses 6 and 7 and Annex C, this document uses:
— bold font to highlight terms which represent metadata objects specified by the metamodel;
— normal font for terms which represent concepts defined in Clause 3.
EXAMPLE Model_Element (7.2.2.3) is a class each instance of which models a model element.
viii
PROOF/ÉPREUVE © ISO/IEC 2022 – All rights reserved

---------------------- Page: 8 ----------------------
INTERNATIONAL STANDARD ISO/IEC 11179-35:2022(E)
Information technology — Metadata registries (MDR) —
Part 35:
Metamodel for model registration
1 Scope
This document provides a specification for an extension to a Metadata Registry (MDR), as specified in
ISO/IEC 11179-3, in which metadata that describes models, and their associated metamodels, 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 metadata about:
a) models used in software engineering or information processing, for example, information or
data models, process models, models of web services or any other type of models used to develop
software systems or the processing of information;
b) the concepts associated with the various elements within the models;
c) the metamodels associated with the models;
d) the mappings identified between the models, between the metamodels, and between the models
and their associated metamodels – this is achieved by using the mapping facilities specified in
ISO/IEC 11179-3.
This document is applicable to the formulation of models and metamodels to be shared among people
and machines, independent of the organization that produces the model or metamodel. It is not
applicable to the physical instantiation of any model.
2 Normative references
The following document is 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:2022, 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 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/
1
© ISO/IEC 2022 – All rights reserved PROOF/ÉPREUVE

---------------------- Page: 9 ----------------------
ISO/IEC 11179-35:2022(E)
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: A concept is independent of its representation.
[SOURCE: ISO/IEC 11179-3:2022, 3.2.7]
3.2
modelling language
language or notation that is used to represent some aspect of a universe of discourse
Note 1 to entry: Examples of modelling languages are languages or notations used to express ontologies or to
model information requirements, processes, services, forms, roles, goals or some other set of concepts that can
be modelled.
[SOURCE: ISO/IEC 19763-10:2014, 3.1.1 modified — “model” replaced by “represent”, “domain of
interest” replaced by “universe of discourse”, and Note 1 added.]
3.3
model
representation of some aspect of a universe of discourse using a recognised modelling language (3.2)
Note 1 to entry: Models can be used to express a set of information requirements, processes, services, roles, goals
or some other aspect of a universe of discourse.
[SOURCE: ISO/IEC 19763-1:2015, 4.1.12 modified — “normative modelling facility and model constructs”
replaced by “recognised modelling language”, “domain of interest” replaced by “universe of discourse”,
and references added.]
3.4
model element
element or component in a model (3.3)
Note 1 to entry: Examples of model elements are representations of an entity type in an information model, a
representation of an event in a process model, a representation of a service operation in a service model, or a
representation of an actor in a role and goal model.
[SOURCE: ISO/IEC 19763-10:2014, 3.1.3]
3.5
model element characteristic
individual characteristic that is used to qualify, identify, classify, quantify or in some other way express
the state of a model element (3.4)
Note 1 to entry: The state of a model element is the aggregation of the model element characteristics of that
model element.
3.6
concept annotation
use of a concept (3.1) to annotate a model (3.3) or a model element (3.4) in order to provide meaning to
the model or model element
4 Abbreviated terms
BPMN Business Process Model and Notation (see Reference [16])
IDEF1X Integrated Definition 1 Extended (an information modelling language) (see Reference [15])
2
PROOF/ÉPREUVE © ISO/IEC 2022 – All rights reserved

---------------------- Page: 10 ----------------------
ISO/IEC 11179-35:2022(E)
UML Unified Modeling Language (see References [2] and [3])
5 Conformance
5.1 Overview of conformance
Conformance rules for a Metadata Registry are specified in ISO/IEC 11179-3:2022, Clause 4. The clause
“Degree of Conformance” is repeated here for convenience. The subsequent subclauses extend the rules
from ISO/IEC 11179-3.
5.2 Degree of conformance
5.2.1 General
The distinction between “strictly conforming” and “conforming” implementations is necessary
to address the simultaneous needs for interoperability and extensions. This document describes
specifications that promote interoperability. Extensions are motivated by needs of users, vendors,
institutions, and industries, and:
a) are not directly specified by this document;
b) are specified and agreed to outside this document;
c) may serve as trial usage for future editions of this document.
A strictly conforming implementation might be limited in usefulness but is maximally interoperable
with respect to this document. A conforming implementation might be more useful but might be less
interoperable with respect to this document.
5.2.2 Strictly conforming implementations
A strictly conforming implementation:
a) shall support all mandatory, optional and conditional classes, attributes, datatypes and
associations;
b) shall not use, test, access, or probe for any extension features nor extensions to classes, attributes,
datatypes or associations or a combination of thereof;
c) shall not recognize, nor act on, nor allow the production of classes, attributes, datatypes or
associations or a combination thereof that are dependent on any unspecified, undefined or
implementation-defined behaviour.
NOTE The use of extensions to the metamodel might cause undefined behaviour.
5.2.3 Conforming implementations
A conforming implementation:
a) shall support all mandatory, optional and conditional classes, attributes, datatypes and
associations;
b) as permitted by the implementation, may use, test, access, or probe for extension features or
extensions to classes, attributes, datatypes, associations or any combination thereof;
c) may recognize, act on, or allow the production of classes, attributes, datatypes, associations or any
combination thereof that are dependent on implementation-defined behaviour.
NOTE 1 All strictly conforming implementations are also conforming implementations.
3
© ISO/IEC 2022 – All rights reserved PROOF/ÉPREUVE

---------------------- Page: 11 ----------------------
ISO/IEC 11179-35:2022(E)
NOTE 2 The use of extensions to the metamodel can cause undefined behaviour.
5.3 Conformance by feature
Conformance claims can be made to the whole of Clause 7 or to specific features within that clause.
Clause 7 is dependent upon one or more clauses of ISO/IEC 11179-3, so conformance to all or part of
Clause 7 shall be understood to imply conformance also to relevant provisions specified in one or more
of the clauses in ISO/IEC 11179-3.
A conformance statement shall specify exactly the features supported and not supported.
5.4 Standard profiles for edition 4 registries
This document specifies the following standard profiles in addition to those specified in
ISO/IEC 11179-3:2022, 4.4.2.
— Model registry: Implements Clause 7, in addition to all provisions of the Basic registry profile of
ISO/IEC 11179-3:2022, 4.4.2;
— Model registry with mapping: Implements Clause 7, in addition to all provisions of the Basic
registry with mapping profile of ISO/IEC 11179-3:2022, 4.4.2.
Conformance to the above profiles can be claimed using the following labels, respectively:
— ISO/IEC 11179-35:2022 Model registry;
— ISO/IEC 11179-35:2022 Model registry with mapping.
5.5 Implementation conformance statement (ICS)
An implementation claiming conformance to this document shall include an Implementation
Conformance Statement stating:
a) whether it conforms or strictly conforms;
b) which clauses are or are not supported;
c) what extensions, if any, are supported or used.
A standard profile may be referenced, if applicable.
EXAMPLE Product X conforms to ISO/IEC 11179-35:2022 Model Registry with Mapping.
5.6 Obligation
Attributes and associations specified in this document are stated to be Mandatory, Conditional or
Optional. The obligation is not explicitly stated but is to be inferred from the multiplicity of the attribute
or association, and the presence or absence of a condition.
For the purpose of conformance:
a) Mandatory attributes and associations shall exist and shall conform to the provisions of this
document.
b) Anything specified as Conditional within this document shall be treated as Mandatory if the
associated condition is satisfied and shall otherwise be not present.
c) Optional attributes and associations are not required to exist, but if they do exist they shall conform
to the provisions of this document.
4
PROOF/ÉPREUVE © IS
...

ISO/IEC 11179-35:2022(E)
ISO/IEC JTC 1/SC 32/WG 2
2022-11-11
Secretariat: ANSI
Information technology — Metadata registries (MDR) — Part 35: Metamodel for model
registration

Pre publication stage

Warning for WDs and CDs
This document is not an ISO International Standard. It is distributed for review and comment. It is subject to
change without notice and may not be referred to as an International Standard.
Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of
which they are aware and to provide supporting documentation.

© ISO/IEC 2022 – All rights reserved 1

---------------------- Page: 1 ----------------------
ISO/IEC 11179-35:2022(E)
© ISO/IEC 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’sISO's member body
in the country of the requester.
ISO copyright officeCopyright Office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: + 41 22 749 01 11
Fax: +41 22 749 09 47
Email: copyright@iso.org
Email: copyright@iso.org
Website: www.iso.orgwww.iso.org
Published in Switzerland.
ii © ISO/IEC 2022 – All rights reserved
ii © ISO/IEC 2022 – All rights reserved

---------------------- Page: 2 ----------------------
ISO/IEC 11179-35:2022(E)
Contents
Foreword . iv
Introduction. v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions. 1
4 Abbreviated terms . 3
5 Conformance . 3
5.1 Overview of conformance. 3
5.2 Degree of conformance . 3
5.2.1 General . 3
5.2.2 Strictly conforming implementations . 4
5.2.3 Conforming implementations . 4
5.3 Conformance by feature . 4
5.4 Standard profiles for edition 4 registries . 4
5.5 Implementation conformance statement (ICS) . 5
5.6 Obligation . 5
6 Relationship to ISO/IEC 11179-3:2022 . 5
6.1 Metamodel for a metadata registry . 5
6.2 Specification of the metamodel . 6
6.3 Use of UML Class diagrams and textual description . 6
6.4 Package dependencies. 6
7 Model package . 7
7.1 Overview of the Model package . 7
7.2 Model metamodel region . 7
7.2.1 Overview of the Model metamodel region . 7
7.2.2 Classes in the Model metamodel region . 8
7.2.3 Associations in the Model metamodel region . 18
Annex A (normative) Consolidated Class Hierarchy . 23
Annex B (informative) Use of the model registration facilities . 24
Annex C (informative) Examples of model registration . 26
Annex D (informative) Relationship to ISO/IEC 19763 . 78
Bibliography . 80
Foreword . vi
Introduction. vii
1 Scope . 1
© ISO/IEC 2022 – All rights reserved iii
© ISO/IEC 2022 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO/IEC 11179-35:2022(E)
2 Normative references . 1
3 Terms and definitions. 1
4 Abbreviated terms . 3
5 Conformance . 3
5.1 Overview of conformance. 3
5.2 Degree of conformance . 3
5.2.1 General . 3
5.2.2 Strictly conforming implementations . 3
5.2.3 Conforming implementations . 4
5.3 Conformance by feature . 4
5.4 Standard profiles for edition 4 registries . 4
5.5 Implementation conformance statement (ICS) . 5
5.6 Obligation . 5
6 Relationship to ISO/IEC 11179-3 . 5
6.1 Metamodel for a metadata registry . 5
6.2 Specification of the metamodel . 5
6.3 Use of UML Class diagrams and textual description . 6
6.4 Package dependencies. 6
7 Model package . 7
7.1 Overview of the Model package . 7
7.2 Model metamodel region . 8
7.2.1 Overview of the Model metamodel region . 8
7.2.2 Classes in the Model metamodel region . 9
7.2.3 Associations in the Model metamodel region . 19
Annex A (informative) Consolidated Class Hierarchy . 24
Annex B (informative) Use of the model registration facilities . 26
Annex C (informative) Examples of model registration . 28
Annex D (informative) Relationship to ISO/IEC 19763 . 86
Bibliography . 88
List of figures
Figure 1 — Package dependencies . 7
Figure 2 — Model metamodel region . 9
Figure A.1 — Consolidated Class Hierarchy . 25
Figure B.1 — Registration of models and metamodels . 27
Figure C.1 — Create Repair Order example in BPMN . 29
Figure C.2 — Sales order processing example expressed as a UML Class Diagram . 34
Figure C.3 — Example form design . 45
Figure C.4 — Form design metamodel (from ISO/IEC TS 19763-13:2016) . 47
Figure C.5 — UML class diagram for the student registration scenario . 60
iv © ISO/IEC 2022 – All rights reserved
iv © ISO/IEC 2022 – All rights reserved

---------------------- Page: 4 ----------------------
ISO/IEC 11179-35:2022(E)
Figure C.7 — Metamodel for the Ellis-Barker entity-relationship notation . 72

List of Tables
Table 1 — Attributes of the Model_Element_Characteristic class . 13
Table 2 — Attribute of the Concept_Annotation class . 16
Table C.1 — Modelling_Language class for the BPMN example . 29
Table C.2 — Model class for the BPMN example . 29
Table C.3 — Model_Element_Type class for the BPMN example . 30
Table C.4 — Model_Element class for the BPMN example. 30
Table C.5 — Model_Element_Characteristic_Type class for the BPMN example . 31
Table C.6 — Model_Element_Characteristic class for the BPMN example . 31
Table C.7 — Model_Element_Model_Relationship_Type class for the BPMN example . 32
Table C.8 — Model_Element_Model_Relationship class for the BPMN example . 32
Table C.9 — Model_Element_Relationship_Type class for the BPMN example . 32
Table C.10 — Model_Element_Relationship class for the BPMN example . 32
Table C.11 — Modelling_Language class for the UML Class Diagram example . 34
Table C.12 — Model class for the UML Class Diagram example . 34
Table C.13 — Concept class for the UML Class Diagram example . 35
Table C.14 — Concept_Annotation class for the UML Class Diagram example . 35
Table C.15 — Model_Element_Type class for the UML Class Diagram example . 35
Table C.16 — Model_Element class for the UML Class Diagram example . 35
Table C.17 — Model_Element_Characteristic_Type class for the UML Class Diagram example . 37
Table C.18 — Model_Element_Characteristic class for the UML Class Diagram example . 37
Table C.19 — Model_Element_Relationship_Type class for the UML Class Diagram example . 41
Table C.20 — Model_Element_Relationship class for the UML Class Diagram example . 41
Table C.21 — Model class for the Form Design example . 47
Table C.22 — Model_Element_Type class for the Form Design example . 48
Table C.23 — Model_Element class for the Form Design example . 48
Table C.24 — Model_Element_Characteristic_Type class for the Form Design example . 51
Table C.25 — Model_Element_Characteristic_Type_Acceptability class for the Form Design
example . 52
Table C.26 — Model_Element_Characteristic class for the Form Design example . 52
Table C.27 — Model_Element_Relationship_Type class for the Form Design example . 56
© ISO/IEC 2022 – All rights reserved v
© ISO/IEC 2022 – All rights reserved v

---------------------- Page: 5 ----------------------
ISO/IEC 11179-35:2022(E)
Table C.28 —Model_Element_Relationship class for the Form Design example . 57
Table C.29 —Modelling_Language class for the JSON Schema example . 65
Table C.30 — Model class for the JSON Schema example . 65
Table C.31 — Model_Element_Type class for the JSON Schema example . 66
Table C.32 — Model_Element class for the JSON Schema example . 66
Table C.33 — Model_Element_Characteristic_Type class for the JSON Schema example . 67
Table C.34 — Model_Element_Characteristic class for the JSON Schema example . 67
Table C.35 — Model_Element_Relationship_Type class for the JSON Schema example . 69
Table C.36 —Model_Element_Relationship class for the JSON Schema example . 70
Table C.37 — Modelling_Language class for the Ellis-Barker metamodel example . 72
Table C.38 — Model class for the Ellis-Barker metamodel example . 73
Table C.39 — Model_Element_Type class the Ellis-Barker metamodel example . 73
Table C.40 — Model_Element class for the Ellis-Barker metamodel example . 73
Table C.41 — Model_Element_Characteristic_Type class for the Ellis-Barker metamodel
example . 76
Table C.42 — Model_Element_Characteristic class for the Ellis-Barker metamodel example . 76
Table C.43 — Model_Element_Relationship_Type class for the Ellis-Barker metamodel
example . 83
Table C.44 — Model_Element_Relationship class for the Ellis-Barker metamodel example . 83


vi © ISO/IEC 2022 – All rights reserved
vi © ISO/IEC 2022 – All rights reserved

---------------------- Page: 6 ----------------------
ISO/IEC 11179-35:2022(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/directiveswww.iso.org/directives or
www.iec.ch/members_experts/refdocswww.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/patentswww.iso.org/patents) or the IEC list of patent declarations received (see
https://patents.iec.chhttps://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.htmlwww.iso.org/iso/foreword.html. In the IEC, see
www.iec.ch/understanding-standardswww.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.
This first edition of ISO/IEC 11179-35 is part of the 4th Edition modularization of ISO/IEC 11179. This
document brings into ISO/IEC 11179 the ability to register models and metamodels. As such, it provides
alternative facilities to those specified in ISO/IEC 19763 (see references [4] to [14]).References [4] to
[14]).
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.htmlwww.iso.org/members.html and www.iec.ch/national-
committeeswww.iec.ch/national-committees.
© ISO/IEC 2022 – All rights reserved vii
© ISO/IEC 2022 – All rights reserved vii

---------------------- Page: 7 ----------------------
ISO/IEC 11179-35:2022(E)
Introduction
In the ISO/IEC 11179 series, the structure of a Metadata Registry is specified in the form of a conceptual
data model. ISO/IEC 11179-3:2022 specifies a metamodel for registry common facilities, which is
intended to be extended by other parts of ISO/IEC 11179 for specific purposes.
This document provides a specification of the extensions to the registry metamodel specified in
ISO/IEC 11179-3 to enable the registration of metadata about models and their associated metamodels.
These models can be information or data models, process models, models of web services or any other
type of models used in software engineering or information processing. All such models can be
considered as metadata.
In clauses Clauses 6 and 7 and Annex C, this document uses:
⎯ — bold font to highlight terms which represent metadata objects specified by the metamodel;
⎯ — normal font for terms which represent concepts defined in clause Clause 3.
EXAMPLE Model_Element (7.2.2.3) is a class each instance of which models a model element.


viii © ISO/IEC 2022 – All rights reserved
viii © ISO/IEC 2022 – All rights reserved

---------------------- Page: 8 ----------------------
INTERNATIONAL STANDARD ISO/IEC 11179-35:2022(E)

Information technology -- Metadata registries (MDR) -- Part 35:
Metamodel for model registration
1 Scope
This document provides a specification for an extension to a Metadata Registry (MDR), as specified in
ISO/IEC 11179-3, in which metadata that describes models, and their associated metamodels, 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 metadata about:
a) a) models used in software engineering or information processing, for example, information or
data models, process models, models of web services or any other type of models used to develop
software systems or the processing of information;
b) b) the concepts associated with the various elements within the models;
c) c) the metamodels associated with the models;
d) d) the mappings identified between the models, between the metamodels, and between the
models and their associated metamodels – this is achieved by using the mapping facilities specified
in ISO/IEC 11179-3.
This document is applicable to the formulation of models and metamodels to be shared among people
and machines, independent of the organization that produces the model or metamodel. It is not
applicable to the physical instantiation of any model.
2 Normative references
The following document is 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:2022, 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 terminological databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https://www.iso.org/obphttps://www.iso.org/obp
— IEC Electropedia: available at http://www.electropedia.org/https://www.electropedia.org/
© ISO/IEC 2022 – All rights reserved 1

---------------------- Page: 9 ----------------------
ISO/IEC 11179-35:2022(E)

3.1
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: A concept is independent of its representation.
[SOURCE: ISO/IEC 11179-3:2022, 3.2.7]

3.2
3.2 modelling language
language or notation that is used to represent some aspect of a universe of discourse
Note 1 to entry: Examples of modelling languages are languages or notations used to express ontologies or to
model information requirements, processes, services, forms, roles, goals or some other set of concepts that can be
modelled.
[SOURCE: ISO/IEC 19763-10:2014, 3.1.1 modified –— “model” replaced by “represent”, “domain of
interest” replaced by “universe of discourse”, and Note 1 added].]

3.3
3.3 model
representation of some aspect of a universe of discourse using a recognised modelling language (3.2)
Note 1 to entry: Models can be used to express a set of information requirements, processes, services, roles,
goals or some other aspect of a universe of discourse.
[SOURCE: ISO/IEC 19763-1:2015, 4.1.12 modified –— “normative modelling facility and model
constructs” replaced by “recognised modelling language”, “domain of interest” replaced by “universe of
discourse”, and references added].]

3.4
3.4 model element
element or component in a model (3.3)
Note 1 to entry: Examples of model elements are representations of an entity type in an information model, a
representation of an event in a process model, a representation of a service operation in a service model, or a
representation of an actor in a role and goal model.
[SOURCE: ISO/IEC 19763-10:2014, 3.1.3 modified – reference added]

3.5
3.5 model element characteristic
2 © ISO/IEC 2022 – All rights reserved
2 © ISO/IEC 2022 – All rights reserved

---------------------- Page: 10 ----------------------
ISO/IEC 11179-35:2022(E)
individual characteristic that is used to qualify, identify, classify, quantify or in some other way express
the state of a model element (3.4)
Note 1 to entry: The state of a model element is the aggregation of the model element characteristics of that
model element.

3.6
3.6 concept annotation
use of a concept (3.1) to annotate a model (3.3) or a model element (3.4) in order to provide meaning to
the model or model element
4 Abbreviated terms
BPMN Business Process Model and Notation (see reference [16])Reference [16])
IDEF1X Integrated Definition 1 Extended (an information modelling language) (see reference
[15])Reference [15])
UML Unified Modeling Language (see references [2], [3])References [2] and [3])
5 Conformance
5.1 Overview of conformance
Conformance rules for a Metadata Registry are specified in ISO/IEC 11179-3:2022, Clause 4. The clause
“Degree of Conformance” is repeated here for convenience. The subsequent subclauses extend the rules
from ISO/IEC 11179-3.
5.2 Degree of conformance
5.2.1 General
The distinction between “strictly conforming” and “conforming” implementations is necessary to
address the simultaneous needs for interoperability and extensions. This document describes
specifications that promote interoperability. Extensions are motivated by needs of users, vendors,
institutions, and industries, and:
a) a) are not directly specified by this document;
b) b) are specified and agreed to outside this document;
c) c) may serve as trial usage for future editions of this document.
A strictly conforming implementation might be limited in usefulness but is maximally interoperable
with respect to this document. A conforming implementation might be more useful but might be less
interoperable with respect to this document.
5.2.2 Strictly conforming implement
...