[GNUnet-SVN] [taler-marketing] branch master updated (b569455 -> 8699ddc)

[gnunet]

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

dold pushed a change to branch master
in repository marketing.

    from b569455  payto: expert review: require general completeness
     new d4fac82  payto: debitor->debtor, prefer sender/receiver
     new d8954bf  payto: clarify dereferencing with unregistered type
     new 8699ddc  metadata

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:
 standards/draft-dold-payto.xml | 21 ++++++++++++---------
 1 file changed, 12 insertions(+), 9 deletions(-)

diff --git a/standards/draft-dold-payto.xml b/standards/draft-dold-payto.xml
index 4777c64..74f9cef 100644
--- a/standards/draft-dold-payto.xml
+++ b/standards/draft-dold-payto.xml
@@ -13,7 +13,7 @@
 <?rfc subcompact="no" ?>
 
 <rfc category="info"
-     docName="draft-dold-payto-05"
+     docName="draft-dold-payto-06"
      ipr="trust200902">
 
   <front>
@@ -48,7 +48,7 @@
       </address>
     </author>
 
-    <date day="24" month="March" year="2019" />
+    <date day="17" month="April" year="2019" />
 
     <!-- Meta-data Declarations -->
     <area>General</area>
@@ -97,7 +97,7 @@
   payto-URI = "payto" "://" authority path-abempty [ "?" opts ]
   opts = opt *( "&" opt )
   opt = (generic-opt / authority-specific-opt) "=" *( pchar )
-  generic-opt = "amount" / "creditor-name" / "debitor-name" /
+  generic-opt = "amount" / "receiver-name" / "sender-name" /
                 "message" / "instruction"
   authority = ALPHA *( ALPHA / DIGIT / "-" / "." )
   path-abempty = <path-abempty, see [RFC3986], Section 3.3>
@@ -110,7 +110,7 @@
 <section anchor="semantics" title="Semantics">
 <t>
   The authority component of a payment URI identifies the payment target type. 
 The
-  payment target types are defined in the Payto Payment Target Type Registry, 
see <xref
+  payment target types are defined in the "Payment Target Types" registry, see 
<xref
   target="payto-registry" />.
 
   The path component of the URI identifies the target for a payment as 
interpreted
@@ -126,6 +126,9 @@
   This allows users with multiple bank accounts (each accessed the respective 
bank's
   banking application) to choose which account to pay with.
 
+  An application SHOULD allow dereferencing a payto URI even
+  if the payment target type of that URI is not registered in the "Payment 
Target Types" registry.
+
   Details of the payment MUST be taken
   from the path and options given in the URI.  The user SHOULD be allowed to
   modify these details before confirming a payment.
@@ -171,11 +174,11 @@ The use of commas is optional for readability and they 
MUST be ignored.
 </t>
 
 <t>
-  creditor-name:  Name of the entity that is credited (receives the payment).
+  receiver-name:  Name of the entity that receives the payment (creditor).
 </t>
 
 <t>
-  debitor-name:  Name of the entity that is debited (makes the payment).
+  sender-name:  Name of the entity that makes the payment (debtor).
 </t>
 
 <t>
@@ -283,7 +286,7 @@ The expert's review SHOULD consider the following criteria:
   <t>The specification of the new payment target type remains within the scope 
of payment transfer form data.
     In particular specifying complete invoices is not in scope.  Neither are 
processing instructions to the
     payment processor or bank beyond a simple payment.</t>
-  <t>The payment target and the options do not contain the debitor's account 
details.</t>
+  <t>The payment target and the options do not contain the payment sender's 
account details.</t>
 </list>
 </t>
 
@@ -336,9 +339,9 @@ The expert's review SHOULD consider the following criteria:
 <t>
 <list style="symbols">
 <t>Name: upi</t>
-<t>Description: Unified Payment Interface. The path is an account alias.  The 
amount and creditor-name
+<t>Description: Unified Payment Interface. The path is an account alias.  The 
amount and receiver-name
 options are mandatory for this payment target.</t>
-<t>Example: payto://upi/address@hidden&amp;amount=INR:200</t>
+<t>Example: payto://upi/address@hidden&amp;amount=INR:200</t>
 <t>Contact: N/A</t>
 <t>References: <xref target="UPILinking" /></t>
 </list>

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