ISO/IEC 11179-3:2013/Amd 1:2020

INTERNATIONAL ISO/IEC
STANDARD 11179-3
Third edition
2013-02-15
AMENDMENT 1
2020-01
Information technology — Metadata
registries (MDR) —
Part 3:
Registry metamodel and basic
attributes
AMENDMENT 1
Technologies de l'information — Registres de métadonnées (RM) —
Partie 3: Métamodèle de registre et attributs de base
AMENDEMENT 1
Reference number
ISO/IEC 11179-3:2013/Amd.1:2020(E)
©
ISO/IEC 2020

---------------------- Page: 1 ----------------------
ISO/IEC 11179-3:2013/Amd.1:2020(E)

COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2020
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
Fax: +41 22 749 09 47
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO/IEC 2020 – All rights reserved

---------------------- Page: 2 ----------------------
ISO/IEC 11179-3:2013/Amd.1:2020(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).
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 http:// 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.
This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 32, Data management and interchange.
A list of all parts in the ISO/IEC 11179 series can be found on the ISO website.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www .iso .org/ members .html.
© ISO/IEC 2020 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO/IEC 11179-3:2013/Amd.1:2020(E)
Information technology — Metadata registries (MDR) —
Part 3:
Registry metamodel and basic attributes
AMENDMENT 1

3.1, 3.2
Change all references to "datatype (3.1.8)" to "datatype (3.1.9)".

3.1.13
Change the reference in the source from "7.3.37" to "7.3.38".

3.2.9
Replace the definition with:
attribute (3.1.4) of a metadata item (3.2.75) commonly needed in its specification

3.2.50
Replace the definition with:
metadata item (3.2.75) which can have designations (3.2.51) and/or definitions (3.2.40)

3.2.75
In NOTE 1, replace 'Clauses 5 through 11' with 'Clauses 9 through 11'.

3.2.76
In the NOTE, replace 'Clauses 5 through 11' with 'Clauses 9 through 11'.

3.2.96
Replace the existing NOTE by the following:
Note 1 to entry: Permissible values may be specified either as part of a value domain (3.2.140), or only
associated with a value meaning (3.2.141).
Note 2 to entry: Within a value domain, permissible values may either be enumerated or described.
© ISO/IEC 2020 – All rights reserved 1

---------------------- Page: 4 ----------------------
ISO/IEC 11179-3:2013/Amd.1:2020(E)

Note 3 to entry: Explicit mapping of a single permissible value to a single value meaning is possible only
when both the value meaning and permissible value are enumerated, e.g. for code sets. For described
permissible values, the described meaning might be associated with a range of values, e.g. weight in
kilograms.

3.2.105
Replace the definition with the following:
identified_item (3.2.64) that is recorded and managed in a metadata registry (3.2.78)

3.2.138
In NOTE 2, replace 'must' with 'shall'.

3.2
Add the following new terms and definitions:
3.2.143
conceptual domain definition
formal definition of a defined conceptual domain (3.2.144)
Note 1 to entry: The definition may reference externally enumerated value meanings.
3.2.144
defined conceptual domain
conceptual domain (3.2.21) that is specified by a formal definition
Note 1 to entry: The definition may reference externally enumerated value meanings.
3.2.145
defined value domain
value domain (3.2.140) that is specified by reference to an external specification
Note 1 to entry: The external specification should enumerate the permissible values.

3.3.24
Replace 'XTML' with 'XTM'.

Clauses 4 through 12
Replace all occurrences of 'must' in normative text with 'shall', except for:
— 7.3.2.7.2.4 where 'must' should simply be deleted;
— 9.1.2.5.3.1 where 'must' is correct;
— 11.1.1 replace 'must' with 'should';
— 11.4.2.3.2 where 'must' is correct;
— Annexes C, D and F, which are informative.
2 © ISO/IEC 2020 – All rights reserved

---------------------- Page: 5 ----------------------
ISO/IEC 11179-3:2013/Amd.1:2020(E)

4.2.2
Replace the whole subclause with the following:
A strictly conforming implementation:
a) shall support all mandatory, optional and conditional classes, attributes and associations;
b) shall not use, test, access, or probe for any extension features nor extensions to classes, attributes
and/or associations;
c) shall not recognize, nor act on, nor allow the production of classes, attributes and/or associations
that are dependent on any unspecified, undefined, or implementation-defined behaviour.
NOTE The use of extensions to the metamodel or the basic attributes can cause undefined behaviour.

4.3
Rename 4.3 to 'Conformance by feature'.
Append:
", or to specific features within these clauses"
at the end of the first sentence of 4.3.

4.4.2
Add the following NOTE at the end of 4.4.2:
NOTE The additional provisions specified in the above profiles apply only to these profiles, and not to
conformance by feature in 4.3.

