[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GNUnet-SVN] [taler-marketing] 02/03: payto: clarify dereferencing with
From: |
gnunet |
Subject: |
[GNUnet-SVN] [taler-marketing] 02/03: payto: clarify dereferencing with unregistered type |
Date: |
Wed, 17 Apr 2019 16:46:02 +0200 |
This is an automated email from the git hooks/post-receive script.
dold pushed a commit to branch master
in repository marketing.
commit d8954bf7ff09fda64b1f156483037689db958091
Author: Florian Dold <address@hidden>
AuthorDate: Wed Apr 17 16:45:01 2019 +0200
payto: clarify dereferencing with unregistered type
---
standards/draft-dold-payto.xml | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/standards/draft-dold-payto.xml b/standards/draft-dold-payto.xml
index 6f3727b..b121f26 100644
--- a/standards/draft-dold-payto.xml
+++ b/standards/draft-dold-payto.xml
@@ -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.
--
To stop receiving notification emails like this one, please contact
address@hidden