[GNUnet-SVN] [taler-marketing] branch master updated: rfc references, formatting and ABNF syntax fixes

[gnunet]

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

dold pushed a commit to branch master
in repository marketing.

The following commit(s) were added to refs/heads/master by this push:
     new 580e039  rfc references, formatting and ABNF syntax fixes
580e039 is described below

commit 580e0395a27a81b44fbe6c9888e134b00017c96e
Author: Florian Dold <address@hidden>
AuthorDate: Wed Feb 15 15:12:55 2017 +0100

    rfc references, formatting and ABNF syntax fixes
---
 standards/draft-dold-payto.xml | 132 ++++++++++++++++++++++++++++++++++-------
 1 file changed, 110 insertions(+), 22 deletions(-)

diff --git a/standards/draft-dold-payto.xml b/standards/draft-dold-payto.xml
index abe912f..4c3f909 100644
--- a/standards/draft-dold-payto.xml
+++ b/standards/draft-dold-payto.xml
@@ -1,7 +1,6 @@
 <?xml version="1.0" encoding="US-ASCII"?>
 <!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
 <!ENTITY RFC3986 SYSTEM 
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.3986.xml";>
-<!ENTITY I-D.narten-iana-considerations-rfc2434bis SYSTEM 
"http://xml.resource.org/public/rfc/bibxml3/reference.I-D.narten-iana-considerations-rfc2434bis.xml";>
 ]>
 <?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
 
@@ -84,21 +83,25 @@ Questions:
 
 <section anchor="introduction" title="Introduction">
 <t>
-  This document defines the 'payto' Uniform Resource Identifier (URI) scheme
+  This document defines the 'payto' Uniform Resource Identifier (URI) <xref 
target="RFC3986" /> scheme
   for specifying payments.  In its simplest form, a 'payto' URL
-  identifies a payment method.  Additional parameters
-  for a payment, such as an account, an amount or a payment reference, can be 
provided.
+  identifies a payment method and optionally an account identifier.  
Additional parameters
+  for a payment, such as an amount or a payment reference, can be provided.
 </t>
 </section>
 
 <section anchor="syntax"
   title="Syntax of a 'payto' URL">
+  <t>
+  This document uses the Augmented Backus-Naur Form (ABNF) of <xref 
target="RFC5234"/>.
+  </t>
   <figure>