5.4
Replace the sentence:
"Clauses 6 through 11 of this part of ISO/IEC 11179 specify the types of metadata objects that form the
structure of a metadata registry."
With:
"Clauses 6 through 8 of this part of ISO/IEC 11179 specify common facilities that form the core of a
metadata registry and which apply to potentially any type of registry content. Clauses 9 through 11
of this part of ISO/IEC 11179 specify the types of metadata objects that form the potential content of a
metadata registry."

5.5.1, list item 2, NOTE
Replace the reference to ISO/IEC 19763-2 with ISO/IEC 19763-10.

Clause 6 (except 6.3.3.1 and 6.3.5.1, see below), and 7.3.2.1:
Change all references to "datatype (3.1.8)" to " datatype (3.1.9)".
© ISO/IEC 2020 – All rights reserved 3

---------------------- Page: 6 ----------------------
ISO/IEC 11179-3:2013/Amd.1:2020(E)

6.3.3.1 and 6.3.5.1
Change all references to "composite datatype (3.1.8)" to "composite datatype (3.1.7)".

8.1.1, paragraph 1
Replace the second sentence with the following:
ISO/IEC 11179-6 further describes the registration of Registered_Items (8.1.2.1), Administered_Items
(8.1.2.2) and Attached_Items (8.1.2.3).

8.1.1, Figure 7
Replace Figure 7 with the following:
4 © ISO/IEC 2020 – All rights reserved

---------------------- Page: 7 ----------------------
ISO/IEC 11179-3:2013/Amd.1:2020(E)

8.1.2.9.1, list item 1, and Annex A, name (attribute of Registry_Specification)
Replace the reference to 8.1.2.9.2.1.1 with 8.1.2.9.2.1.

8.1.2.9.2
Change the subclause number of 8.1.2.9.2.1.1 to 8.1.2.9.2.1.

© ISO/IEC 2020 – All rights reserved 5

---------------------- Page: 8 ----------------------
ISO/IEC 11179-3:2013/Amd.1:2020(E)

8.1.5.1.1, paragraph 1
Insert the following after the first sentence:
The association has two roles:
— authority (verb form: has_authority) which references a Registration_Authority class;
— administered_item (verb form: for_administered_item) which references an Administered_Item class.
An authority may have zero or more administered_items. An administered_item shall have one or more
authorities.

8.1.5.2.1, paragraph 1
Insert the following after the first sentence:
The association has two roles:
— document_reference (verb form: has_document_reference) which references a Reference_
Document class;
— referencing_item (verb form: is_referencing_item) which references a Registered_Item class.
A document_reference may have zero or more referencing_items. A referencing_item may have zero or
more document_references.

11.2.2.3.2, paragraph 1
In the last sentence, replace "in the form of" with "by".

11.3.1, Figure 13
Replace Figure 13 with the following:
6 © ISO/IEC 2020 – All rights reserved

---------------------- Page: 9 ----------------------
ISO/IEC 11179-3:2013/Amd.1:2020(E)


11.3.2.5.2.3
Designate the existing NOTE as NOTE 1, and add the following NOTE:
NOTE 2 maximum_character_quantity is intended to be specified primarily for described value domains. If
specified for enumerated_value_domains, care should be taken to ensure the specified value is consistent with
the enumerated permissible values.
© ISO/IEC 2020 – All rights reserved 7

---------------------- Page: 10 ----------------------
ISO/IEC 11179-3:2013/Amd.1:2020(E)

11.3.2.9
At the end of 11.3.2.9, insert subclauses 11.3.2.10 through 11.3.2.14:

11.3.2.10  Conceptual_Domain_Definition class
11.3.2.10.1  Description of Conceptual_Domain_Definition
Conceptual_Domain_Definition is a class, each instance of which models a conceptual domain definition
(3.2.144), a formal definition of a defined conceptual domain (3.2.145).
Conceptual_Domain_Definition shall participate in a domain_definition association (11.3.3.7) with
exactly one Defined_Conceptual_Domain (11.3.2.11).
11.3.2.10.2  Attributes of Conceptual_Domain_Definition
11.3.2.10.2.1  definition_expression
Attribute name: definition_expression
Definition: formal definition of the conceptual_domain expressed in some formal grammar
Obligation: Mandatory
Multiplicity: 1
Datatype: Text (6.2.12)
11.3.2.10.2.2  definition_grammar
Attribute name: definition_grammar
Definition: name of the grammar used in definition_expression
Obligation: Mandatory
Multiplicity: 1
Datatype: String (6.2.11)
11.3.2.10.2.3  source_uri
Attribute name: source_uri
Definition: Uri for the source of the Conceptual_Domain_Definition
Obligation: Optional
Multiplicity: 0.1
Datatype: String (6.2.11)
—— End of attributes of Conceptual_Domain_Definition ——
11.3.2.11  Defined_Conceptual_Domain class
11.3.2.11.1  Direct superclass
Conceptual_Domain (11.3.2.1).
8 © ISO/IEC 2020 – All rights reserved

