ISO/IEC 11179-3:2023/FDAmd 1

FINAL DRAFT
Amendment
ISO/IEC
11179-3:2023/
FDAM 1
ISO/IEC JTC 1/SC 32
Information technology — Metadata
Secretariat: ANSI
registries (MDR) —
Voting begins on:
2026-03-06
Part 3:
Metamodel for registry common
Voting terminates on:
2026-05-01
facilities
AMENDMENT 1: Enhancements to
Item Mapping
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 SUPPOR TING DOCUMENTATION.
IN ADDITION TO THEIR EVALUATION AS
BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO­
LOGICAL, COMMERCIAL AND USER PURPOSES, DRAFT
INTERNATIONAL STANDARDS MAY ON OCCASION HAVE
TO BE CONSIDERED IN THE LIGHT OF THEIR POTENTIAL
TO BECOME STAN DARDS TO WHICH REFERENCE MAY BE
MADE IN NATIONAL REGULATIONS.
Reference number
ISO/IEC 11179­3:2023/FDAM 1:2026(en) © ISO/IEC 2026

FINAL DRAFT
ISO/IEC 11179-3:2023/FDAM 1:2026(en)
Amendment
ISO/IEC
11179-3:2023/
FDAM 1
ISO/IEC JTC 1/SC 32
Information technology — Metadata
Secretariat: ANSI
registries (MDR) —
Voting begins on:
Part 3:
Metamodel for registry common
Voting terminates on:
facilities
AMENDMENT 1: Enhancements to
Item Mapping
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 SUPPOR TING DOCUMENTATION.
© ISO/IEC 2026
IN ADDITION TO THEIR EVALUATION AS
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO­
LOGICAL, COMMERCIAL AND USER PURPOSES, DRAFT
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
INTERNATIONAL STANDARDS MAY ON OCCASION HAVE
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
TO BE CONSIDERED IN THE LIGHT OF THEIR POTENTIAL
or ISO’s member body in the country of the requester.
TO BECOME STAN DARDS TO WHICH REFERENCE MAY BE
MADE IN NATIONAL REGULATIONS.
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 Reference number
ISO/IEC 11179­3:2023/FDAM 1:2026(en) © ISO/IEC 2026

© ISO/IEC 2026 – All rights reserved
ii
ISO/IEC 11179-3:2023/FDAM 1:2026(en)
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).
ISO and IEC draw attention to the possibility that the implementation of this document may involve the
use of (a) patent(s). ISO and IEC take no position concerning the evidence, validity or applicability of any
claimed patent rights in respect thereof. As of the date of publication of this document, ISO and IEC had not
received notice of (a) patent(s) which may be required to implement this document. However, implementers
are cautioned that this may not represent the latest information, which may be obtained from the patent
database available at www.iso.org/patents and https://patents.iec.ch. ISO and IEC shall not be held
responsible for identifying any or all such patent rights.
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 Amendment 1 provides minor enhancements to the registry specification in Clause 9, major
enhancements to the Item Mapping facility in Clause 11, and adds a new Rules facility as Clause 12 of
ISO/IEC 11179-3:2023.
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.

© ISO/IEC 2026 – All rights reserved
iii
ISO/IEC 11179-3:2023/FDAM 1:2026(en)
Information technology — Metadata registries (MDR) —
Part 3:
Metamodel for registry common facilities
AMENDMENT 1: Enhancements to Item Mapping

3.2.29
Replace term entry 3.2.29 with the following:
3.2.29
datum (singular)
datums (countable plural)
data (uncountable plural)
designation (3.2.11) whose concept (3.2.7) is a value

3.2.30
Replace term entry 3.2.30 with the following:
3.2.30
metadata
descriptive data (3.2.29) about an object(s) (3.2.1)
Note 1 to entry: In the ISO/IEC 11179 and ISO/IEC 19763 series of standards, the objects being described are instances
of the subclasses of Item (6.4.2.1), e.g. concepts, data elements, services etc.

6.2.1, Figure 2
Replace Figure 2 with the following:
Figure 2 — Predefined types metamodel region

© ISO/IEC 2026 – All rights reserved
ISO/IEC 11179-3:2023/FDAM 1:2026(en)

6.2.13
Insert the following subclause after 6.2.13:
6.2.14  BLOB
BLOB is a datatype which represents a binary large object string datatype.
EXAMPLE A PDF document to be attached to an instance of the Reference_Document (6.3.8) class.

6.3.1, Figure 3
Replace Figure 3 with the following:
Figure 3 — Basic classes metamodel region

© ISO/IEC 2026 – All rights reserved
ISO/IEC 11179-3:2023/FDAM 1:2026(en)
6.3.8.2, Table 7
Append the following row at the end of Table 7:
document BLOB 0.1 The reference document itself.

© ISO/IEC 2026 – All rights reserved
ISO/IEC 11179-3:2023/FDAM 1:2026(en)
9.1, Figure 7
Replace Figure 7 with the following:

Figure 7 — Registration metamodel region

© ISO/IEC 2026 – All rights reserved
ISO/IEC 11179-3:2023/FDAM 1:2026(en)
9.4.10.2
Replace the text in 9.4.10.2 with the following:
See registry_claims_conformance association (9.5.9).

