commit 00609057f29f4335f3028e057c1425a4ef003db7 parent 815797e6b88ad8f8aec3e5298b26e3f0e0846cec Author: MS <ms@taler.net> Date: Thu, 22 Sep 2022 11:13:30 +0200 rewording ISO20022 critique Diffstat:
| M | libeufin/iso20022.rst | | | 11 | ++++++----- |
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/libeufin/iso20022.rst b/libeufin/iso20022.rst @@ -24,13 +24,14 @@ The specifics of this mapping are: of message elements in the same schema. -Why does LibEuFin not use ISO 20022? -==================================== +How does LibEuFin leverage ISO 20022? +===================================== -While LibEuFin can ingest ISO 20022 messages (camt.05x, pain.002) and generate -them (pain.001), it does not use ISO 20022 in its API and internal data model. +While LibEuFin can communicate ISO 20022 messages (camt.05x, pain.001) to +other parties, it does **not** model its own authored API and internal data +after the ISO 20022 standard. -Reasons for not using ISO 20022 directly are: +Objections to ISO20022: 1. Impedance mismatch. ISO 20022 messages do not map well to query/response APIs.