ISO/TR 22126-3:2023
(Main)Financial services — Semantic technology — Part 3: Semantic enrichment of the ISO 20022 conceptual model
Financial services — Semantic technology — Part 3: Semantic enrichment of the ISO 20022 conceptual model
This document examines semantic enrichment to support the maintenance of the ISO 20022 conceptual model. It reports on existing and proposed practices to enrich a model: — in a repository, annotating repository concepts with metadata using semantic markup or constraints; — outside a repository, using references to repository concepts, such as the provenance of changes.
Titre manque — Partie 3: Titre manque
General Information
Standards Content (Sample)
TECHNICAL ISO/TR
REPORT 22126-3
First edition
2023-01
Financial services — Semantic
technology —
Part 3:
Semantic enrichment of the ISO 20022
conceptual model
Reference number
ISO/TR 22126-3:2023(E)
© ISO 2023
---------------------- Page: 1 ----------------------
ISO/TR 22126-3:2023(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO 2023
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 2023 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/TR 22126-3:2023(E)
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Semantic markup . 2
4.1 Synonyms . 2
4.2 Multilingual support . 2
4.3 External code sets . 2
5 Constraints . 2
6 Metamodel resource identifiers .3
6.1 Internationalised resource identifiers . 3
6.2 Metamodel as specified . 3
6.3 Metamodel as implemented . 3
7 Model resource identifiers . 3
7.1 Internationalised resource identifiers . 3
7.2 OID (object identifier) . 3
7.3 UUID (universally unique identifier) . 4
7.4 Tool-specific identification schemes . 4
7.5 Repository concept name IRIs . 4
7.6 Language-specific IRIs . 4
7.7 ISO 20022-4 schema references . 5
7.8 Informative IRIs . 5
7.9 Prefixes. 5
8 Tracking provenance and pedigree .6
8.1 Introduction . 6
8.2 The PROV-O model . 6
8.3 ISO 20022 provenance requirements and PROV-O mappings . 6
8.4 Prov-O core components . 6
8.5 ISO 20022 change request process . 7
Annex A (informative) ISO 20022 change request provenance represented in Prov-O .9
Bibliography .12
iii
© ISO 2023 – All rights reserved
---------------------- Page: 3 ----------------------
ISO/TR 22126-3:2023(E)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out
through ISO technical committees. Each member body interested in a subject for which a technical
committee has been established has the right to be represented on that committee. International
organizations, governmental and non-governmental, in liaison with ISO, also take part in the work.
ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of
electrotechnical standardization.
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 ISO documents 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 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).
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 Technical Committee ISO/TC 68, Financial services, Subcommittee SC 9,
Information exchange for financial services.
A list of all parts in the ISO 22126 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.
iv
© ISO 2023 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/TR 22126-3:2023(E)
Introduction
This document contains information on the perceived state of the art of semantic technology as it
pertains to information exchange in financial services. It is informative, not normative.
This document reports on semantic enrichment of the ISO 20022 conceptual model.
The ISO 20022 series defines a scalable, methodical process to ensure consistent descriptions of
messages throughout the financial services industry.
Beyond its primary purpose of providing an operational model of elements, messages and their
associated workflows, there is a further requirement for metadata to add an understanding of the
meaning of their content and context.
The advent of semantic technology enables the enrichment of an ISO 20022 model repository:
— in a repository, annotating repository concepts with metadata using semantic markup or constraints;
— outside a repository, using references to repository concepts.
This is illustrated by demonstrating how the provenance of changes to a model repository can be
[10]
tracked using the W3C PROV-O ontology specification .
In a repository, each concept can be annotated with semantic markup to indicate it is a synonym of
a concept in another model or that it as an external code set. Semantic markup can also be used for
tagging of names and definitions in other languages. Constraints enable the formal specification in
logical languages of relationships between concepts.
Outside a repository, the resource description framework (RDF) can be used to reference repository
concepts with internationalised resource identifiers (IRIs) constructed from object identifiers (OIDs),
universally unique identifiers (UUIDs) or their names with the namespace of the schema, model,
metamodel or registration authority website. This is illustrated with the provenance ontology (Prov-O),
which can be used to track changes to concepts in a repository.
v
© ISO 2023 – All rights reserved
---------------------- Page: 5 ----------------------
TECHNICAL REPORT ISO/TR 22126-3:2023(E)
Financial services — Semantic technology —
Part 3:
Semantic enrichment of the ISO 20022 conceptual model
1 Scope
This document examines semantic enrichment to support the maintenance of the ISO 20022 conceptual
model. It reports on existing and proposed practices to enrich a model:
— in a repository, annotating repository concepts with metadata using semantic markup or constraints;
— outside a repository, using references to repository concepts, such as the provenance of changes.
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 20022-1, Financial services — Universal financial industry message scheme — Part 1: Metamodel
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 20022-1 and the following
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
semantic
related to distinct meaning
Note 1 to entry: As each word can have several meanings, the purpose of semantics is to clarify the exact meaning
of a word in a context to refer to a particular concept.
3.2
provenance
information on the place and time of origin, derivation or generation of a resource or a record or proof
of authenticity or of past ownership
[SOURCE: ISO/IEC 11179-7:2019, 3.1.10]
3.3
pedigree
relationship to an authoritative source
1
© ISO 2023 – All rights reserved
---------------------- Page: 6 ----------------------
ISO/TR 22126-3:2023(E)
4 Semantic markup
4.1 Synonyms
The ISO 20022 metamodel specifies that any repository concept can have semantic markup. Semantic
markup has been used by the Registration Authority to state that a concept is a synonym of another
concept in another model. For the type name "synonym", its element names are "name" and "context".
For example: The messageElement "PriceDetails" is a synonym of value ":90a:" in context "ISO 15022".
4.2 Multilingual support
Semantic markup can be used to provide translated property values on any repository concept.
For the type name "translation", its element names are "language" and the name of other textual
features of the repository concept including and not limited to: name, definition, example, expression,
meaningWhenFalse, meaningWhenTrue, unitCode and messageTypeDescription.
[6]
The value of the language tag is a code conforming with IETF’s Best Current Practice 47. It comprises
[11]
sub-tags from the IANA Language Subtag Registry. This permits extensions for transliteration and
private use.
When the model is represented using RDF, the translations become named properties of the repository
concept whose string value is the named elements value, appended with the language element value.
Constraints on the graph can be used to restrict the occurrence of a string to one per distinct language
tag.
For example: a messageElement with the name "PriceDetails" has semantic markup of type "translation"
for language "zh-Hans" with the name "价格明细", and Latin transliteration of the Mandarin dialect
using pinyin would be represented in Terse Triple Language (TTL, Turtle) as:
[ a iso20022:messageElement ;
iso20022:name "PriceDetails"@en , "价格明细"@zh-Hans , "Jiàgé míngxì"@zh-Latn-pinyin ;
… ]
4.3 External code sets
Semantic markup has been used by the Registration Authority to state that a CodeSet is
validated externally to generated syntax message scheme. For the semantic markup type named
"ExternalCodeSetAttribute", its element "IsExternalCodeSet" has the value "true".
CodeSets and Codes can include provenance information in semantic markup. For the semantic markup
type named "ExternalCodeAttribute", its elements record the Requestor, Status, LastUpDatedDate and
CreationDate.
5 Constraints
The ISO 20022 metamodel specifies that any repository concept can have constraints, which each have
an expression and a language of expression. Expressions written in logical languages can be generated
into artifacts which validate the definition of messages, the sequence of messages and the configuration
of messaging participants.
For example, in order to create a variant message definition that allows only a subset of features of the
original, it is simply a matter of adding constraints to check that only those features are used. This has
the benefit of simply being able to reuse software that supports the original message definition as is,
with undesired features disabled.
Options include, but are not limited to:
— CL: Common Logic, which is a first-order logical language;
2
© ISO 2023 – All rights reserved
---------------------- Page: 7 ----------------------
ISO/TR 22126-3:2023(E)
— OCL: Object Constraint Language, associated with UML;
— SHACL: the SHApes Constraint Language, for validating RDF graphs against a set of conditions;
— XPath: a query language using XML technologies.
6 Metamodel resource identifiers
6.1 Internationalised resource identifiers
IRIs can be used to reference the metamodel, its metaclasses and their properties.
6.2 Metamodel as specified
[8]
The ISO URN namespace can be used to reference the repository and its metaclass specifications.
Fragments naming the property can be appended to each metaclass, as ISO 20022-1 does not specify
the properties as individual document elements.
MetaModel-Specification-IRI ::= "iso:std:iso:20022:-1:ed-2:v1:en"
MetaClass-Specification-IRI ::= MetaModel-Specification-IRI docelement
MetaProperty-Specification-IRI ::= MetaClass-Specification-IRI "#" property-name
EXAMPLE A reference to the 'code' property of B.2.1.5 Metaclass CodeSet can be represented as IRI:
iso:std:iso:20022:-1:ed-2:v1:en:clause:B.2.1.5#code
6.3 Metamodel as implemented
The specified metamodel can be implemented in a variety of ways and can vary from the specification.
The IRI of the met
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.