marketing

commit a7c5a397e6502a99adc68311632b4667732a3103
parent f71dc42df4465f2758ad226a5c6cc94f6abca77b
Author: Florian Dold <florian.dold@gmail.com>
Date:   Fri, 17 Feb 2017 00:37:10 +0100

minor fixes

Diffstat:
M
standards/uri-request-payto.txt
 | 
6
++++--

1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/standards/uri-request-payto.txt b/standards/uri-request-payto.txt
@@ -24,10 +24,10 @@ ABNF
 
   payto-URI = "payto" "://" method account [ "?" params ]
   params = param *( "&" param )
-  param = (generic-param / authority-specific-param) "=" *pchar
+  param = (generic-param / method-specific-param) "=" *pchar
   generic-param = "amount" / "recipient-name" / "sender-name" /
                "message" / "instruction"
-  authority-specific-param = *pchar
+  method-specific-param = *pchar
   method = <authority, see [RFC3986], Section 3.2>
   account = <path-abempty, see [RFC3986], Section 3.3>
   pchar = <pchar, see [RFC3986], Appendix A.>
@@ -76,6 +76,8 @@ Scheme semantics:
     which MUST NOT be subject to lossy conversions.  Character set
     limitations allowed for instructions depend on the payment method.
 
+  The set of valid method-specific-param are depends on the payment method.
+
 Encoding considerations:
   The payto URI scheme encoding conforms to the encoding rules established
   for URIs in [RFC3986].