gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[taler-docs] branch master updated (b4f3af2 -> 59e74a0)


From: gnunet
Subject: [taler-docs] branch master updated (b4f3af2 -> 59e74a0)
Date: Sat, 28 Nov 2020 02:32:46 +0100

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

ttn pushed a change to branch master
in repository docs.

    from b4f3af2  diction: s/existing (in the system)/\1/
     new ae55e94  delete trailing whitespace
     new 2d6ffd3  add period at end of sentence
     new 59e74a0  upcase ‘ebics’

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/ebics.rst | 20 +++++++++-----------
 1 file changed, 9 insertions(+), 11 deletions(-)

diff --git a/libeufin/ebics.rst b/libeufin/ebics.rst
index 9960fe1..8dc9a61 100644
--- a/libeufin/ebics.rst
+++ b/libeufin/ebics.rst
@@ -58,13 +58,13 @@ EBICS Glossary
 
   FTAM
     Historical predecessor protocol to EBICS (*file transfer, access and 
management*).
-   
+
   HEV
     The *Host EBICS Version*.  Queried by the client with an HEV request 
message.
 
   Human Subscriber
 
-   See :term:`Subscriber`. 
+   See :term:`Subscriber`.
 
   H004
     Host protocol version 4.  Refers to the XML Schema defined in *EBICS 2.5*.
@@ -84,7 +84,7 @@ EBICS Glossary
     The Order Number is used to match VEUs in a second upload to the original 
order.
     An Order Number matches the format ``[A-Z][A-Z0-9]{3}`` (and is not really 
a number!).
 
-    Must be unique per customer ID and per order type
+    Must be unique per customer ID and per order type.
 
   Transaction ID
     A transaction ID is a 128-bit cryptographically strong random number.
@@ -100,7 +100,7 @@ EBICS Glossary
   Partner ID
     In German, this is called "Kunden ID" (= Customer ID).
     One partner can have multiple "participants", which are identified by user 
IDs.
-    
+
     Practical example:  A company has one Partner ID.  Each person at the 
company
     that can access the company's bank accounts gets their own User ID.
     When the person is indirectly accessing the bank server (for example via
@@ -131,7 +131,7 @@ EBICS Glossary
     EBICS implements its own protocol-level segmentation of business-related 
messages.
     The segmentation can be seen as an alternative to the HTTP facilities of 
``Accept-Ranges``.
 
-    The order data of an ebics message may not exceed 1 MB.  The segmentation 
applies both
+    The order data of an EBICS message may not exceed 1 MB.  The segmentation 
applies both
     to requests and responses.
 
   Subscriber
@@ -145,7 +145,7 @@ EBICS Glossary
     and ``UserId``.  A technical subscriber cannot sign a bank-technical 
request.
 
   Technical Subscriber
-   See :term:`Subscriber`. 
+   See :term:`Subscriber`.
 
   TLS
     *Transport Layer Security*.  All messages in EBICS are sent over HTTP with 
TLS.
@@ -219,7 +219,7 @@ Relevant Order Types
     **Before EBICS 3.0, France**.  File Download.  Mainly used by France-style 
EBICS.
 
   HAA
-   Type: Download, Optional 
+   Type: Download, Optional
 
    Download order types for which there is new data available.
 
@@ -229,7 +229,7 @@ Relevant Order Types
    Download information about a subscriber.  From German "Teilnehmerdaten".
 
   HKD
-   Type: Download, Optional 
+   Type: Download, Optional
 
    Download information about a customer (=partner).  From German 
"Kundendaten".
 
@@ -441,7 +441,7 @@ SWIFT will eventually transition from MT messages to 
ISO20022,
 but some banks might still only give us account statements in the old
 SWIFT format.
 
-  
+
 
 Key Management
 ==============
@@ -592,5 +592,3 @@ Others
 
 * `<https://wiki.windata.de/index.php?title=EBICS-Auftragsarten>`_
 * `<https://www.gls-laden.de/media/pdf/f1/c6/f2/nderungsauftrag.pdf>`_
-
-

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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]