9.4.10.3, Table 28
Replace Table 28 with the following:
Table 28 — Attributes of Registry_Specification class
Attribute name Multiplicity Datatype Description
name 1 Sign (6.2.10) Definition: name by which the regis-
try is commonly known
Example: Australian Institute of
Health and Welfare (AIHW) Metadata
[39]
Online Registry (METeOR)
comment 0.1 Text (6.2.12) Definition: any comment that should
be noted about the registry
web_address 0.1 String (6.2.11) Definition: The World Wide Web
uniform resource locator (URL) for
the registry
Example: https:// meteor .aihw .gov
.au/
default_language 0.1 Language_Identification Definition: The language that is used
(6.3.7) as the default in the registry for des-
ignations, definitions and reference
documents.
Examples: eng-840, en-US
alternative_language 0.* Language_Identification Definition: Any other language that is
(6.3.7) used in the registry
Examples: eng-840, en-US
character_repertoire 1 String (6.2.11) Definition: The character repertoire
that is used by the registry for inter-
nal operation
[3]
Example: ISO/IEC 646 or ISO/
[10]
IEC 10646
reference_document_ 0.* String (6.2.11) Definition: Specification of the kind of
identifier_kind identifier used for identifying refer-
ence documents in the registry
Examples: Some registries use URIs.
Other registries use an external
document management system which
provides unstructured, opaque
identifiers. Yet other registries define
a structured identifier form which
embeds an identifier type within
each identifier in the registry. This
attribute specifies the form of identi-
fiers used for reference documents in
this particular registry.
© ISO/IEC 2026 – All rights reserved
ISO/IEC 11179-3:2023/FDAM 1:2026(en)
TTabablele 2 288 ((ccoonnttiinnueuedd))
Attribute name Multiplicity Datatype Description
representation_class_scheme_ 0.1 String (6.2.11) Definition: identifier of the classifica-
id tion scheme used by the registry to
capture representation classes
Changes from previous editions:
[12]
Edition 2 (ISO/IEC 11179-3:2003 )
had a separate structure to record
“representation classes”. In edition
[13])
3 (ISO/IEC 11179-3:2013 and
edition 4 (this document), these are
considered to be just another classifi-
cation scheme, which in edition 3 was
considered a kind of concept system.
This document has restored a Classi-
fication_Scheme class independent
of the Concept_
System class specified in ISO/
IEC 11179-32. This attribute allows
the registration authority to specify
which classification scheme is used
for this purpose. This document uses
just the identifier of the classification
scheme for this attribute. Edition 3
embedded a whole concept system.
context 0.1 Context (6.4.2.3) Definition: context which represents
the registry itself
It is sometimes useful to reference a
default context, rather than create a
new one. This attribute is one possi-
ble choice for such a default.
default_time_zone 0.1 Datetime (6.2.3) (only Definition: time zone to be assumed
hours and minutes are for any datetime instance that does
used) not explicitly specify its own time
zone.
Specified as the number of hours
offset from UTC, with no separator
between hours and minutes, with a
leading zero if the hour is less then 9,
and a leading minus sign if applicable.
Example: For Newfoundland Daylight
Time:  -0230
9.4.10
Add the following new subclause after 9.4.10:
9.4.11  Registry_Conformance class
9.4.11.1  Description of Registry_Conformance
Registry_Conformance specifies the standard(s) to which the registry claims conformance along with the
degree of conformance, level of conformance and other details.
9.4.11.2  Associations of Registry_Conformance
See registry_claims_conformance association (9.5.9).
9.4.11.3  Attributes of Registry_Conformance

© ISO/IEC 2026 – All rights reserved
ISO/IEC 11179-3:2023/FDAM 1:2026(en)
See Table 29.
Table 29 — Attributes of Registry_Conformance class
Attribute name Multiplicity Datatype Description
standard 1 String (6.2.11) Definition: Identifier for the
standard to which this registry
claims conformance.
Example: ISO/IEC 11179-3:2023
degree_of_conformance 0.1 Degree_of_Conformance Definition: ‘conforming’ or
(9.6.1) ‘strictly conforming’. See 4.2.
Condition: applies only if the
specified standard provides
these options.
conformance_level 0.1 String (6.2.11) Definition: The conformance
level of the registry as described
in the standard
Example: Conformance Level 2
(where standard is specified as
ISO/IEC 11179-3:2003).
Condition: applies only if the
specified standard uses con-
formance levels.
Note: This document specifies
conformance labels instead of
conformance levels.
conformance_label 0.1 String (6.2.11) Definition: The conformance
label of the registry as described
in the standard
Example: ISO/IEC 11179-3:2023
Basic Registry (see 4.4.3).
Condition: applies only if the
specified standard uses con-
formance labels.
included_features 0.1 String (6.2.11) Definition: Freeform specifica-
tion of the features of the stand-
ard that this implementation
supports.
Condition: applies only if the
specified standard allows con-
formance by feature (see 4.3).
excluded_features 0.1 String (6.2.11) Definition: Freeform specifica-
tion of the features of the stand-
ard that this implementation
does not support.
Condition: applies only if the
specified standard allows con-
formance by feature (see 4.3).

Renumber all subsequent tables and the references to them.

© ISO/IEC 2026 – All rights reserved
ISO/IEC 11179-3:2023/FDAM 1:2026(en)
9.5.8
Add the following new subclause after 9.5.8:
9.5.9  registry_claims_conformance association
The registry_claims_conformance association records the binding of exactly one instance of the Registry_
Specification (9.4.10) class with zero, one or more instances of the Registry_Conformance class (9.4.11)
which specify the standard(s) to which the registry claims conformance.

Clause 11
Replace Clause 11 with the following:
11   Item_Mapping package
11.1  Overview of the Item_Mapping metamodel region
The Item_Mapping package consists of one region, the Item_Mapping metamodel region, which specifies a
facility to map among registry items in a registry that uses the common facilities specified in this document.

Figure 9 — Item mapping metamodel region

11.2   Classes referenced from the Basic and core package
11.2.1  Item class
11.2.1.1  Description of Item

© ISO/IEC 2026 – All rights reserved
ISO/IEC 11179-3:2023/FDAM 1:2026(en)
Item is part of the Core metamodel and is specified in 6.4.2.1. It is extended here in the Item Mapping
metamodel. It is further extended in the Identification region (see Clause 7), the Designation and Definition
region (see Clause 8), the Classification region (see Clause 10) and indirectly in the Registration region (see
Clause 9).
11.2.1.2  Associations of Item
This metamodel region specifies the following association classes:
— Subject_Mapping association class (11.4.1);
— Object_Mapping association class (11.4.2).
Other associations are added in other metamodel regions where the Item class is extended:
— the Core metamodel region (6.4.2.1.2);
— the Identification metamodel region (7.2.1.2);
— the Designation and Definition metamodel region (8.2.1.2);
— the Classification metamodel region (10.2.1.2);
[17] [18] [19] [20]
— and in ISO/IEC 11179-31 , ISO/IEC 11179-32 , ISO/IEC 11179-33 , ISO/IEC 11179-34 and
[21]
ISO/IEC 11179-35 .
11.2.1.3  Attributes of Item
No attributes are specified in this metamodel region.
11.2.1.4  Subclasses of Item
This metamodel region introduces the following subclasses of Item:
— Item_Mapping class (11.3.1);
— Item_Mapping_Transformation class (11.3.2);
11.3  Classes in the Item_Mapping metamodel region
11.3.1  Item_Mapping class
11.3.1.1  Direct superclass
Item (11.2.1), allowing instances to be identified, registered, administered, named, defined and classified.
11.3.1.2  Description of Item_Mapping
Item_Mapping is a class each instance of which models some part of a mapping of registry items. Each
instance of the Item_Mapping class comprises a Subject_Mapping (11.4.1) set of instances of the Item class
(11.2.1) and an Object_Mapping (11.4.2) set of instances of the Item class that model similar real-world
requirements.
The primary direction of the mapping is from the instances of the subject Items (11.2.1) via instances of
the Subject_Mapping association class (11.4.1) to the instances of the object Items via instances of the
Object_Mapping association class (11.4.2). If the bidirectionality_ind (11.3.1.4) of the instance of the
Item_Mapping class has the value TRUE, then the inverse mapping is also valid.
11.3.1.3  Associations of Item_Mapping
See:
— Subject_Mapping association class (11.4.1);
— Object_Mapping association class (11.4.2);

© ISO/IEC 2026 – All rights reserved
ISO/IEC 11179-3:2023/FDAM 1:2026(en)
— mapping_hierarchy association (11.5.1);
— item_mapping_transformation association (11.5.2);
— mapping_provenance association (11.5.3).
11.3.1.4  Attributes of Item_Mapping
See Table 32.
Table 32 — Attributes of Item_Mapping class
Attribute name Multiplicity Datatype Description
degree 1 Item_Mapping_Degree Definition: specification of the kind of
(11.6.1) mapping between sets of registry items
linked to this instance of Item_Map-
ping
description 0.1 Text (6.2.12) Definition: additional explanation of
the kind of mapping between sets of
registry items linked to this instance of
Item_Mapping, for use especially the
value of the degree attribute is speci-
fied as ‘related to’.
bidirectionality_ind 0.1 Boolean (6.2.2) Definition: indicator as to whether this
instance of Item_Mapping is bidirec-
tional
originator 0.1 Contact (6.3.5) Definition: identification of the Contact
who originated the transformation rule
rationale 0.1 Text (6.2.12) Definition: explanation of the reason
for the transformation
11.3.2  Item_Mapping_Transformation class
11.3.2.1  Direct superclass
Item (11.2.1), allowing instances to be identified, registered, administered, named, defined and classified.
11.3.2.2  Description of Item_Mapping_Transformation
Item_Mapping_Transformation is a class each instance of which specifies a transformation rule used by
an instance of the Item_Mapping class (11.3.1).
11.3.2.3  Associations of Item_Mapping_Transformation
See:
— item_mapping_transformation association (11.5.2);
— structured_transformation_rule association (11.5.7);
— transformation_provenance association (11.5.4).
11.3.2.4  Attributes of Item_Mapping_Transformation
See Table 33.
© ISO/IEC 2026 – All rights reserved
ISO/IEC 11179-3:2023/FDAM 1:2026(en)
Table 33 — Attributes of Item_Mapping_Transformation class
Attribute name Multiplicity Datatype Description
textual_transformation_rule 0.1 Text (6.2.12) Definition: specification of the transfor-
mation to be applied to the subject Item
instance(s) to produce the object Item
instance(s)
rule_notation 0.1 Notation (6.2.7) Conditional.
Definition: designation of the notation
used to specify the rule
[22] [31]
EXAMPLES    EBNF , XCL
Condition: Required if
textual_transformation_rule is present.
implementation_platforms 0.* String (6.2.11) Definition: designation of any platforms
where the rule has been implemented

11.3.3  Provenance class
11.3.3.1  Direct superclass
None.
11.3.3.2  Description of Provenance
Provenance is a class, each instance of which records the provenance of either an instance of the Item_
Mapping (11.3.1) class or an instance of the Item_Mapping_Transformation (11.3.2) class.
11.3.3.3  Associations of Provenance
Provenance has the following assocations:
— mapping_provenance (11.5.3);
— transformation_provenance (11.5.4);
— provenance_review (11.5.5).
11.3.3.4  Attributes of Provenance
See Table 34.
© ISO/IEC 2026 – All rights reserved
ISO/IEC 11179-3:2023/FDAM 1:2026(en)
Table 34 — Attributes of Provenance class
Attribute name Multiplicity Datatype Description
originator 0.1 Contact (6.3.5) Definition: The contact that originated
the related instance of the Item_Map-
ping or Item_Mapping_Transforma-
tion class.
owner 0.1 Contact (6.3.5) Definition: The contact that owns the
related instance of the Item_Mapping
or Item_Mapping_Transformation
class.
created_datetime 1 Datetime (6.2.3) Definition: The date and time when the
related instance of the Item_Mapping
or Item_Mapping_Transformation
class was created.
last_updated_datetime 0.1 Datetime (6.2.3) Definition: The date and time when the
related instance of the Item_Mapping
or Item_Mapping_Transformation
class was last updated.
comment 0.1 Text (6.2.12) Definition: Any additional information
about the related instance of the Item_
Mapping or Item_Mapping_Transfor-
mation class.
11.3.3.5  Constraints on Provenance
Each instance of the Provenance class shall be associated with exactly one instance of the Item_Mapping
(11.3.1) class, or with exactly one instance of the Item_Mapping_Transformation (11.3.2) class, but not
both.
11.3.4  Provenance_Review class
11.3.4.1  Direct superclass
None.
11.3.4.2  Description of Provenance_Review
Provenance_Review is a class, each instance of which records the review of an instance of the Provenance
class (11.3.3).
11.3.4.3  Associations of Provenance_Review
Provenance_Review has the following associations:
— provenance_review (11.5.5);
— provenance_review_approval (11.5.6).
11.3.4.4  Attributes of Provenance_Review
See Table 35.
© ISO/IEC 2026 – All rights reserved
ISO/IEC 11179-3:2023/FDAM 1:2026(en)
Table 35 — Attributes of Provenance_Review class
Attribute name Multiplicity Datatype Description
reviewer 1 Contact (6.3.5) Definition: The contact that performed
the review of the related instance of the
Provenance class.
review_type 0.1 String (6.2.11) Definition: Specification of the type
of review that was performed on the
provenance.
review_date 1 Date (6.2.4) Definition: The date the review was
performed.
review_reason 0.1 Text (6.2.12) Definition: Explanation of why the re-
view was performed.
11.3.5  Provenance_Review_Approval class
11.3.5.1  Direct superclass
None.
11.3.5.2  Description of Provenance_Review_Approval
Provenance_Review_Approval is a class, each instance of which records the approval of an instance of the
Provenance_Review class.
11.3.5.3  Associations of Provenance_Review_Approval
Provenance_Review_Approval has the following assocation:
— provenance_review_approval (11.5.6).
11.3.5.4  Attributes of Provenance_Review_Approval
See Table 36.
Table 36 — Attributes of Provenance_Review_Approval class
Attribute name Multiplicity Datatype Description
approver 1 Contact (6.3.5) Definition: The contact that approved
the review of the related instance of the
Provenance class.
approval_date 1 Date (6.2.4) Definition: The date the review was
approved.
11.4  Association Classes in the Item_Mapping metamodel region
11.4.1  Subject_Mapping association class
11.4.1.1  Description of Subject_Mapping
Subject_Mapping is an association which records the binding of zero, one or more instances of the Item_
Mapping class (11.3.1) with one or more instances of the Item class (11.2.1) which are the subject of the
mapping.
Subject_Mapping is also a class with one attribute as specified in 11.4.1.2.
11.4.1.2  Attributes of Subject_Mapping
See Table 37.
© ISO/IEC 2026 – All rights reserved
ISO/IEC 11179-3:2023/FDAM 1:2026(en)
Table 37 — Attributes of Subject_Mapping association class
Attribute name Multiplicity Datatype Description
mapping_variable_name 0.1 String (6.2.11) Definition: name of the variable used in the Sub-
ject_Mapping in the Item_Mapping_Transforma-
tion. textual_transformation_rule (11.3.2.4).
EXAMPLE See B.3.3 which illustrates the
variables: ‘day’, ‘month’ and ‘year’ in the mapping
of a date to its component data elements.

11.4.2  Object_Mapping association class
11.4.2.1  Description of Object_Mapping
Object_Mapping is an association which records the binding of zero, one or more instances of the Item_
Mapping class (11.3.1) with one or more instances of the Item class (11.2.1) which are the object of the
mapping.
Object_Mapping is also a class with one attribute as specified in 11.4.2.2.
11.4.2.2  Attributes of Object_Mapping
See Table 38.
Table 38 — Attributes of Object_Mapping association class
Attribute name Multiplicity Datatype Description
mapping_variable_name 0.1 String (6.2.11) Definition: name of the variable used in the
Object_Mapping in the Item_Mapping_Transfor-
mation. textual_transformation_rule (11.3.2.4)
EXAMPLE See B.3.3 which illustrates the variables:
‘day’, ‘month’ and ‘year’ in the mapping of a date to
its component data elements.
11.5  Associations in the Item_Mapping metamodel region
11.5.1  mapping_hierarchy association
The mapping_hierarchy association is a reflexive association which records the binding of zero or one
instance of the Item_Mapping (11.3.1) class, each of which represents a superset mapping, to zero, one or
more other instances of the Item_Mapping class, each of which represents a subset mapping. This association
registers any superset-subset hierarchy that exists within a group of the mappings, e.g. when two models
and their model elements are mapped together, the instance of the Item_Mapping class that represents the
top-level mapping of the models will be at the superset end of this association and the instances of the Item_
Mapping class that represent the lower-level mappings of sets of model elements be at the subset end of this
association.
11.5.2  item_mapping_transformation association
The item_mapping_transformation association records the binding of zero, one or more instances of the
Item_Mapping_Transformation (11.3.2) class, each of which specifies a transformation rule, to exactly one
instance of the Item_Mapping class (11.3.1), which represents a mapping of subject Items (11.2.1) to object
Items.
© ISO/IEC 2026 – All rights reserved
ISO/IEC 11179-3:2023/FDAM 1:2026(en)
11.5.3  mapping_provenance association
The mapping_provenance association records the binding of zero or one instances of the Item_Mapping
(11.3.1) class, each of which specifies an item mapping, to zero, one or more instances of the Provenance
(11.3.3) class which records the provenance of the item mapping.
11.5.4  transformation_provenance association
The transformation_provenance association records the binding of zero or one instances of the Item_
Mapping_Transformation (11.3.2) class, each of which specifies an item mapping transformation, to zero,
one or more instances of the Provenance (11.3.3) class which records the provenance of the item mapping
transformation.
11.5.5  provenance_review association
The provenance_review association records the binding of zero, one more instances of the Provenance_
Review (11.3.4) class to exactly one instance of the Provenance (11.3.3) class that the provenance review
is about.
11.5.6  provenance_review_approval association
The provenance_review_approval association records the binding of zero, one more instances of the
Provenance_Review_Approval (11.3.5) class to exactly one instance of the Provenance_Review (11.3.4)
class that the approval is about.
11.5.7  structured_transformation_rule association
The structured_transformation_rule association records the binding of one or more instances of the
Item_Mapping_Transformation (11.3.2) class with zero or one instance of the Rule (11.7.1) class which
provides the details about the transformation rule.
11.6  Datatypes in the Item Mapping metamodel region
11.6.1  Item_Mapping_Degree enumeration
Item_Mapping_Degree is an enumerated datatype with values as shown in Table 39.
Table 39 — Enumeration of Item_Mapping_Degree values
Value Description
related to Indicates that the creator of the mapping has asserted that the subject item(s) and the object
item(s) share some form of relationship other than those explicitly defined by the other values
of Item_Mapping_Degree, and as further explained in the description.
same as Indicates that the creator of the mapping has asserted that the subject item(s) and the object
item(s) have the same semantics and syntax. (I.e., they represent the same thing, though they
necessarily have different identifiers, and may have different names.)
semantically Indicates that the creator of the mapping has asserted that the subject item(s) and the object
equivalent item(s) have the same semantics.
semantically Indicates that the creator of the mapping has asserted that the subject item(s) and the object
similar item(s) are semantically similar although not identical.
derived from Indicates that the creator of the mapping has as
...

ISO/IEC 11179-3:2023/AmdFDAmd 1:2026(en)
ISO/IEC JTC 1/SC 32/WG 2
Secretariat: ANSI
Date: 2026-0102-20
Information technology — Metadata registries (MDR) —
Part 3:
Metamodel for registry common facilities — Amendment
AMENDMENT 1: Enhancements to Item Mapping

DISFDIS stage
Warning for WDs and CDs
© ISO/IEC 2026 – All rights reserved

ISO #####-#:####(X)
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 #### – All rights reserved

ISO/IEC 11179-3:2023/AmdFDAmd 1:2026(en)
© ISO/IEC 2026
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
EmailE-mail: copyright@iso.org
Website: www.iso.orgwww.iso.org
Published in Switzerland
© ISO/IEC 2025 2026 – All rights reserved
iii
ISO/IEC 11179-3:2023/AmdFDAmd 1:2026(en)
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).
ISO and IEC draw attention to the possibility that the implementation of this document may involve the use of
(a) patent(s). ISO and IEC take no position concerning the evidence, validity or applicability of any claimed
patent rights in respect thereof. As of the date of publication of this document, ISO and IEC had not received
notice of (a) patent(s) which may be required to implement this document. However, implementers are
cautioned that this may not represent the latest information, which may be obtained from the patent database
available at www.iso.org/patents and https://patents.iec.ch. ISO and IEC shall not be held responsible for
identifying any or all such patent rights.
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 Amendment 1 provides minor enhancements to the registry specification in Clause 9, major
enhancements to the Item Mapping facility in Clause 11, and adds a new Rules facility as Clause 12 of
ISO/IEC 11179-3:2023.
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.
© ISO/IEC 2026 – All rights reserved
iv
ISO/IEC 11179-3:2023/AmdFDAmd 1:2026(en)
Information technology — Metadata registries (MDR) — —
Part 3:
Metamodel for registry common facilities — Amendment
AMENDMENT 1: Enhancements to Item Mapping

3.2.29
Replace term entry 3.2.29 with the following:
3.2.29
datum (singular)
datums (countable plural)
data (uncountable plural)
designation (3.2.11) whose concept (3.2.7) is a value

3.2.30
Replace term entry 3.2.30 with the following:
3.2.30
metadata
descriptive data (3.2.29) about an object(s) (3.2.1)
Note 1 to entry: In the ISO/IEC 11179 and ISO/IEC 19763 series of standards, the objects being described are instances
of the subclasses of Item (6.4.2.1), e.g. concepts, data elements, services etc.

6.2.1, Figure 2
Replace Figure 2 with the following:

© ISO/IEC 2026 – All rights reserved
ISO/IEC 11179-3:2023/AmdFDAmd 1:2026(en)

Figure 2:— Predefined types metamodel region

© ISO/IEC 2026 – All rights reserved
ISO/IEC 11179-3:2023/AmdFDAmd 1:2026(en)

6.2.13
Insert the following subclause after 6.2.13:
6.2.14  BLOB
BLOB is a datatype which represents a binary large object string datatype.
EXAMPLE : A PDF document to be attached to an instance of the Reference_Document (6.3.8) class.

6.3.1, Figure 3
Replace Figure 3 with the following:

© ISO/IEC 2026 – All rights reserved
ISO/IEC 11179-3:2023/AmdFDAmd 1:2026(en)

