[taler-docs] branch master updated (e174e5b -> 37cb140)

[gnunet]

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

ttn pushed a change to branch master
in repository docs.

    from e174e5b  upcase ‘xsd’
     new 8472a40  mark up ‘https://www.iso20022.org/standardsrepository’; add 
period at end of sentence
     new 22904b5  add period at end of sentence (two instances)
     new 37cb140  hopefully uncontroversial style nit: 
s/organisations/organizations/

The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 libeufin/iso20022.rst | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/libeufin/iso20022.rst b/libeufin/iso20022.rst
index d96469d..e45222a 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;
    }
-

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