---------------------- Page: 11 ----------------------
ISO/IEC 11179-3:2013/Amd.1:2020(E)

11.3.2.11.2  Description of Defined_Conceptual_Domain
Defined_Conceptual_Domain is a class, each instance of which models a defined conceptual domain
(3.2.145).
As a subclass of Conceptual_Domain, Defined_Conceptual_Domain inherits the associations of the former.
In addition, Defined_Conceptual_Domain shall participate in a domain_definition association with one or
more Conceptual_Domain_Definitions.
Where multiple Conceptual_Domain_Definitions are specified, the definition_expression (11.3.2.10.2.1) of
each shall be equivalent, each specified using a different definition_grammar (11.3.2.10.2.2).
11.3.2.11.3  Attributes of Defined_Conceptual_Domain
11.3.2.11.3.1  begin_date
Attribute name: begin_date
Definition: date on which this Defined_Conceptual_Domain became, or will become, a valid
Defined_Conceptual_Domain
Obligation: Mandatory
Multiplicity: 1
Datatype: Date (6.2.3)
NOTE A registration authority can determine whether this date is the date the defined
conceptual domain becomes valid in a registry, or the date the defined conceptual
domain becomes part of the source domain, or some other date.
11.3.2.11.3.2  end_date
Attribute name: end_date
Definition: date on which the Defined_Conceptual_Domain ceased, or will cease, to be valid.
Obligation: Optional
Multiplicity: 0.1
Datatype: Date (6.2.3)
NOTE 1 The absence of the end_date indicates that the Defined_Conceptual_Domain is still valid.
NOTE 2 A registration authority can determine whether this date is the date the defined
conceptual domain becomes no longer valid in a registry, or the date the defined
conceptual domain becomes no longer part of the source domain, or some other date.
11.3.2.11.3.3  locked_date
Attribute name: locked_date
Definition: date on which the set of Defined_Value_Meanings associated with the Defined_Con-
ceptual_Domain was, or will be, locked.
Obligation: Optional
Multiplicity: 0.1
Datatype: Date (6.2.3)
© ISO/IEC 2020 – All rights reserved 9

---------------------- Page: 12 ----------------------
ISO/IEC 11179-3:2013/Amd.1:2020(E)

11.3.2.11.3.4  expanded_on
Attribute name: expanded_on
Definition: datetime at which the set of Defined_Value_Meanings associated with the Defined_Con-
ceptual_Domain was expanded and imported into the registry.
Obligation: Optional
Multiplicity: 0.1
Datatype: Datetime (6.2.4)
—— End of attributes of Defined_Conceptual_Domain ——
11.3.2.12  Defined_Value_Meaning class
11.3.2.12.1  Direct superclass
Defined_Value_Meaning is a subclass of Concept (6.4.2.2, 9.1.2.1).
11.3.2.12.2  Description of Defined_Value_Meaning
Defined_Value_Meaning is a class, each instance of which models a value meaning (3.2.142), which
provides semantic content of a possible value.
NOTE Defined_Value_Meaning is like Value_Meaning (11.3.2.8), except importing the value meanings for a
Defined_Conceptual_Domain is optional, and if done will be done as a set, so the begin_date and end_date attributes
reside on the domain instead of the individual values.
Defined_Value_Meaning shall participate in a defined_value_meaning_set association (11.3.3.8) with one
or more Defined_Conceptual_Domains (11.3.2.11).
Defined_Value_Meaning may participate in a defined_permissible_value_meaning (11.3.3.9) association
with zero or more Defined_Permissible_Values (11.3.2.14).
11.3.2.12.3  Attributes of Defined_Value_Meaning
None.
11.3.2.13  Defined_Value_Domain class
11.3.2.13.1  Direct superclass
Value_Domain (11.3.2.8)
11.3.2.13.2  Description of Defined_Value_Domain
Defined_Value_Domain is a class each instance of which models a defined value domain (3.2.145), a
value domain (3.2.140) that is specified by a reference to an external source of all its permissible values
(3.2.96). The external source is specified by the associated the Defined_Conceptual_Domain (11.3.2.11),
in conjunction with the fieldname_for_permitted_value attribute.
NOTE A Defined_Value_Domain is like an Enumerated_Value_Domain (11.3.2.6), except the enumerated
values are referenced from the external source that specifies the Defined_Conceptual_Domain (11.3.2.11), and the
permissible values could or could not be imported into the registry. If the permissible values are imported, then
they are imported as a set, so the begin_date and end_date attributes are specified on the Defined_Value_Domain
instead of on the individual Permissible_Values (11.3.2.7).
Each Defined_Value_Domain class may participate in the association:
— defined_pe
...