summaryrefslogtreecommitdiff
path: root/libeufin/iso20022.rst
diff options
context:
space:
mode:
Diffstat (limited to 'libeufin/iso20022.rst')
-rw-r--r--libeufin/iso20022.rst9
1 files changed, 4 insertions, 5 deletions
diff --git a/libeufin/iso20022.rst b/libeufin/iso20022.rst
index d96469d0..e45222a5 100644
--- a/libeufin/iso20022.rst
+++ b/libeufin/iso20022.rst
@@ -5,15 +5,15 @@ ISO 20022 is the standard that defines many XML messages for FinTech. It is
very general, and often countries/orgs define subsets (TVS, technical
validation subset) of the schema.
-Documentation for message fields can be viewed at https://www.iso20022.org/standardsrepository
+Documentation for message fields can be viewed at `<https://www.iso20022.org/standardsrepository>`__.
The primary syntax for ISO 20022 messages is XML. To avoid LibEuFin clients
having to deal with XML, we define a mapping from ISO 20022 messages into JSON.
The specifics of this mapping are:
- * The JSON should be "idiomatic" and easy to process
- * When possible, the highly nested structures of ISO 20022 should be flattened
+ * The JSON should be "idiomatic" and easy to process.
+ * When possible, the highly nested structures of ISO 20022 should be flattened.
* It must be possible round-trip between the LibEuFin JSON and ISO 20022
XML messages. The mapping of message types is not 1-to-1, as some ISO 20022 messages are
very similar and can be mapped to the same JSON structure.
@@ -36,7 +36,7 @@ Reasons for not using ISO 20022 directly are:
to JSON, they are difficult to use due to their verbosity.
3. Underspecification. Messages like camt.05x leave many "degrees of freedom"
when translating the underlying data into a message.
-4. No interoperability. As a result of underspecification, different countries/organisations
+4. No interoperability. As a result of underspecification, different countries/organizations
define their own subset and interpretation rules for ISO 20022 messages. This can
lead to even contradictory usage rules. An example for this is how the Swiss and EPC
interpretations handle transaction amounts in the presence of multiple currencies.
@@ -209,4 +209,3 @@ FIXME: This is not complete yet.
proprietaryIssuer?: string;
proprietaryCode?: string;
}
-