-  <artwork><![CDATA[
+  <artwork type="abnf"><![CDATA[
   payto-URI = "payto" "://" authority path-abempty [ "?" opts ]
-  opts = opt *( "&amp;" opt)
+  opts = opt *( "&amp;" opt )
   opt = (generic-opt / authority-specific-opt) "=" *( pchar )
-  generic-opt = "amount" / "recipient-name" / "sender-name" / "message" / 
"instruction"
+  generic-opt = "amount" / "recipient-name" / "sender-name" /
+                "message" / "instruction"
   authority = <authority, see [RFC3986], Section 3.2>
   path-abempty = <path-abempty, see [RFC3986], Section 3.3>
   pchar = <pchar, see [RFC3986], Appendix A.>
@@ -123,50 +126,57 @@ Questions:
 <section anchor="examples" title="Examples">
 <figure>
   <artwork><![CDATA[
-    payto://sepa/CH9300762011623852957?amount=EUR:200.0&message=hello%20world
+  payto://sepa/CH9300762011623852957?amount=EUR:200.0&message=hello
 
-    INVALID (authority missing):  payto:sepa/12345
+  INVALID (authority missing):  payto:sepa/12345
 ]]>
+  </artwork>
+</figure>
 
 </section>
 
 <section anchor="payment-methods" title="Payment Methods">
 
-<t>
-  sepa: Single European Payment Area. The path is an IBAN, as defined by [REF].
-
-  upi: Unified Payment Interface. The path is an account alias, as defined by 
[REF].
-
-  bitcoin: Bitcoin protocol. The path is a bitcoinaddress, as defined by [REF].
-
-  ach: FIXME.
-</t>
+<t>sepa: Single European Payment Area. The path is an IBAN, as defined by 
<xref target="ISO20022" />.</t>
+<t>upi: Unified Payment Interface. The path is an account alias, as defined by 
<xref target="UPILinking" />.</t>
+<t>bitcoin: Bitcoin protocol. The path is a bitcoinaddress, as defined by 
<xref target="BIP0021" />.</t>
+<t>ach: Automated Clearing House.  The path is a bank account number, as 
defined by <xref target="NACHA" /></t>
 
 </section>
 
 <section anchor="generic-options" title="Generic Options">
 <t>
   The following options SHOULD be understood by every payment method.
+</t>
+<t>
 
   amount:  The amount to transfer, including currency information if 
applicable. The format MUST be:
 <figure>
   <artwork><![CDATA[
-  amount = ?(currency ":") unit ?("." fraction)
-  currency = *[A-Z]
-  unit = +[0-9,]
-  fraction = +[0-9,]
+  amount = [ currency ":" ] unit [ "." fraction ]
+  currency = 1*ALPHA
+  unit = 1*(DIGIT / ",")
+  fraction = 1*(DIGIT / ",")
  ]]>
   </artwork>
 </figure>
   The fraction MUST be smaller than 10^8.  The unit value MUST be smaller than 
2^53.  The use of commas
   is optional for readability and they MUST be ignored.
+</t>
 
+<t>
   recepient-name:  Name of the recipient of the payment.
+</t>
 
+<t>
   sender-name:  Name of the sender of the payment.
+</t>
 
+<t>
   message:  A short message to identify the purpose of the payment, which MAY 
be subject to lossy conversions (for example, due to character set encoding 
limitations).
+</t>
 
+<t>
   instruction:  A short message giving instructions to the recipient, which 
MUST NOT be subject to lossy conversions.  Character set limitations allowed 
for instructions depend on the payment method.
 </t>
 </section>
@@ -180,6 +190,7 @@ Questions:
   into allowable character using either an encoding or a replacement table.
   This conversion process is typically not lossless.
 </t>
+</section>
 
 
 <!-- section anchor="checksums" title="Checksums">
@@ -197,10 +208,87 @@ Questions:
 
     &RFC3986;
 
+    <reference anchor="ISO20022">
+      <front>
+        <title>ISO 20022 Financial Services - Universal financial industry 
message scheme</title>
+        <author>
+          <organization>International Organization for 
Standardization</organization>
+          <address>
+            <uri>http://www.iso.ch</uri>
+          </address>
+        </author>
+        <date month="May" year="2013"/>
+      </front>
+    </reference>
+
+    <reference anchor="NACHA">
+      <front>
+        <title>NACHA Operating Rules &amp; Guidelines</title>
+        <author>
+          <organization>NACHA</organization>
+          <address>
+            <uri>https://www.nacha.org/</uri>
+          </address>
+        </author>
+        <date month="January" year="2017"/>
+      </front>
+    </reference>
+
+  <reference anchor="RFC5234">
+    <front>
+      <title abbrev="ABNF for Syntax Specifications">Augmented BNF for Syntax 
Specifications: ABNF</title>
+      <author initials="D." surname="Crocker" fullname="Dave Crocker" 
role="editor">
+        <organization>Brandenburg InternetWorking</organization>
+        <address>
+          <email>address@hidden</email>
+        </address>
+      </author>
+      <author initials="P." surname="Overell" fullname="Paul Overell">
+        <organization>THUS plc.</organization>
+        <address>
+          <email>address@hidden</email>
+        </address>
+      </author>
+      <date month="January" year="2008"/>
+    </front>
+    <seriesInfo name="STD" value="68"/>
+    <seriesInfo name="RFC" value="5234"/>
+  </reference>
+
+
+  </references>
+
+  <references title="Informational References">
+
+   <reference anchor="BIP0021" target="https://en.bitcoin.it/wiki/BIP_0021";>
+     <front>
+         <title>Bitcoin Improvement Proposal 21</title>
+         <author initials="N." surname="Schneider"
+                 fullname="Nils Schneider">
+         </author>
+         <author initials="M." surname="Corallo"
+                 fullname="Matt Corallo">
+         </author>
+
+         <date month="January" year="2012" />
+     </front>
+  </reference>
+
+  <reference anchor="UPILinking" 
target="http://www.npci.org.in/documents/UPILinkingSpecificationsVersion10draft.pdf";>
+    <front>
+      <title>Unified Payment Interface - Common URL Specifications For Deep
+      Linking And Proximity Integration</title>
+      <author><organization>National Payment Corporation of 
India</organization>
+      </author>
+      <date month="May" year="2016" />
+    </front>
+  </reference>
+
   </references>
 
   <!-- Change Log
 
+v01 2017-02-15  CG   References and formatting
 v01 2017-02-13  CG   Minimal clarifications
 v00 2017-01-17  FD   Initial version
   -->

-- 
To stop receiving notification emails like this one, please contact
address@hidden