ISO/IEC 19763-16:2021
(Main)Information technology — Metamodel framework for interoperability (MFI) — Part 16: Metamodel for document model registration
Information technology — Metamodel framework for interoperability (MFI) — Part 16: Metamodel for document model registration
The primary purpose of the ISO/IEC 19763 series is to specify a metamodel framework for interoperability. This document specifies a metamodel for registering document models (or schemata). Examples of such document models include: — specifications for XML documents (using XML schema[3]); — specifications for JSON documents (using JSON schema[2]). This metamodel was developed taking into account the requirements for both XML schema and JSON schema, but is applicable to all current specifications for document models.
Titre manque — Partie 16: Titre manque
General Information
Buy Standard
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 19763-16
First edition
2021-09
Information technology — Metamodel
framework for interoperability
(MFI) —
Part 16:
Metamodel for document model
registration
Reference number
ISO/IEC 19763-16:2021(E)
©
ISO/IEC 2021
---------------------- Page: 1 ----------------------
ISO/IEC 19763-16:2021(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2021
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 © ISO/IEC 2021 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 19763-16:2021(E)
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms, definitions and abbreviated terms . 1
3.1 Terms and definitions . 1
3.2 Abbreviated terms . 2
4 Conformance . 2
4.1 General . 2
4.2 Degree of conformance . 2
4.2.1 General. 2
4.2.2 Strictly conforming implementation . 3
4.2.3 Conforming implementation . 3
4.3 Implementation conformance statement (ICS) . 3
5 Structure of MFI Document model registration . 3
5.1 Overview of MFI Document model registration . 3
5.2 Association between MFI Document model registration and MFI Core and mapping . 5
5.3 Metaclasses in MFI Document model registration . 6
5.3.1 Document_Schema . 6
5.3.2 Document_Schema_Language . 7
5.3.3 Document_Schema_Namespace . 7
5.3.4 Enumerated_Node . 8
5.3.5 Namespace . 8
5.3.6 Node . 8
5.3.7 Node_Enumeration . 9
5.3.8 Node_Relationship.10
5.3.9 Node_Relationship_Type .10
5.3.10 Restricted_Node.11
5.3.11 Schema_Reuse .11
5.3.12 Schema_Reuse_Type .12
Annex A (informative) Description of the metamodel .13
Annex B (informative) Relationship of metaclasses to the MDR Metamodel .18
Annex C (informative) Examples of document model registration .19
Bibliography .67
© ISO/IEC 2021 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/IEC 19763-16:2021(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 patents.iec.ch).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to the
World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see www .iso .org/
iso/ foreword .html. In the IEC, see www .iec .ch/ understanding -standards.
This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 32, Data management and interchange.
A list of all parts in the ISO/IEC 19763 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.
iv © ISO/IEC 2021 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC 19763-16:2021(E)
Introduction
There is an increasing demand for systems to interoperate by exchanging information and data. These
exchanges are sometimes performed using 'documents' such as XML documents and JSON documents.
The business information requirements conveyed by these documents are often specified in supporting
document models, for example, in XML schemas for XML documents and in JSON schemas for JSON
documents.
The information contained in these models – the metadata – can be registered using the facilities
specified by this document. Most of the metaclasses specified in this document are subclasses of the
metaclasses specified in ISO/IEC 19763-10:2014, 7.1, 7.2 and 7.3.
Where there is an overlap of the universe of discourse of the business information requirements
specified in the registered models, the mappings between registered models can then be registered
using the facilities specified in ISO/IEC 19763-10:2014, Clause 8, thus enabling further interoperation.
A model registry, as specified using any of the metamodels described in ISO/IEC 19763, uses the
common facilities specified in ISO/IEC 11179-3:2013, Clauses 6, 7 and 8. A model registry is, therefore,
a part of a metadata registry.
© ISO/IEC 2021 – All rights reserved v
---------------------- Page: 5 ----------------------
INTERNATIONAL STANDARD ISO/IEC 19763-16:2021(E)
Information technology — Metamodel framework for
interoperability (MFI) —
Part 16:
Metamodel for document model registration
1 Scope
The primary purpose of the ISO/IEC 19763 series is to specify a metamodel framework for
interoperability. This document specifies a metamodel for registering document models (or schemata).
Examples of such document models include:
[3]
— specifications for XML documents (using XML schema );
[2]
— specifications for JSON documents (using JSON schema ).
This metamodel was developed taking into account the requirements for both XML schema and JSON
schema, but is applicable to all current specifications for document models.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
ISO/IEC 19763-10:2014, Information technology — Metamodel framework for interoperability (MFI) —
Part 10: Core model and basic mapping
ISO/IEC 11179-3:2013, Information technology — Metadata registries (MDR) — Part 3: Registry
metamodel and basic attributes
3 Terms, definitions and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/
3.1.1
document
unit of data that is well-formed according to some agreed specification
Note 1 to entry: In this document, examples of a unit of data that is referred to as a document include, but are not
restricted to, XML documents and JSON documents.
[SOURCE: ISO/IEC TR 24716:2007, 4.4, modified — Note 1 has been added.]
© ISO/IEC 2021 – All rights reserved 1
---------------------- Page: 6 ----------------------
ISO/IEC 19763-16:2021(E)
3.1.2
document schema
formal specification of the structure of a document (3.1.1)
Note 1 to entry: The same schema can be used for multiple documents.
3.1.3
document schema language
language used to specify document schemata
3.1.4
namespace
set of character strings available for naming entities of specific classes within a specific scope
3.1.5
node
elements, comments, processing instructions, and text in a document
[SOURCE: ISO 24531:2013, 4.35 modified — The definition in the source document specifically referred
to XML documents but is applicable to all documents; the references to XML and Note 1 have been
removed.]
3.1.6
node enumeration
list of named values used as the range of a particular node (3.1.5)
3.2 Abbreviated terms
Abbreviated terms Definition
JSON JavaScript Object Notation
MFI Core and mapping Metamodel Framework for Interoperability Core and mapping
a
MFI Document model registration Metamodel Framework for Interoperability document model
registration
MDR Metamodel Metadata registries metamodel
URL Uniform Resource Locator
XML eXtensible Markup Language
a
Whenever this abbreviation is used, this document is referring to itself.
4 Conformance
4.1 General
Any claim of conformance to this document shall support the metamodel specified in Clause 5,
depending on a degree of conformance as described below.
4.2 Degree of conformance
4.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, but are not specified by this document.
2 © ISO/IEC 2021 – All rights reserved
---------------------- Page: 7 ----------------------
ISO/IEC 19763-16:2021(E)
A strictly conforming implementation may be limited in usefulness but is maximally interoperable
with respect to this document. A conforming implementation may be more useful but may be less
interoperable with respect to this document.
4.2.2 Strictly conforming implementation
A strictly conforming implementation:
a) shall support the metamodel specified in Clause 5;
b) shall not use, test, access, or probe for any extension features nor extensions to the metamodel
specified in Clause 5.
4.2.3 Conforming implementation
A conforming implementation:
a) shall support the metamodel specified in Clause 5;
b) as permitted by the implementation, may use, test, access, or probe for any extension features or
extensions to the metamodel specified in Clause 5.
NOTE 1 All strictly conforming implementations are also conforming implementations.
NOTE 2 The use of extensions to the metamodel can cause undefined behaviour.
4.3 Implementation conformance statement (ICS)
Any claim of conformance to this document shall include an implementation conformance statement
stating:
a) whether it is a strictly conforming implementation (4.2.2) or a conforming implementation (4.2.3);
b) what extensions, if any, are supported or used if it is a conforming implementation.
5 Structure of MFI Document model registration
5.1 Overview of MFI Document model registration
Figure 1 shows the metamodel for the registration of document models such as XML schemas and JSON
schemas.
© ISO/IEC 2021 – All rights reserved 3
---------------------- Page: 8 ----------------------
ISO/IEC 19763-16:2021(E)
Figure 1 — Metamodel of MFI Document model registration
The metamodel for document model registration comprises the following metaclasses:
— Document_Schema
— Document_Schema_Language
— Document_Schema_Namespace
— Enumerated_Node, a subclass of Restricted_Node
4 © ISO/IEC 2021 – All rights reserved
---------------------- Page: 9 ----------------------
ISO/IEC 19763-16:2021(E)
— Namespace (which shall be in accordance with ISO/IEC 11179-3:2013, 7.2.2.3)
— Node
— Node_Enumeration
— Node_Relationship
— Node_Relationship_Type
— Restricted_Node, a subclass of Node
— Schema_Reuse
— Schema_Reuse_Type
The metamodel is described in detail in Annex A. Detailed specifications of the metaclasses are provided
in 5.3.
Examples of the registration of document models using this metamodel are provided in Annex C.
5.2 Association between MFI Document model registration and MFI Core and mapping
The associations between the metaclasses specified in this document and the metaclasses in MFI Core
and mapping (ISO/IEC 19763-10:2014, 7.1, 7.2 and 7.3) are shown in Figure 2.
Key
specialisation of metaclasses
Figure 2 — Associations between MFI Document model registration
and MFI Core and mapping
Document_Schema_Language in this document is a specialisation of (or subclass of) Modelling_
Language (in accordance with ISO/IEC 19763-10:2014, 7.1).
Document_Schema in this document is a specialisation of Model (in accordance with
ISO/IEC 19763-10:2014, 7.2).
All the remaining metaclasses are specialisations of Model_Element (in accordance with
ISO/IEC 19763-10:2014, 7.3).
The association between Document_Schema and Document_Schema_Language in this document is a
specialisation of the association between Model (in accordance with ISO/IEC 19763-10:2014, 7.2) and
Modelling_Language (in accordance with ISO/IEC 19763-10:2014, 7.1).
© ISO/IEC 2021 – All rights reserved 5
---------------------- Page: 10 ----------------------
ISO/IEC 19763-16:2021(E)
The association between Document_Schema and the remaining metaclasses specified in this document
are specializations of the association between Model (in accordance with ISO/IEC 19763-10:2014, 7.2)
and Model_Element (in accordance with ISO/IEC 19763-10:2014, 7.3).
MFI Core and mapping (ISO/IEC 19763-10:2014, Clause 9) explains that instances of the metaclasses
specified in 5.3 can be extended by the types defined in ISO/IEC 11179-3:2013, Clauses 7 and 8. Annex B
provides suggested type extension for each of the metaclasses specified in 5.3.
5.3 Metaclasses in MFI Document model registration
5.3.1 Document_Schema
Document_Schema is a metaclass each instance of which represents a representation of a particular
document schema.
Superclass
Model (which shall be in accordance with ISO/IEC 19763-10:2014, 7.2)
Attribute DataType Multiplicity Description
name String 1.1 A statement specifying the name by which this
document schema is known.
context String 0.1 A statement describing the universe of discourse
covered by this document schema.
revision_status String 0.1 A statement describing revision or version status of this
document schema.
Reference Class Multiplicity Description Inverse Precedence
describing_ Document_ 1.1 The document schema expressed_ No
language Schema_ language in which schema
Language this schema is expressed.
roled_ Document_ 0.* The set of namespaces named_ Yes
namespace Schema_ that are cited in this schema
Namespace schema.
node_model_ Node 1.* The set of nodes containing_ Yes
element contained within this schema
document schema.
subject_reuse Schema_Reuse 0.* The set of schema reused_ Yes
reuses that record that schema
this schema is reused
within another schema
(the recipient schema) or as
a node in another schema
(the recipient
node).
object_reuse Schema_Reuse 0.* The set of schema reuses recipient_ Yes
that record that this schema
schema reuses another
schema (the reused
schema).
Constraints
[None]
6 © ISO/IEC 2021 – All rights reserved
---------------------- Page: 11 ----------------------
ISO/IEC 19763-16:2021(E)
5.3.2 Document_Schema_Language
Document_Schema_Language is a metaclass each instance of which represents a representation of a
particular document schema language.
Superclass
Modelling_Language (which shall be in accordance with ISO/IEC 19763-10:2014, 7.1)
Attribute DataType Multiplicity Description
name String 1.1 A statement specifying the name by which this
document schema language is known.
version String 0.1 A statement specifying the version of this
particular document schema language.
encoding String 0.1 A statement specifying the encoding that is used
within this particular document schema
language.
url String 0.1 A statement specifying the URL that may be used to
access the specification of this particular
document schema language.
further_details String 0.1 A statement providing any necessary further details
necessary to unambiguously specify this particular
document schema language.
Reference Class Multiplicity Description Inverse Precedence
expressed_schema Document_Schema 0.* The set of describing_language Yes
document
schemas that
are expressed
in this
language.
Constraints
[None]
5.3.3 Document_Schema_Namespace
Document_Schema_Namespace is a metaclass each instance of which represents a representation of a
particular namespace that is cited within a schema.
Superclass
Model_Element (which shall be in accordance with ISO/IEC 19763-10:2014, 7.3)
Attribute DataType Multiplicity Description
role String 1.1 A statement specifying the role that this particular namespace
is playing within the related document schema. Examples are
“Target”, “Prefix” and “Default”.
Reference Class Multiplicity Description Inverse Precedence
cited_namespace Namespace 1.1 The namespace cited used_namespace No
for use with this role
in the related
document schema.
named_schema Document_ 1.1 The document roled_namespace No
Schema schema for which this
namespace is specified
with this role.
Constraints
[None]
© ISO/IEC 2021 – All rights reserved 7
---------------------- Page: 12 ----------------------
ISO/IEC 19763-16:2021(E)
5.3.4 Enumerated_Node
Enumerated_Node is a metaclass each instance of which represents a representation of a particular
type of node within a schema, a restricted node for which there is a set of permitted values specified for
the restricted node.
Superclass
Restricted_Node
Attribute DataType Multiplicity Description
[None]
Reference Class Multiplicity Description Inverse Precedence
node_ Node_ 2.* The set of valid enumerated_ Yes
enumeration Enumeration values for this node. node
Constraints
[None]
5.3.5 Namespace
Namespace is a metaclass defined in ISO/IEC 11179-3:2013, 7.2.2.3. It is shown here to indicate the
additional reference required for this document.
Superclass
[None]
Attribute DataType Multiplicity Description
[None]
Reference Class Multiplicity Description Inverse Precedence
used_namespace Document_Schema_ 0.* The set of cited_namespace Yes
Namespace document
schema
namespace
within which
this
namespace is
the cited
namespace.
Constraints
[None]
5.3.6 Node
Node is a metaclass each instance of which represents a representation of a particular node within a
schema. Node has one subclass; Enumerated_Node.
Superclass
Model_Element (which shall be in accordance with ISO/IEC 19763-10:2014, 7.3)
Attribute DataType Multiplicity Description
name String 0.1 A statement specifying the name for this node.
type String 0.1 A statement specifying the type of this node. Examples are
“simple”, “complex”, “group”, “sequence”, “choice”, “element”
and “attribute”.
8 © ISO/IEC 2021 – All rights reserved
---------------------- Page: 13 ----------------------
ISO/IEC 19763-16:2021(E)
namespace String 0.1 A statement specifying the namespace to be used for this node.
This shall only exist if the namespace for the node differs
from the namespace specified as the default namespace for
the document schema of which this node is a component part
or if there is no default specified for the document schema.
datatype String 0.1 A statement specifying the datatype for this node.
minimum_ String 0.1 A statement of the minimum number of occurrences of
occurrences values of this node. In most circumstances this will be “0”
(indicating that the note is optional) or “1” (indicating that
the node is mandatory).
maximum_ String 0.1 A statement of the maximum number of occurrences of
occurrences values of this node. In most circumstances this will be “1”
or “unbounded”.
Reference Class Multiplicity Description Inverse Precedence
containing_ Document_ 1.1 The schema that node_model_ No
schema Schema contains this node. element
object_reuse Schema_ 0.* The set of schema recipient_ Yes
Reuse reuses that record that node
this node reuses a
schema (the reused
schema).
inferior_ Node_ 0.* The set of node parent_node Yes
relationship Relationship relationships through
which this
node is the parent of
other nodes.
superior_ Node_ 0.* The set of node child_node Yes
relationship Relationship relationships through
which this node is the
child of other nodes.
Constraints
[None]
5.3.7 Node_Enumeration
Node_Enumeration is a metaclass each instance of which represents a representation of a particular
permitted value for an enumerated node.
Superclass
Model_Element (which shall be in accordance with ISO/IEC 19763-10:2014, 7.3)
Attribute DataType Multiplicity Description
value String 1.1 A specification of the actual permitted value.
annotation String 0.1 A statement describing the meaning of the value.
Reference Class Multiplicity Description Inverse Precedence
enumerated_ Enumerated_ 1.1 The enumerated node_ No
node Node node for which this enumeration
value is a permitted
value.
Constraints
[None]
© ISO/IEC 2021 – All rights reserved 9
---------------------- Page: 14 ----------------------
ISO/IEC 19763-16:2021(E)
5.3.8 Node_Relationship
Node_Relationship is a metaclass each instance of which represents a representation of a particular
relationship between two nodes.
Superclass
Model_Element (which shall be in accordance with ISO/IEC 19763-10:2014, 7.3)
Attribute DataType Multiplicity Description
[None]
Reference Class Multiplicity Description Inverse Precedence
node_ Node_ 1.1 The categorisation of this categorised_ No
relationship_ Relationship_ node relationship. node_
categorisation Type relationship
parent_node Node 1.1 The referenced node that inferior_ No
is the parent node in this relationship
node
relationship.
child_node Node 1.* The set of referenced superior_ No
nodes, each element of relationship
which is a child node in
this node relationship.
Constraints
[None]
5.3.9 Node_Relationship_Type
Node_Relationship_Type is a metaclass each instance of which represents a representation of a
particular categorisation of a set of node relationships.
Superclass
Model_Element (which shall be in accordance with ISO/IEC 19763-10:2014, 7.3)
Attribute DataType Multiplicity Description
designation String 1.1 A statement specifying the category of the associated node
relationships.
description String 0.1 A statement explaining the meaning of the designation
statement for this node relationship type.
Reference Class Multiplicity Description Inverse Precedence
categorised_ Node_ 0.* The set of node re- node_ Yes
node_ Relationship lationships that are relationship_
relationship categorised by this categorisation
node relationship
type.
Constraints
[None]
10 © ISO/IEC 2021 – All rights reserved
---------------------- Page: 15 ----------------------
ISO/IEC 19763-16:2021(E)
5.3.10 Restricted_Node
Restricted_Node is a metaclass each instance of which represents a representation of a particular type
of node within a schema, a node for which there is a restriction, such as a pattern, placed upon the
values of the node.
Superclass
Node
Attribute DataType Multiplicity Description
restriction_base String 0.1 A statement specifying the datatype within which each of
the values of the node is to be specified.
restriction_ String 0.1 A statement specifying any pattern that is to be applied to
pattern the values specified for the node.
Reference Class Multiplicity Description Inverse Precedence
[None]
Constraints
[None]
5.3.11 Schema_Reuse
Schema_Reuse is a metaclass each instance of which represents a representation of a particular schema
reuse within another schema or of a particular schema reuse as a node within a schema.
Superclass
Model_Element (which shall be in accordance with ISO/IEC 19763-10:2014, 7.3)
Attribute DataType Multiplicity Description
associated_ String 0.1 A statement of any namespace associated with the reused
namespace schema.
Reference Class Multiplicity Description Inverse Precedence
schema_reuse_ Schema_Reuse_ 1.1 The categorised_schema_ No
categorisation Type categorisation reuse
of this schema
reuse.
reused_schema Docume
...
INTERNATIONAL ISO/IEC
STANDARD 19763-16
First edition
Information technology — Metamodel
framework for interoperability
(MFI) —
Part 16:
Metamodel for document model
registration
PROOF/ÉPREUVE
Reference number
ISO/IEC 19763-16:2021(E)
©
ISO/IEC 2021
---------------------- Page: 1 ----------------------
ISO/IEC 19763-16:2021(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2021
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 2021 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 19763-16:2021(E)
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms, definitions and abbreviated terms . 1
3.1 Terms and definitions . 1
3.2 Abbreviated terms . 2
4 Conformance . 2
4.1 General . 2
4.2 Degree of conformance . 2
4.2.1 General. 2
4.2.2 Strictly conforming implementation . 3
4.2.3 Conforming implementation . 3
4.3 Implementation conformance statement (ICS) . 3
5 Structure of MFI Document model registration . 3
5.1 Overview of MFI Document model registration . 3
5.2 Association between MFI Document model registration and MFI Core and mapping . 5
5.3 Metaclasses in MFI Document model registration . 6
5.3.1 Document_Schema . 6
5.3.2 Document_Schema_Language . 7
5.3.3 Document_Schema_Namespace . 7
5.3.4 Enumerated_Node . 8
5.3.5 Namespace . 8
5.3.6 Node . 8
5.3.7 Node_Enumeration . 9
5.3.8 Node_Relationship.10
5.3.9 Node_Relationship_Type .10
5.3.10 Restricted_Node.11
5.3.11 Schema_Reuse .11
5.3.12 Schema_Reuse_Type .12
Annex A (informative) Description of the metamodel .13
Annex B (informative) Relationship of metaclasses to the MDR Metamodel .18
Annex C (informative) Examples of document model registration .19
Bibliography .67
© ISO/IEC 2021 – All rights reserved PROOF/ÉPREUVE iii
---------------------- Page: 3 ----------------------
ISO/IEC 19763-16:2021(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 patents.iec.ch).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to the
World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see www .iso .org/
iso/ foreword .html. In the IEC, see www .iec .ch/ understanding -standards.
This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 32, Data management and interchange.
A list of all parts in the ISO/IEC 19763 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.
iv PROOF/ÉPREUVE © ISO/IEC 2021 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC 19763-16:2021(E)
Introduction
There is an increasing demand for systems to interoperate by exchanging information and data. These
exchanges are sometimes performed using 'documents' such as XML documents and JSON documents.
The business information requirements conveyed by these documents are often specified in supporting
document models, for example, in XML schemas for XML documents and in JSON schemas for JSON
documents.
The information contained in these models – the metadata – can be registered using the facilities
specified by this document. Most of the metaclasses specified in this document are subclasses of the
metaclasses specified in ISO/IEC 19763-10:2014, 7.1, 7.2 and 7.3.
Where there is an overlap of the universe of discourse of the business information requirements
specified in the registered models, the mappings between registered models can then be registered
using the facilities specified in ISO/IEC 19763-10:2014, Clause 8, thus enabling further interoperation.
A model registry, as specified using any of the metamodels described in ISO/IEC 19763, uses the
common facilities specified in ISO/IEC 11179-3:2013, Clauses 6, 7 and 8. A model registry is, therefore,
a part of a metadata registry.
© ISO/IEC 2021 – All rights reserved PROOF/ÉPREUVE v
---------------------- Page: 5 ----------------------
INTERNATIONAL STANDARD ISO/IEC 19763-16:2021(E)
Information technology — Metamodel framework for
interoperability (MFI) —
Part 16:
Metamodel for document model registration
1 Scope
The primary purpose of the ISO/IEC 19763 series is to specify a metamodel framework for
interoperability. This document specifies a metamodel for registering document models (or schemata).
Examples of such document models include:
[3]
— specifications for XML documents (using XML schema );
[2]
— specifications for JSON documents (using JSON schema ).
This metamodel was developed taking into account the requirements for both XML schema and JSON
schema, but is applicable to all current specifications for document models.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
ISO/IEC 19763-10:2014, Information technology — Metamodel framework for interoperability (MFI) —
Part 10: Core model and basic mapping
ISO/IEC 11179-3:2013, Information technology — Metadata registries (MDR) — Part 3: Registry
metamodel and basic attributes
3 Terms, definitions and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the following terms and definitions 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/
3.1.1
document
unit of data that is well-formed according to some agreed specification
Note 1 to entry: In this document, examples of a unit of data that is referred to as a document include, but are not
restricted to, XML documents and JSON documents.
[SOURCE: ISO/IEC TR 24716:2007, 4.4, modified — Note 1 has been added.]
© ISO/IEC 2021 – All rights reserved PROOF/ÉPREUVE 1
---------------------- Page: 6 ----------------------
ISO/IEC 19763-16:2021(E)
3.1.2
document schema
formal specification of the structure of a document (3.1.1)
Note 1 to entry: The same schema can be used for multiple documents.
3.1.3
document schema language
language used to specify document schemata
3.1.4
namespace
set of character strings available for naming entities of specific classes within a specific scope
3.1.5
node
elements, comments, processing instructions, and text in a document
[SOURCE: ISO 24531:2013, 4.35 modified — The definition in the source document specifically referred
to XML documents but is applicable to all documents; the references to XML and Note 1 have been
removed.]
3.1.6
node enumeration
list of named values used as the range of a particular node (3.1.5)
3.2 Abbreviated terms
Abbreviated terms Definition
JSON JavaScript Object Notation
MFI Core and mapping Metamodel Framework for Interoperability Core and mapping
a
MFI Document model registration Metamodel Framework for Interoperability document model
registration
MDR Metamodel Metadata registries metamodel
URL Uniform Resource Locator
XML eXtensible Markup Language
a
Whenever this abbreviation is used, this document is referring to itself.
4 Conformance
4.1 General
Any claim of conformance to this document shall support the metamodel specified in Clause 5,
depending on a degree of conformance as described below.
4.2 Degree of conformance
4.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, but are not specified by this document.
2 PROOF/ÉPREUVE © ISO/IEC 2021 – All rights reserved
---------------------- Page: 7 ----------------------
ISO/IEC 19763-16:2021(E)
A strictly conforming implementation may be limited in usefulness but is maximally interoperable
with respect to this document. A conforming implementation may be more useful but may be less
interoperable with respect to this document.
4.2.2 Strictly conforming implementation
A strictly conforming implementation:
a) shall support the metamodel specified in Clause 5;
b) shall not use, test, access, or probe for any extension features nor extensions to the metamodel
specified in Clause 5.
4.2.3 Conforming implementation
A conforming implementation:
a) shall support the metamodel specified in Clause 5;
b) as permitted by the implementation, may use, test, access, or probe for any extension features or
extensions to the metamodel specified in Clause 5.
NOTE 1 All strictly conforming implementations are also conforming implementations.
NOTE 2 The use of extensions to the metamodel can cause undefined behaviour.
4.3 Implementation conformance statement (ICS)
Any claim of conformance to this document shall include an implementation conformance statement
stating:
a) whether it is a strictly conforming implementation (4.2.2) or a conforming implementation (4.2.3);
b) what extensions, if any, are supported or used if it is a conforming implementation.
5 Structure of MFI Document model registration
5.1 Overview of MFI Document model registration
Figure 1 shows the metamodel for the registration of document models such as XML schemas and JSON
schemas.
© ISO/IEC 2021 – All rights reserved PROOF/ÉPREUVE 3
---------------------- Page: 8 ----------------------
ISO/IEC 19763-16:2021(E)
Figure 1 — Metamodel of MFI Document model registration
The metamodel for document model registration comprises the following metaclasses:
— Document_Schema
— Document_Schema_Language
— Document_Schema_Namespace
— Enumerated_Node, a subclass of Restricted_Node
4 PROOF/ÉPREUVE © ISO/IEC 2021 – All rights reserved
---------------------- Page: 9 ----------------------
ISO/IEC 19763-16:2021(E)
— Namespace (which shall be in accordance with ISO/IEC 11179-3:2013, 7.2.2.3)
— Node
— Node_Enumeration
— Node_Relationship
— Node_Relationship_Type
— Restricted_Node, a subclass of Node
— Schema_Reuse
— Schema_Reuse_Type
The metamodel is described in detail in Annex A. Detailed specifications of the metaclasses are provided
in 5.3.
Examples of the registration of document models using this metamodel are provided in Annex C.
5.2 Association between MFI Document model registration and MFI Core and mapping
The associations between the metaclasses specified in this document and the metaclasses in MFI Core
and mapping (ISO/IEC 19763-10:2014, 7.1, 7.2 and 7.3) are shown in Figure 2.
Key
specialisation of metaclasses
Figure 2 — Associations between MFI Document model registration
and MFI Core and mapping
Document_Schema_Language in this document is a specialisation of (or subclass of) Modelling_
Language (in accordance with ISO/IEC 19763-10:2014, 7.1).
Document_Schema in this document is a specialisation of Model (in accordance with
ISO/IEC 19763-10:2014, 7.2).
All the remaining metaclasses are specialisations of Model_Element (in accordance with
ISO/IEC 19763-10:2014, 7.3).
The association between Document_Schema and Document_Schema_Language in this document is a
specialisation of the association between Model (in accordance with ISO/IEC 19763-10:2014, 7.2) and
Modelling_Language (in accordance with ISO/IEC 19763-10:2014, 7.1).
© ISO/IEC 2021 – All rights reserved PROOF/ÉPREUVE 5
---------------------- Page: 10 ----------------------
ISO/IEC 19763-16:2021(E)
The association between Document_Schema and the remaining metaclasses specified in this document
are specializations of the association between Model (in accordance with ISO/IEC 19763-10:2014, 7.2)
and Model_Element (in accordance with ISO/IEC 19763-10:2014, 7.3).
MFI Core and mapping (ISO/IEC 19763-10:2014, Clause 9) explains that instances of the metaclasses
specified in 5.3 can be extended by the types defined in ISO/IEC 11179-3:2013, Clauses 7 and 8. Annex B
provides suggested type extension for each of the metaclasses specified in 5.3.
5.3 Metaclasses in MFI Document model registration
5.3.1 Document_Schema
Document_Schema is a metaclass each instance of which represents a representation of a particular
document schema.
Superclass
Model (which shall be in accordance with ISO/IEC 19763-10:2014, 7.2)
Attribute DataType Multiplicity Description
name String 1.1 A statement specifying the name by which this
document schema is known.
context String 0.1 A statement describing the universe of discourse
covered by this document schema.
revision_status String 0.1 A statement describing revision or version status of this
document schema.
Reference Class Multiplicity Description Inverse Precedence
describing_ Document_ 1.1 The document schema expressed_ No
language Schema_ language in which schema
Language this schema is expressed.
roled_ Document_ 0.* The set of namespaces named_ Yes
namespace Schema_ that are cited in this schema
Namespace schema.
node_model_ Node 1.* The set of nodes containing_ Yes
element contained within this schema
document schema.
subject_reuse Schema_Reuse 0.* The set of schema reused_ Yes
reuses that record that schema
this schema is reused
within another schema
(the recipient schema) or as
a node in another schema
(the recipient
node).
object_reuse Schema_Reuse 0.* The set of schema reuses recipient_ Yes
that record that this schema
schema reuses another
schema (the reused
schema).
Constraints
[None]
6 PROOF/ÉPREUVE © ISO/IEC 2021 – All rights reserved
---------------------- Page: 11 ----------------------
ISO/IEC 19763-16:2021(E)
5.3.2 Document_Schema_Language
Document_Schema_Language is a metaclass each instance of which represents a representation of a
particular document schema language.
Superclass
Modelling_Language (which shall be in accordance with ISO/IEC 19763-10:2014, 7.1)
Attribute DataType Multiplicity Description
name String 1.1 A statement specifying the name by which this
document schema language is known.
version String 0.1 A statement specifying the version of this
particular document schema language.
encoding String 0.1 A statement specifying the encoding that is used
within this particular document schema
language.
url String 0.1 A statement specifying the URL that may be used to
access the specification of this particular
document schema language.
further_details String 0.1 A statement providing any necessary further details
necessary to unambiguously specify this particular
document schema language.
Reference Class Multiplicity Description Inverse Precedence
expressed_schema Document_Schema 0.* The set of describing_language Yes
document
schemas that
are expressed
in this
language.
Constraints
[None]
5.3.3 Document_Schema_Namespace
Document_Schema_Namespace is a metaclass each instance of which represents a representation of a
particular namespace that is cited within a schema.
Superclass
Model_Element (which shall be in accordance with ISO/IEC 19763-10:2014, 7.3)
Attribute DataType Multiplicity Description
role String 1.1 A statement specifying the role that this particular namespace
is playing within the related document schema. Examples are
“Target”, “Prefix” and “Default”.
Reference Class Multiplicity Description Inverse Precedence
cited_namespace Namespace 1.1 The namespace cited used_namespace No
for use with this role
in the related
document schema.
named_schema Document_ 1.1 The document roled_namespace No
Schema schema for which this
namespace is specified
with this role.
Constraints
[None]
© ISO/IEC 2021 – All rights reserved PROOF/ÉPREUVE 7
---------------------- Page: 12 ----------------------
ISO/IEC 19763-16:2021(E)
5.3.4 Enumerated_Node
Enumerated_Node is a metaclass each instance of which represents a representation of a particular
type of node within a schema, a restricted node for which there is a set of permitted values specified for
the restricted node.
Superclass
Restricted_Node
Attribute DataType Multiplicity Description
[None]
Reference Class Multiplicity Description Inverse Precedence
node_ Node_ 2.* The set of valid enumerated_ Yes
enumeration Enumeration values for this node. node
Constraints
[None]
5.3.5 Namespace
Namespace is a metaclass defined in ISO/IEC 11179-3:2013, 7.2.2.3. It is shown here to indicate the
additional reference required for this document.
Superclass
[None]
Attribute DataType Multiplicity Description
[None}
Reference Class Multiplicity Description Inverse Precedence
used_namespace Document_Schema_ 0.* The set of cited_namespace Yes
Namespace document
schema
namespace
within which
this
namespace is
the cited
namespace.
Constraints
[None]
5.3.6 Node
Node is a metaclass each instance of which represents a representation of a particular node within a
schema. Node has one subclass; Enumerated_Node.
Superclass
Model_Element (which shall be in accordance with ISO/IEC 19763-10:2014, 7.3)
Attribute DataType Multiplicity Description
name String 0.1 A statement specifying the name for this node.
type String 0.1 A statement specifying the type of this node. Examples are
“simple”, “complex”, “group”, “sequence”, “choice”, “element”
and “attribute”.
8 PROOF/ÉPREUVE © ISO/IEC 2021 – All rights reserved
---------------------- Page: 13 ----------------------
ISO/IEC 19763-16:2021(E)
namespace String 0.1 A statement specifying the namespace to be used for this node.
This shall only exist if the namespace for the node differs
from the namespace specified as the default namespace for
the document schema of which this node is a component part
or if there is no default specified for the document schema.
datatype String 0.1 A statement specifying the datatype for this node.
minimum_ String 0.1 A statement of the minimum number of occurrences of
occurrences values of this node. In most circumstances this will be “0”
(indicating that the note is optional) or “1” (indicating that
the node is mandatory).
maximum_ String 0.1 A statement of the maximum number of occurrences of
occurrences values of this node. In most circumstances this will be “1”
or “unbounded”.
Reference Class Multiplicity Description Inverse Precedence
containing_ Document_ 1.1 The schema that node_model_ No
schema Schema contains this node. element
object_reuse Schema_ 0.* The set of schema recipient_ Yes
Reuse reuses that record that node
this node reuses a
schema (the reused
schema).
inferior_ Node_ 0.* The set of node parent_node Yes
relationship Relationship relationships through
which this
node is the parent of
other nodes.
superior_ Node_ 0.* The set of node child_node Yes
relationship Relationship relationships through
which this node is the
child of other nodes.
Constraints
[None]
5.3.7 Node_Enumeration
Node_Enumeration is a metaclass each instance of which represents a representation of a particular
permitted value for an enumerated node.
Superclass
Model_Element (which shall be in accordance with ISO/IEC 19763-10:2014, 7.3)
Attribute DataType Multiplicity Description
value String 1.1 A specification of the actual permitted value.
annotation String 0.1 A statement describing the meaning of the value.
Reference Class Multiplicity Description Inverse Precedence
enumerated_ Enumerated_ 1.1 The enumerated node_ No
node Node node for which this enumeration
value is a permitted
value.
Constraints
[None]
© ISO/IEC 2021 – All rights reserved PROOF/ÉPREUVE 9
---------------------- Page: 14 ----------------------
ISO/IEC 19763-16:2021(E)
5.3.8 Node_Relationship
Node_Relationship is a metaclass each instance of which represents a representation of a particular
relationship between two nodes.
Superclass
Model_Element (which shall be in accordance with ISO/IEC 19763-10:2014, 7.3)
Attribute DataType Multiplicity Description
[None]
Reference Class Multiplicity Description Inverse Precedence
node_ Node_ 1.1 The categorisation of this categorised_ No
relationship_ Relationship_ node relationship. node_
categorisation Type relationship
parent_node Node 1.1 The referenced node that inferior_ No
is the parent node in this relationship
node
relationship.
child_node Node 1.* The set of referenced superior_ No
nodes, each element of relationship
which is a child node in
this node relationship.
Constraints
[None]
5.3.9 Node_Relationship_Type
Node_Relationship_Type is a metaclass each instance of which represents a representation of a
particular categorisation of a set of nodes relationships.
Superclass
Model_Element (which shall be in accordance with ISO/IEC 19763-10:2014, 7.3)
Attribute DataType Multiplicity Description
designation String 1.1 A statement specifying the category of the associated node
relationships.
description String 0.1 A statement explaining the meaning of the designation
statement for this node relationship type.
Reference Class Multiplicity Description Inverse Precedence
categorised_ Node_ 0.* The set of node re- node_ Yes
node_ Relationship lationships that are relationship_
relationship categorised by this categorisation
node relationship
type.
Constraints
[None]
10 PROOF/ÉPREUVE © ISO/IEC 2021 – All rights reserved
---------------------- Page: 15 ----------------------
ISO/IEC 19763-16:2021(E)
5.3.10 Restricted_Node
Restricted_Node is a metaclass each instance of which represents a representation of a particular type
of node within a schema, a node for which there is a restriction. Such as a pattern, placed upon the
values of the node.
Superclass
Node
Attribute DataType Multiplicity Description
restriction_base String 0.1 A statement specifying the datatype within which each of
the values of the node is to be specified.
restriction_ String 0.1 A statement specifying any pattern that is to be applied to
pattern the values specified for the node.
Reference Class Multiplicity Description Inverse Precedence
[None]
Constraints
[None]
5.3.11 Schema_Reuse
Schema_Reuse is a metaclass each instance of which represents a representation of a particular schema
reuse within another schema or of a particular schema reuse as a node within a schema.
Superclass
Model_Element (which shall be in accordance with ISO/IEC 19763-10:2014, 7.3)
Attribute DataType Multiplicity Description
associated_ String 0.1 A statement of any namespace associated with the reused
namespace schema.
Reference Cla
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.