Figure 3 –— Basic classes metamodel region

6.3.8.2, Table 7
Append the following row at the end of table Table 7:
document BLOB 0.1 The reference document itself.

9.1, Figure 7
Replace Figure 7 with the following:

© ISO/IEC 2026 – All rights reserved
ISO/IEC 11179-3:2023/AmdFDAmd 1:2026(en)

© ISO/IEC 2026 – All rights reserved
ISO/IEC 11179-3:2023/AmdFDAmd 1:2026(en)

Figure 7 –— Registration metamodel region
9.4.10.2
Replace the text in 9.4.10.2 with the following:
See registry_claims_conformance association (9.5.9).
© ISO/IEC 2026 – All rights reserved
ISO/IEC 11179-3:2023/AmdFDAmd 1:2026(en)

9.4.10.3, Table 28
Replace Table 28 with the following:
Table 28 — Attributes of Registry_Specification class
Attribute name Multiplicity Datatype Description
name 1 Sign (6.2.10) Definition: name by which the
registry is commonly known
Example: Australian Institute of
Health and Welfare (AIHW)
Metadata Online Registry
[39]
(METeOR) )
comment 0.1 Text (6.2.12) Definition: any comment that should
be noted about the registry
web_address 0.1 String (6.2.11) Definition: The World Wide Web
uniform resource locator (URL) for
the registry
Example:
https://meteor.aihw.gov.au/
default_language 0.1 Language_Identification Definition: The language that is used
(6.3.7) as the default in the registry for
designations, definitions and
reference documents.
Examples: eng-840, en-US
alternative_language 0.* Language_Identification Definition: Any other language that
(6.3.7) is used in the registry
Examples: eng-840, en-US
character_repertoire 1 String (6.2.11) Definition: The character repertoire
that is used by the registry for
internal operation
[3]
Example: ISO/IEC 646 or
[10]
ISO/IEC 10646
reference_document_ 0.* String (6.2.11) Definition: Specification of the kind
identifier_kind of identifier used for identifying
reference documents in the registry
Examples: Some registries use URIs.
Other registries use an external
document management system
which provides unstructured,
opaque identifiers. Yet other
registries define a structured
identifier form which embeds an
identifier type within each identifier
in the registry. This attribute
specifies the form of identifiers used
for reference documents in this
particular registry.
representation_class_scheme_ 0.1 String (6.2.11) Definition: identifier of the
id classification scheme used by the
© ISO/IEC 2026 – All rights reserved
ISO/IEC 11179-3:2023/AmdFDAmd 1:2026(en)
Attribute name Multiplicity Datatype Description
registry to capture representation
classes
Changes from previous editions:
Edition 2 (ISO/IEC 11179-
[12]
3:2003 )) had a separate structure
to record “representation classes”.
In edition 3 (ISO/IEC 11179-
[13])
3:2013 and edition 4 (this
document), these are considered to
be just another classification
scheme, which in edition 3 was
considered a kind of concept system.
This document has restored a
Classification_Scheme class
independent of the Concept_
System class specified in
ISO/IEC 11179-32. This attribute
allows the registration authority to
specify which classification scheme
is used for this purpose. This
document uses just the identifier of
the classification scheme for this
attribute. Edition 3 embedded a
whole concept system.
context 0.1 Context (6.4.2.3) Definition: context which represents
the registry itself
It is sometimes useful to reference a
default context, rather than create a
new one. This attribute is one
possible choice for such a default.
default_time_zone 0.1 Datetime (6.2.3) (only Definition: time zone to be assumed
hours and minutes are for any datetime instance that does
used) not explicitly specify its own time
zone.
Specified as the number of hours
offset from UTC, with no separator
between hours and minutes, with a
leading zero if the hour is less then
9, and a leading minus sign if
applicable.
Example: For Newfoundland
Daylight Time:  -0230
9.4.10
Add the following new subclause after 9.4.10:
9.4.11  Registry_Conformance class
9.4.11.1  Description of Registry_Conformance
Registry_Conformance specifies the standard(s) to which the registry claims conformance along with the
degree of conformance, level of conformance and other details.
© ISO/IEC 2026 – All rights reserved
ISO/IEC 11179-3:2023/AmdFDAmd 1:2026(en)
9.4.11.2  Associations of Registry_Conformance
See registry_claims_conformance association (9.5.9).
9.4.11.3  Attributes of Registry_Conformance
See Table 29.
Table 29 — Attributes of Registry_Conformance class
Attribute name Multiplicity Datatype Description
standard 1 String (6.2.11) Definition: Identifier for the
standard to which this registry
claims conformance.
Example: ISO/IEC 11179-
3:2023
degree_of_conformance 0.1 Degree_of_Conformance Definition: ‘conforming’ or
(9.6.1) ‘strictly conforming’. See 4.2.
Condition: applies only if the
specified standard provides
these options.
conformance_level 0.1 String (6.2.11) Definition: The conformance
level of the registry as
described in the standard
Example: Conformance Level 2
(where standard is specified as
ISO/IEC 11179-3:2003).
Condition: applies only if the
specified standard uses
conformance levels.
Note: This document specifies
conformance labels instead of
conformance levels.
conformance_label 0.1 String (6.2.11) Definition: The conformance
label of the registry as
described in the standard
Example: ISO/IEC 11179-
3:2023 Basic Registry (see
4.4.3).
Condition: applies only if the
specified standard uses
conformance labels.
included_features 0.1 String (6.2.11) Definition: Freeform
specification of the features of
the standard that this
implementation supports.
Condition: applies only if the
specified standard allows
conformance by feature (see
4.3).
excluded_features 0.1 String (6.2.11) Definition: Freeform
specification of the features of
the standard that this
© ISO/IEC 2026 – All rights reserved
ISO/IEC 11179-3:2023/AmdFDAmd 1:2026(en)
Attribute name Multiplicity Datatype Description
implementation does not
support.
Condition: applies only if the
specified standard allows
conformance by feature (see
4.3).
Renumber all subsequent tables and the references to them.

