Search
×
FR

Placeholder headline

This is just a placeholder headline

TEMA 2026 Edition – Online Subscription Only

$

BUY NOW

Placeholder headline

This is just a placeholder headline

API RP 15SIH, 2nd Edition: Installation and Handling of Spoolable Reinforced Plastic Line Pipe

$

158

BUY NOW

Placeholder headline

This is just a placeholder headline

API RP 754, 4th Edition: Process Safety Performance Indicators for the Refining and Petrochemical Industries

$

393

BUY NOW

Placeholder headline

This is just a placeholder headline

ASME B31.1-2020: Power Piping

$

668

BUY NOW

Placeholder headline

This is just a placeholder headline

ASME B31.1-2022: Power Piping

$

668

BUY NOW

ISO 20022-9:2026

ISO 20022-9:2026 Financial services — Universal financial industry message scheme — Part 9: Syntax generation requirements and rules

CDN $251.00

This publication was last reviewed and confirmed in 2026.

Financial services — Universal financial industry message scheme — Part 9: Syntax generation requirements and rules

Description

This document complements the ISO 20022 Metamodel, as specified in ISO 20022-1, with generic requirements and guidelines to define specific syntax generation rules for other encodings in order to produce schemas based on each specific syntax generation rules in compliance with this document. Such specific syntaxes include XML, ASN.1 and JSON. (XML and ASN.1 do not imply ISO 20022-4 XML schema generation and ISO 20022-8 ASN.1 generation only. W3C XML Schema, ASN.1 and JSON can be used to express or define a variety of schema types.)

Under this metamodel-driven and syntax-agnostic approach of ISO 20022 series, interoperability is ensured at the conceptual level of the metamodel specified in ISO 20022-1, rather than at the physical level of syntaxes specified in ISO 20022-4 and ISO 20022-8.

In this document, “schema” refers to the “SyntaxMessageScheme” defined in ISO 20022-1. However, for ease of reading, this document will hereafter refer to it as “schema” which is a general term for design documents that define data structures.

The metaclass “MessageDefinition” that is described in ISO 20022-1:2026, Figure 13 is the target of the transformation specified in this document, but the metaclass “MessageChoreography” is not. In other words, this document is only the rules for the syntax of the data representation language. For example, Application Programming Interface (API) specific aspects are outside the scope of this document.

Regarding the concept of conformance to this document, see Annex B.

Edition

1

Published Date

2026-06-18

Status

PUBLISHED

Pages

25

Language Detail Icon

English

Format Secure Icon

Secure PDF

Abstract

This document complements the ISO 20022 Metamodel, as specified in ISO 20022-1, with generic requirements and guidelines to define specific syntax generation rules for other encodings in order to produce schemas based on each specific syntax generation rules in compliance with this document. Such specific syntaxes include XML, ASN.1 and JSON. (XML and ASN.1 do not imply ISO 20022-4 XML schema generation and ISO 20022-8 ASN.1 generation only. W3C XML Schema, ASN.1 and JSON can be used to express or define a variety of schema types.)

Under this metamodel-driven and syntax-agnostic approach of ISO 20022 series, interoperability is ensured at the conceptual level of the metamodel specified in ISO 20022-1, rather than at the physical level of syntaxes specified in ISO 20022-4 and ISO 20022-8.

In this document, "schema" refers to the "SyntaxMessageScheme" defined in ISO 20022-1. However, for ease of reading, this document will hereafter refer to it as "schema" which is a general term for design documents that define data structures.

The metaclass “MessageDefinition” that is described in ISO 20022-1:2026, Figure 13 is the target of the transformation specified in this document, but the metaclass “MessageChoreography” is not. In other words, this document is only the rules for the syntax of the data representation language. For example, Application Programming Interface (API) specific aspects are outside the scope of this document.

Regarding the concept of conformance to this document, see Annex B.

Previous Editions

Can’t find what you are looking for?

Please contact us at: