commit 86b86a02b3cbcd683517b44b83ff253361a5051a
parent 6c48e8535da56009c368ba7ed720830a69b60699
Author: Florian Dold <florian.dold@gmail.com>
Date: Wed, 17 Apr 2019 15:24:03 +0200
payto: expert review
Diffstat:
1 file changed, 20 insertions(+), 13 deletions(-)
diff --git a/standards/draft-dold-payto.xml b/standards/draft-dold-payto.xml
@@ -261,22 +261,29 @@ is "Payment Target Types".
<t>Name: The name of the payment target type (case insensitive ASCII string, restricted to alphanumeric characters,
dots and dashes)</t>
<t>Description: A description of the payment target type, including the semantics of the path in the URI if applicable.</t>
-<t>Example: Example URI to illustrate the payment target type.</t>
+<t>Example: At least one example URI to illustrate the payment target type.</t>
<t>Contact: The contact information of a person to contact for further information</t>
-<t>References: Optionally, references describing the payment method (such as an RFC) and method-specific options</t>
+<t>References: Optionally, references describing the payment method (such as an RFC) and method-specific options,
+ or references describing the payment system underlying the payment target type.</t>
</list>
The registration policy for this registry is "expert review", as described in <xref target="RFC5226" />.
-The expert should be appointed by the IETF Indenpendent Stream Editor.
-
-The expert SHOULD check that
-* references clearly describe syntax and semantics of the payment target and optional parameters if applicable
-* appropriateness of the chosen payment target type name and (if applicable) vendor neutrality, specifically
-avoiding conflicts with well-known payment systems and names that have a potential to confuse users
-* compatibility of the payment target type specification with the this specification
-* the specifications of new payment target types remain within the scope of payment transfer form data. In particular
-specifying complete invoices is not in scope. Neither are processing instructions to the bank beyond a simple payment.
-* the optional parameters do not contain information that specifies the debitor's account details
-
+The expert is appointed by the IETF Indenpendent Stream Editor.
+
+The expert's review SHOULD consider the following criteria:
+<list style="numbers">
+ <t>The description clearly defines the syntax and semantics of the payment target and optional parameters if applicable.</t>
+ <t>Relevant references are provided if they are available.</t>
+ <t>The chosen name is appropriate for the payment target type, does not conflict
+ with well-known payment systems, and avoids potential to confuse users.</t>
+ <t>The payment system underlying the payment target type is not fundamentally
+ incompatible with the general options (such as positive decimal amounts) in this specification.</t>
+ <t>The payment target type is not a vendor-specific version of a payment target type that
+ could be described more generally by a vendor-neutral payment target type.</t>
+ <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>
+</list>
</t>
<section anchor="registry-entry-ach" title="ACH Bank Account">