9.5.8
Add the following new subclause after 9.5.8:
9.5.9  registry_claims_conformance association
The registry_claims_conformance association records the binding of exactly one instance of the
Registry_Specification (9.4.10) class with zero, one or more instances of the Registry_Conformance class
(9.4.11) which specify the standard(s) to which the registry claims conformance.

Clause 11
Replace Clause 11 with the following:
11  Item_Mapping package
11.1  Overview of the Item_Mapping metamodel region
The Item_Mapping package consists of one region, the Item_Mapping metamodel region, which specifies a
facility to map among registry items in a registry that uses the common facilities specified in this document.

© ISO/IEC 2026 – All rights reserved
ISO/IEC 11179-3:2023/AmdFDAmd 1:2026(en)

Figure 9— Item mapping metamodel region

11.2  Classes referenced from the Basic and core package
© ISO/IEC 2026 – All rights reserved
ISO/IEC 11179-3:2023/AmdFDAmd 1:2026(en)
11.2.1  Item class
11.2.1.1  Description of Item
Item is part of the Core metamodel and is specified in 6.4.2.1. It is extended here in the Item Mapping
metamodel. It is further extended in the Identification region (see Clause 7), the Designation and Definition
region (see Clause 8), the Classification region (see Clause 10) and indirectly in the Registration region (see
Clause 9).
11.2.1.2  Associations of Item
This metamodel region specifies the following association classes:
— — Subject_Mapping association class ();(11.4.1);
— — Object_Mapping association class ().(11.4.2).
Other associations are added in other metamodel regions where the Item class is extended:
— — the Core metamodel region (6.4.2.1.2);
— — the Identification metamodel region (7.2.1.2);
— — the Designation and Definition metamodel region (8.2.1.2);
— — the Classification metamodel region (10.2.1.2);
[17] [18] [19] [20]
— — and in ISO/IEC 11179-31 ,, ISO/IEC 11179-32 ,, ISO/IEC 11179-33 ,, ISO/IEC 11179-34 and
[21]
ISO/IEC 11179-35 .
11.2.1.3  Attributes of Item
No attributes are specified in this metamodel region.
11.2.1.4  Subclasses of Item
This metamodel region introduces the following subclasses of Item:
— — Item_Mapping class ();(11.3.1);
— — Item_Mapping_Transformation class ();(11.3.2);
11.3  Classes in the Item_Mapping metamodel region
11.3.1  Item_Mapping class
11.3.1 Item_Mapping class
11.3.1  .1 Direct superclass
Item (),(11.2.1), allowing instances to be identified, registered, administered, named, defined and classified.
11.3.1.2  Description of Item_Mapping
Item_Mapping is a class each instance of which models some part of a mapping of registry items. Each
instance of the Item_Mapping class comprises a Subject_Mapping ()(11.4.1) set of instances of the Item class
© ISO/IEC 2026 – All rights reserved
ISO/IEC 11179-3:2023/AmdFDAmd 1:2026(en)
()(11.2.1) and an Object_Mapping ()(11.4.2) set of instances of the Item class that model similar real-world
requirements.
The primary direction of the mapping is from the instances of the subject Items ()(11.2.1) via instances of the
Subject_Mapping association class ()(11.4.1) to the instances of the object Items via instances of the
Object_Mapping association class ().(11.4.2). If the bidirectionality_ind ()(11.3.1.4) of the instance of the
Item_Mapping class has the value TRUE, then the inverse mapping is also valid.
11.3.1.3  Associations of Item_Mapping
See:
— — Subject_Mapping association class ();(11.4.1);
— — Object_Mapping association class ();(11.4.2);
— — mapping_hierarchy association ();(11.5.1);
— — item_mapping_transformation association ();(11.5.2);
— — mapping_provenance association ().(11.5.3).
11.3.1.4  Attributes of Item_Mapping
See Table 32.
Table 32 — Attributes of Item_Mapping class
Attribute name Multiplicity Datatype Description
degree 1 Item_Mapping_Degree Definition: specification of the kind of
()(11.6.1) mapping between sets of registry
items linked to this instance of
Item_Mapping
description 0.1 Text (6.2.12) Definition: additional explanation of
the kind of mapping between sets of
registry items linked to this instance
of Item_Mapping, for use especially
the value of the degree attribute is
specified as ‘related to’.
bidirectionality_ind 0.1 Boolean (6.2.2) Definition: indicator as to whether this
instance of Item_Mapping is
bidirectional
originator 0.1 Contact (6.3.5) Definition: identification of the
Contact who originated the
transformation rule
rationale 0.1 Text (6.2.12) Definition: explanation of the reason
for the transformation
11.3.2  Item_Mapping_Transformation class
11.3.2.1  Direct superclass
© ISO/IEC 2026 – All rights reserved
ISO/IEC 11179-3:2023/AmdFDAmd 1:2026(en)
Item (),(11.2.1), allowing instances to be identified, registered, administered, named, defined and classified.
11.3.2.2  Description of Item_Mapping_Transformation
Item_Mapping_Transformation is a class each instance of which specifies a transformation rule used by an
instance of the Item_Mapping class ().(11.3.1).
11.3.2.3  Associations of Item_Mapping_Transformation
See:
— — item_mapping_transformation association ();(11.5.2);
— — structured_transformation_rule association ();(11.5.7);
— — transformation_provenance association ().(11.5.4).
11.3.2.4  Attributes of Item_Mapping_Transformation
See Table 33.
Table 33 — Attributes of Item_Mapping_Transformation class
Attribute name Multiplicity Datatype Description
textual_transformation_rule 0.1 Text (6.2.12) Definition: specification of the
transformation to be applied to the
subject Item instance(s) to produce the
object Item instance(s)
rule_notation 0.1 Notation (6.2.7) Conditional.
Definition: designation of the notation
used to specify the rule
EXAMPLES    EBNF, XCL
rule_notation 0.1 Notation (6.2.7)
Merged Cells
Conditional.
Definition: designation of the notation
Merged Cells
used to specify the
Merged Cells
textual_transformation_rule
[22] [31]
EXAMPLES EBNF , XCL
Condition: Required if
textual_transformation_rule is present.
implementation_platforms 0.* String (6.2.11) Definition: designation of any platforms
where the
Item_Mapping_Transformation and any
associations haverule has been
implemented
11.3.3  Provenance class
11.3.3.1  Direct superclass
None.
© ISO/IEC 2026 – All rights reserved
ISO/IEC 11179-3:2023/AmdFDAmd 1:2026(en)
11.3.3.2  Description of Provenance
Provenance is a class, each instance of which records the provenance of either an instance of the
Item_Mapping ()(11.3.1) class or an instance of the Item_Mapping_Transformation ()(11.3.2) class.
11.3.3.3  Associations of Provenance
Provenance has the following assocations:
— — mapping_provenance ();(11.5.3);
— — transformation_provenance ();(11.5.4);
— — provenance_review ().(11.5.5).
11.3.3.3.4  Attributes of Provenance
See Table 34.
Table 34 — Attributes of Provenance class
Attribute name Multiplicity Datatype Description
originator 0.1 Contact (6.3.5) Definition: The contact that originated
the related instance of the
Item_Mapping or
Item_Mapping_Transformation class.
owner 0.1 Contact (6.3.5) Definition: The contact that owns the
related instance of the Item_Mapping
or Item_Mapping_Transformation
class.
created_datetime 1 Datetime (6.2.3) Definition: The date and time when the
related instance of the Item_Mapping
or Item_Mapping_Transformation
class was created.
last_updated_datetime 0.1 Datetime (6.2.3) Definition: The date and time when the
related instance of the Item_Mapping
or Item_Mapping_Transformation
class was last updated.
comment 0.1 Text (6.2.12) Definition: Any additional information
about the related instance of the
Item_Mapping or
Item_Mapping_Transformation class.

