commit f71dc42df4465f2758ad226a5c6cc94f6abca77b
parent d657e3e3f8ca6e649a057e8c5b84f97f24aaffde
Author: Florian Dold <florian.dold@gmail.com>
Date: Fri, 17 Feb 2017 00:33:14 +0100
syntax problems
Diffstat:
1 file changed, 21 insertions(+), 20 deletions(-)
diff --git a/standards/uri-request-payto.txt b/standards/uri-request-payto.txt
@@ -19,28 +19,29 @@ Scheme syntax:
Additional keys may be allowed or required by the payment method.
ABNF
- Formal syntax is defined using ABNF [RFC5234]. Certain values
- are included by reference from [RFC3986]:
-
- payto-URI = "payto" "://" method account [ "?" params ]
- params = param *( "&" param )
- param = (generic-param / authority-specific-param) "=" *( pchar )
- generic-param = "amount" / "recipient-name" / "sender-name" /
- "message" / "instruction"
- method = <authority, see [RFC3986], Section 3.2>
- account = <path-abempty, see [RFC3986], Section 3.3>
- pchar = <pchar, see [RFC3986], Appendix A.>
- amount = [ currency ":" ] unit [ "." fraction ]
- currency = 1*ALPHA
- unit = 1*(DIGIT / ",")
- fraction = 1*(DIGIT / ",")
+ Formal syntax is defined using ABNF [RFC5234]. Certain values
+ are included by reference from [RFC3986]:
+
+ payto-URI = "payto" "://" method account [ "?" params ]
+ params = param *( "&" param )
+ param = (generic-param / authority-specific-param) "=" *pchar
+ generic-param = "amount" / "recipient-name" / "sender-name" /
+ "message" / "instruction"
+ authority-specific-param = *pchar
+ method = <authority, see [RFC3986], Section 3.2>
+ account = <path-abempty, see [RFC3986], Section 3.3>
+ pchar = <pchar, see [RFC3986], Appendix A.>
+ amount = [ currency ":" ] unit [ "." fraction ]
+ currency = 1*ALPHA
+ unit = 1*(DIGIT / ",")
+ fraction = 1*(DIGIT / ",")
Scheme semantics:
- The authority component of a payment URI identifies the payment
- method. The path component of the URI identifies the target
- account for a payment as interpreted by the respective payment
- method. The query component of the URI can provide additional
- parameters for a payment.
+ The authority component of a payment URI identifies the payment
+ method. The path component of the URI identifies the target
+ account for a payment as interpreted by the respective payment
+ method. The query component of the URI can provide additional
+ parameters for a payment.
The following methods MUST have the following semantics:
