ISO/IEC 20944-5:2013

Information technology — Metadata Registries Interoperability and Bindings (MDR-IB) — Part 5: Profiles

The ISO/IEC 20944 series of International Standards provides the bindings and their interoperability for metadata registries, such as those specified in the ISO/IEC 11179 series of International Standards. ISO/IEC 20944-5:2013 contains provisions that are common to the profiles, and the profiles themselves. A profile of ISO/IEC 11179-3:2003 is included, which maps ISO/IEC 11179 metadata attributes to standardized identifiers for navigation and access of ISO/IEC 11179 metadata.

Technologies de l'information — Interopérabilité et liaisons des registres de métadonnées (MDR-IB) — Partie 5: Profils

General Information

• Status: Published
• Publication Date: 07-Jan-2013
• ICS: 35.040 - Information coding
• ICS: 35.040.50 - Automatic identification and data capture techniques
• Technical Committee: ISO/IEC JTC 1/SC 32 - Data management and interchange
• Drafting Committee: ISO/IEC JTC 1/SC 32/WG 2 - MetaData
• Current Stage: 9020 - International Standard under periodical review
• Start Date: 15-Jul-2024
• Completion Date: 15-Jul-2024

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 20944-5
First edition
2013-01-15
Information technology — Metadata
Registries Interoperability and Bindings
(MDR-IB) —
Part 5:
Profiles
Technologies de l'information — Interopérabilité et liaisons des registres
de métadonnées (MDR-IB) —
Partie 5: Profils
Reference number
©
ISO/IEC 2013
©  ISO/IEC 2013
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56  CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail [e-mail]
Web www.iso.org
Published in Switzerland
ii © ISO/IEC 2013 – All rights reserved

Contents Page
Foreword . iv
Introduction . v
1  Scope . 1
2  Normative references . 1
3  Terms and definitions . 1
4  Attribute mapping for ISO/IEC 11179-3 MDR metamodel . 2
4.1  General . 2
4.2  Value space of labels . 2
4.3  Available labels . 2
4.4  Label formation . 2
4.5  Resolving conflicts . 4
4.6  Additional provisions . 4
4.7  Identifier mappings . 5
4.8  Conformance label . 13
5  Profile for ISO/IEC 11179-3 MDR metamodel . 13
5.1  General . 13
5.2  Profile . 14
5.3  Conformance label . 14
Annex A (informative) Developing and using profiles . 15
Bibliography . 17

© ISO/IEC 2013 – All rights reserved iii

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. In the field of information
technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of the joint technical committee is to prepare International Standards. Draft International
Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as
an International Standard requires approval by at least 75 % of the national bodies casting a vote.
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.
ISO/IEC 20944-5 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 32, Data management and interchange.
ISO/IEC 20944 consists of the following parts, under the general title Information technology — Metadata
Registries Interoperability and Bindings (MDR-IB):
 Part 1: Framework, common vocabulary, and common provisions for conformance
 Part 2: Coding bindings
 Part 3: API bindings
 Part 4: Protocol bindings
 Part 5: Profiles
iv © ISO/IEC 2013 – All rights reserved

Introduction
This part of ISO/IEC 20944 contains provisions that are common to the profiles, and the profiles themselves.
It is intended that this part of ISO/IEC 20944 will be extended, via amendments or revisions, as additional
profiles are established.
© ISO/IEC 2013 – All rights reserved v

INTERNATIONAL STANDARD ISO/IEC 20944-5:2013(E)

Information technology — Metadata Registries Interoperability
and Bindings (MDR-IB) —
Part 5:
Profiles
1 Scope
The ISO/IEC 20944 series of International Standards describe codings, application programming interfaces
(APIs), and protocols for interacting with an ISO/IEC 11179 metadata registry (MDR).
This part of ISO/IEC 20944 specifies the common provisions for profiles using the ISO/IEC 20944 series.
This part of ISO/IEC 20944 specifies mapping of metamodel attributes, as specified in ISO/IEC 11179-3, to
identifiers for the purpose of navigating metadata registries.
2 Normative references
The following referenced documents are indispensable for the application 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 Guide 2, Standardization and related activities — General vocabulary
ISO/IEC TR 10000-1, Information technology — Framework and taxonomy of International Standardized
Profiles — Part 1: General principles and documentation framework
ISO/IEC 11179-3:2003, Information technology — Metadata registries (MDR) — Part 3: Registry metamodel
and basic attributes
ISO/IEC 20944-1:2013, Information technology — Metadata Registries Interoperability and Bindings (MDR-
IB) — Framework, common vocabulary, and common provisions for conformance
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO/IEC 20944-1 apply.

Users and implementers of this part of ISO/IEC 20944 may find it useful to reference the terms and definitions from
ISO/IEC 20944-1.
© ISO/IEC 2013 – All rights reserved 1