11.3.3.5  Constraints on Provenance
Each instance of the Provenance class shall be associated with exactly one instance of the Item_Mapping
()(11.3.1) class, or with exactly one instance of the Item_Mapping_Transformation ()(11.3.2) class, but not
both.
11.3.4  Provenance_Review class
11.3.4.1  Direct superclass
© ISO/IEC 2026 – All rights reserved
ISO/IEC 11179-3:2023/AmdFDAmd 1:2026(en)
None.
11.3.4.2  Description of Provenance_Review
Provenance_Review is a class, each instance of which records the review of an instance of the Provenance
class ().(11.3.3).
11.3.4.3  Associations of Provenance_Review
Provenance_Review has the following assocationsassociations:
— — provenance_review ();(11.5.5);
— — provenance_review_approval ().(11.5.6).
11.3.4.4  Attributes of Provenance_Review
See Table 35.
Table 35 — Attributes of Provenance_Review class
Attribute name Multiplicity Datatype Description
reviewer 1 Contact (6.3.5) Definition: The contact that performed
the review of the related instance of
the Provenance class.
review_type 0.1 String (6.2.11) Definition: Specification of the type of
review that was performed on the
provenance.
review_date 1 Date (6.2.4) Definition: The date the review was
performed.
review_reason 0.1 Text (6.2.12) Definition: Explanation of why the
review was performed.
11.3.5  Provenance_Review_Approval class
11.3.5.1  Direct superclass
None.
11.3.5.2  Description of Provenance_Review_Approval
Provenance_Review_Approval is a class, each instance of which records the approval of an instance of the
Provenance_Review class.
11.3.5.3  Associations of Provenance_Review_Approval
Provenance_Review_Approval has the following assocation:
— — provenance_review_approval ().(11.5.6).
11.3.5.4  Attributes of Provenance_Review_Approval
© ISO/IEC 2026 – All rights reserved
ISO/IEC 11179-3:2023/AmdFDAmd 1:2026(en)
See Table 36.
Table 36 — Attributes of Provenance_Review_Approval class
Attribute name Multiplicity Datatype Description
approver 1 Contact (6.3.5) Definition: The contact that approved
the review of the related instance of
the Provenance class.
approval_date 1 Date (6.2.4) Definition: The date the review was
approved.
11.4  Association Classes in the Item_Mapping metamodel region
11.4.1  Subject_Mapping association class
11.4.1.1  Description of Subject_Mapping
Subject_Mapping is an association which records the binding of zero, one or more instances of the
Item_Mapping class ()(11.3.1) with one or more instances of the Item class ()(11.2.1) which are the subject
of the mapping.
Subject_Mapping is also a class with one attribute as specified in .11.4.1.2.
11.4.1.2  Attributes of Subject_Mapping
See Table 37.
Table 37 — Attributes of Subject_Mapping association class
Attribute name Multiplicity Datatype Description
mapping_variable_name 0.1 String (6.2.11) Definition: name of the variable used in the
Subject_Mapping in the
Item_Mapping_Transformation.
textual_transformation_rule ().(11.3.2.4).
EXAMPLE See B.3.3 which illustrates the
variables: ‘day’, ‘month’ and ‘year’ in the mapping
of a date to its component data elements.

