[GNUnet-SVN] [taler-marketing] 01/02: put existing payment methods into registry defaults

[gnunet]

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

dold pushed a commit to branch master
in repository marketing.

commit d204157f05bc1d916ce76b2b4bd8b1d6fa582e6e
Author: Florian Dold <address@hidden>
AuthorDate: Sat Apr 7 03:16:18 2018 +0200

    put existing payment methods into registry defaults
---
 standards/draft-dold-payto.xml | 18 ++++++++++++------
 1 file changed, 12 insertions(+), 6 deletions(-)

diff --git a/standards/draft-dold-payto.xml b/standards/draft-dold-payto.xml
index 80553f3..e0e55d3 100644
--- a/standards/draft-dold-payto.xml
+++ b/standards/draft-dold-payto.xml
@@ -134,11 +134,7 @@ Questions:
 
 <section anchor="payment-methods" title="Payment Methods">
 
-<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>
-
+<t>The payment methods are defined in the Payto Payment Method Registry, see 
<xref target="payto-registry" />.</t>
 </section>
 
 <section anchor="generic-options" title="Generic Options">
@@ -220,12 +216,22 @@ is "Payto Payment Method Registry".
 <t>The registry shall record for each entry:
 <list style="symbols">
 <t>Name:  The name of the payment method (case insensitive ASCII string)</t>
-<t>Description: A description of the payment method</t>
+<t>Description: A description of the payment method, including the semantics 
of the path in the URI if applicable.</t>
 <t>Contact: The contact information of a person to contact for further 
information</t>
 <t>References: Optionally, references describing the payment method (such as 
an RFC) and method-specific options</t>
 </list>
 The registration policy for this registry is "First Come First Served", as 
described in <xref target="RFC5226" />.
 </t>
+
+<t>The registry is initially populated with the following entries:</t>
+<texttable>
+<ttcol>Name</ttcol><ttcol>Description</ttcol><ttcol>Contact></ttcol><ttcol>References</ttcol>
+<c>ach</c><c>Automated Clearing House.  The path is a bank account 
number.</c><c>N/A</c><c><xref target="NACHA" /></c>
+<c>sepa</c><c>Single European Payment Area. The path is an 
IBAN.</c><c>N/A</c><c><xref target="ISO20022" /></c>
+<c>upi</c><c>Unified Payment Interface. The path is an account 
alias.</c><c>N/A</c><c><xref target="UPILinking" /></c>
+<c>bitcoin</c><c>Bitcoin protocol. The path is a "bitcoinaddress" as per <xref 
target="BIP0021" />.</c><c>N/A</c><c><xref target="BIP0021" /></c>
+</texttable>
+
 </section>
 
 </section>

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