4 Attribute mapping for ISO/IEC 11179-3 MDR metamodel
4.1 General
The identifiers in this clause provide a common mapping to the attributes of the ISO/IEC 11179-3 metamodel.
Although the identifiers describe a hierarchical path, there is no requirement that the metamodel be organized
or implemented in a hierarchical structure.
4.2 Value space of labels
The value space of possible labels (i.e., navigable identifiers) is the value space defined by the
ISO/IEC 11404 datatype:
type character_based_multiple_identifier =
array (0.*) of ( characterstring(iso-10646) )
NOTE The characterstring datatype is used for representing labels, such as metamodel attribute identifiers (e.g.,
"units_of_measure"), and used for representing array indexes (e.g., the string "0" represents the index of the first element
of an array).
4.3 Available labels
The value space is the set of characterstrings.
4.4 Label formation
The ISO/IEC 11179-3 registry metamodel describes a data model (for metadata) in UML notation. The
following conventions apply with respect to mapping ISO/IEC 11179-3 metamodel attributes to navigable
identifiers that may be used to access the data of the metamodel attribute (i.e., metadata).
4.4.1 Semantic provisions
The ISO/IEC 11179-3 metamodel uses a limited set of UML metaobjects (UML features) from the UML
notation. The ISO/IEC 11179-3 metamodel employs the following constraints or assumptions:
 A limited set of UML metaobjects are used: classes, attributes, containment, relations, objectified relations,
specialization.
 Classes only have attributes and relations; classes do not have methods.
 All attributes are public.
 Specialized classes only use single inheritance.
These UML notational features are transformed as follows:
 UML class notation: UML classes are comprised of UML attributes and UML relations. From the class, this
part of ISO/IEC 20944 describes navigation to the attributes and, if navigable, navigation to the
relationship.
The distinction between possible and available is: the "possible" concerns the value space from which the labels are
chosen, while the "available" concerns those ones that are valid. For example, in North America, phone numbers come
from a possible list of 10-digit numbers "nnn-nnn-nnnn", but not all possible numbers are available, e.g., numbers whose
first digits are 0 or 1 are not available (e.g., "022-222-2222" is not available).
2 © ISO/IEC 2013 – All rights reserved

 UML attributes: An attribute is navigated according to the access operations supported by its datatype.
For example, an array is accessed by its index; a record is accessed by the labels of its components.
 UML relations: A relation may be navigated from its roles (sides) that support navigation. Objectified
relations may be navigated from the relation's roles that support navigation.
 UML containment relations: A containment relation may be navigated from its parent.
 UML relations' role's multiplicity: A cardinality of 0.1 or 1.1 may be navigated directly by the relation role.
A cardinality of 0.* or 1.* may be navigated as an array of relations for the particular role.
Other constraints and provisions of the ISO/IEC 11179-3 metamodel are contained in the normative wording
of ISO/IEC 11179-3.
Inheritance is simulated by copying all the attributes and relationships of the base type to the subtype, e.g. if
"Y" is derived from the base type "X", and "X" has attributes "A" and "B", and relation "C", and "Y" has
attributes "D" and "E", then an instance of "Y" has the navigable identifiers "a", "b", "c_relation", "d", and "e".
A conforming implementation shall map the labels defined in this Clause to a conforming ISO/IEC 11179-3
metadata registry
4.4.2 Syntactic provisions
The following are syntax requirements
 All identifiers that refer to classes have the suffix "_class" added to the identifier, e.g., the "Representation
Class" class, becomes "representation_class_class".
 All identifiers that refer to navigable relations have the suffix "_relation" added to the identifier (e.g.,
"classifying_relation", "classified_by_relation").
 Containment relationships are represented by the component name (and not "Containing"), e.g., the
"Classification Scheme" class contains a "Classification Scheme Item" class which is represented by
"classification_scheme_membership"; in other words, if "X" represents an instance of the "Classification
Scheme" class, then "X/classification_scheme_membership" represents an instance(s) of the
"Classification Scheme Item" (see below for more information on indexing notation for this particular class).
 Attributes of objectified relationships are accessed via the "_relation" access token, e.g., if "X" is an
instance of an "administered_item_class", then "X/having_relation/P/_relation/terminological_entry"
represents a component of the "terminological_entry" objectified relation class.
 Attributes and relationships with cardinality "[1.1]" are represented without indexing.
 Attributes and relationships with cardinality "[0.1]" are represented without indexing. Note: In the case of
zero instances, it is assumed that the implementation will have some technique for determining whether or
not the optional feature is present.
 Attributes and relationships with other cardinalities (e.g., "[0.*]", "[1.*]") are accessed via an indexing
mechanism, e.g., if "X" is an instance of the "language_section_class", then "X/name_entry/0",
"X/name_entry/1", "X/name_entry/2", etc., may represent the identifiers associated with each of the
"name_entry"s.
 The slash character "/" is used to separate components of a navigation identifier. Note that individual
bindings may use different component separators and other syntax conventions.
© ISO/IEC 2013 – All rights reserved 3

4.4.3 Lexical provisions
The following are lexical provisions
 All identifier are transformed to lower case, spaces are transformed to underscores, and other punctuation
is removed, e.g., "Context (for administered item)" becomes "context_for_administered_item".
 All id
...