diff options
| author | Florian Dold <florian.dold@gmail.com> | 2019-09-27 16:00:28 +0200 |
|---|---|---|
| committer | Florian Dold <florian.dold@gmail.com> | 2019-09-27 16:00:28 +0200 |
| commit | 31273c479076370f60d8c4acc96e5353f511ab04 (patch) | |
| tree | db540c44f3867b4aca5edb0516f54f37c29522c2 | |
| parent | 90161e31c6b8fd06c3d013bf934b2688d0732c83 (diff) | |
| download | marketing-31273c479076370f60d8c4acc96e5353f511ab04.tar.gz marketing-31273c479076370f60d8c4acc96e5353f511ab04.tar.bz2 marketing-31273c479076370f60d8c4acc96e5353f511ab04.zip | |
fix syntax errors and date
| -rw-r--r-- | standards/draft-dold-payto.xml | 12 |
1 files changed, 7 insertions, 5 deletions
diff --git a/standards/draft-dold-payto.xml b/standards/draft-dold-payto.xml index 76fc544..4b30a6f 100644 --- a/standards/draft-dold-payto.xml +++ b/standards/draft-dold-payto.xml @@ -14,7 +14,7 @@ <rfc category="info" docName="draft-dold-payto-08" - ipr="trust200909"> + ipr="trust200902"> <front> <title abbrev="The 'payto' URI scheme"> @@ -48,7 +48,7 @@ </address> </author> - <date day="21" month="July" year="2019" /> + <date day="27" month="September" year="2019" /> <!-- Meta-data Declarations --> <area>General</area> @@ -70,7 +70,7 @@ <t> This document defines the 'payto' Uniform Resource Identifier (URI) <xref target="RFC3986" /> scheme for designating transfer form data for payments. In particular, it always identifies the target of a payment. - A 'payto' URL consists of a payment target type, a target identifier and optional parameters + A 'payto' URI consists of a payment target type, a target identifier and optional parameters such as an amount or a payment reference. </t> <t> @@ -88,7 +88,7 @@ </section> <section anchor="syntax" - title="Syntax of a 'payto' URL"> + title="Syntax of a 'payto' URI"> <t> This document uses the Augmented Backus-Naur Form (ABNF) of <xref target="RFC5234"/>. </t> @@ -222,7 +222,7 @@ a user might not be able to identify the target of a payment. In particular due to homographs <xref target="unicode-tr36" />, a payment target type SHOULD NOT use human-readable names in combination with unicode in the target account specification, as it could give the user the illusion of being able -to identify the target account from the URL. +to identify the target account from the URI. </t> <t> To avoid unnecessary data collection, payment target types SHOULD NOT @@ -233,8 +233,10 @@ essential for an application to conduct a payment. <section anchor="iana" title="IANA Considerations"> +<t> IANA maintains a registry called the "Uniform Resource Identifier (URI) Schemes" registry. +</t> <section anchor="payto-uri" title="URI Scheme Registration"> <t> |