[taler-docs] branch master updated: rewording ISO20022 critique

[gnunet]

This is an automated email from the git hooks/post-receive script.

ms pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new 0060905  rewording ISO20022 critique
0060905 is described below

commit 00609057f29f4335f3028e057c1425a4ef003db7
Author: MS <ms@taler.net>
AuthorDate: Thu Sep 22 11:13:30 2022 +0200

    rewording ISO20022 critique
---
 libeufin/iso20022.rst | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/libeufin/iso20022.rst b/libeufin/iso20022.rst
index a4c0bf7..7b1fed8 100644
--- 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.

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.