11.4.2  Object_Mapping association class
11.4.2.1  Description of Object_Mapping
Object_Mapping is an association which records the binding of zero, one or more instances of the
Item_Mapping class ()(11.3.1) with one or more instances of the Item class ()(11.2.1) which are the object of
the mapping.
Object_Mapping is also a class with one attribute as specified in .11.4.2.2.
11.4.2.2  Attributes of Object_Mapping
© ISO/IEC 2026 – All rights reserved
ISO/IEC 11179-3:2023/AmdFDAmd 1:2026(en)
See Table 38.
Table 38 — Attributes of Object_Mapping association class
Attribute name Multiplicity Datatype Description
mapping_variable_name 0.1 String (6.2.11) Definition: name of the variable used in the
Object_Mapping in the
Item_Mapping_Transformation.
textual_transformation_rule ()(11.3.2.4)
EXAMPLE See B.3.3 which illustrates the variables:
‘day’, ‘month’ and ‘year’ in the mapping of a date to
its component data elements.
11.5  Associations in the Item_Mapping metamodel region
11.5.1  mapping_hierarchy association
The mapping_hierarchy association is a reflexive association which records the binding of zero or one
instance of the Item_Mapping ()(11.3.1) class, each of which represents a superset mapping, to zero, one or
more other instances of the Item_Mapping class, each of which represents a subset mapping. This association
registers any superset-subset hierarchy that exists within a group of the mappings, e.g. when two models and
their model elements are mapped together, the instance of the Item_Mapping class that represents the top-
level mapping of the models will be at the superset end of this association and the instances of the
Item_Mapping class that represent the lower-level mappings of sets of model elements be at the subset end
of this association.
11.5.2  item_mapping_transformation association
The item_mapping_transformation association records the binding of zero, one or more instances of the
Item_Mapping_Transformation ()(11.3.2) class, each of which specifies a transformation rule, to exactly one
instance of the Item_Mapping class (),(11.3.1), which represents a mapping of subject Items ()(11.2.1) to
object Items.
11.5.3  mapping_provenance association
The mapping_provenance association records the binding of zero or one instances of the Item_Mapping
()(11.3.1) class, each of which specifies an item mapping, to zero, one or more instances of the Provenance
()(11.3.3) class which records the provenance of the item mapping.
11.5.4  transformation_provenance association
The transformation_provenance association records the binding of zero or one instances of the
Item_Mapping_Transformation ()(11.3.2) class, each of which specifies an item mapping transformation, to
zero, one or more instances of the Provenance ()(11.3.3) class which records the provenance of the item
mapping transformation.
11.5.5  provenance_review association
The provenance_review association records the binding of zero, one more instances of the
Provenance_Review ()(11.3.4) class to exactly one instance of the Provenance ()(11.3.3) class that the
provenance review is about.
© ISO/IEC 2026 – All rights reserved
ISO/IEC 11179-3:2023/AmdFDAmd 1:2026(en)
11.5.6  provenance_review_approval association
The provenance_review_approval association records the binding of zero, one more instances of the
Provenance_Review_Approval ()(11.3.5) class to exactly one instance of the Provenance_Review ()(11.3.4)
class that the approval is about.
11.5.7  structured_transformation_rule association
The structured_transformation_rule association records the binding of one or more instances of the
Item_Mapping_Transformation ()(11.3.2) class with zero or one instance of the Rule ()(11.7.1) class which
provides the details about the transformation rule.
11.6  Datatypes in the Item Mapping metamodel region
11.6.1  Item_Mapping_Degree enumeration
Item_Mapping_Degree is an enumerated datatype with values as shown in Table 39.
Table 39 — Enumeration of Item_Mapping_Degree values
Value Description
related to Indicates that the creator of the mapping has asserted that the subject item(s) and the object
item(s) share some form of relationship other than those explicitly defined by the other values
of Item_Mapping_Degree, and as further explained in the description.
same as Indicates that the creator of the mapping has asserted that the subject item(s) and the object
item(s) have the same semantics and syntax. (I.e., they represent the same thing, though they
necessarily have different identifiers, and may have different names.)
semantically Indicates that the creator of the mapping has asserted that the subject item(s) and the object
equivalent item(s) have the same semantics.
semantically Indicates that the creator of the mapping has asserted that the subject item(s) and the object
similar item(s) are semantically similar although not identical.
derived from Indicates that the creator of the mapping has asserted that the subject item(s) have been used
in the creation of the object item(s). Inverse of “has derivation”.
has derivation Indicates that the creator of the mapping has asserted that the object item(s) have been used in
the creation of the subject item(s). Inverse of “derived from”.
broader than Indicates that the creator of the mapping has asserted that the subject item(s) and the object
item(s) are linked, and that the object item(s) have a broader meaning than the subject item(s).
Inverse of “narrower than”.
narrower than Indicates that the creator of the mapping has asserted that the subject item(s) and the object
item(s) are linked, and that the object item(s) have a narrower meaning than the subject
item(s). Inverse of “broader than”.
child
...