From 778fcb352163aba8712c30335da15a81b0210d78 Mon Sep 17 00:00:00 2001 From: rvm4 Date: Wed, 6 Apr 2016 17:35:08 -0700 Subject: [PATCH 1/2] grammatical updates to the payment method identifier spec --- specs/method-identifiers.html | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/specs/method-identifiers.html b/specs/method-identifiers.html index 6e43d9a8..7ecc3532 100644 --- a/specs/method-identifiers.html +++ b/specs/method-identifiers.html @@ -58,7 +58,7 @@

The Payment Request API [[!PAYMENTREQUESTAPI]] requires that merchants supply a list - identifiers for supported payment methods. This document defines those identifier + of identifiers for supported payment methods. This document defines those identifier strings and how they are created.

@@ -76,7 +76,7 @@ Web Platform Incubator Community Group.

- +

Introduction

@@ -93,7 +93,7 @@

Requirements for identifiers

There are a set of requirements that the payment method identifiers are designed to support:

  1. It must be possible for the Working Group to mint a payment method identifier for any payment method.
    2. -
  2. It must be possible for the anyone to mint a payment method identifier for a payment method under their control.
    3. +
  3. It must be possible for anyone to mint a payment method identifier for a payment method under their control.
  4. It should be possible to use a standard short string to identify common payment methods.
  5. It must be possible for someone minting a non-standard identifier to make it globally unique in a cost-effective manner.
@@ -104,10 +104,10 @@

Payment Method Identifier

The Payment Method Identifier is a string that uniquely identifies a payment method that a user can use to complete a transaction. For example, Visa, MasterCard, and American Express are payment methods used in some countries.

-
+
This document currently specifies multiple alternate options for payment method identifiers. The Working Group has - not yet selected an approach, which might be one documented in this specification or another as yet undocumented proposal.
+ not yet selected an approach. The chosen approach might be one documented in this specification or another as yet undocumented proposal.

Option 1a

@@ -201,7 +201,7 @@

Discussion topics

  • Developers may find it confusing to us a URL if it isn't intended to point to a resource.
  • Overloading the same string to mean an identifier in some cases and a resource location in others is undesirable. The intent of a URL is to load or locate a resource and may only be done sometimes with this proposal. A URL might mistakenly be crafted as an identifier but later lead to attempts to load it that weren't anticipated (by potentially large numbers of users).
    • -
  • Experience with XML namespaces suggests that optional downloading resources from identifiers tends to encourage +
  • Experience with XML namespaces suggests that optionally downloading resources from identifiers tends to encourage user agents to hard code common identifiers for performance reasons potentially leading to a closed or unbalanced system.
    • @@ -305,7 +305,7 @@

    Dependencies

    This section relies on several other underlying specifications.

    URL
    -
    The terms URL, absolute URL, URL parser, and URL equivalence are defined by [[!url-1-20141209]] (or the editor's draft).
    +
    The terms URL, absolute URL, URL parser, and URL equivalence are defined by [[!url-1-20141209]] (or the editor's draft).
    From 014a6bf668d3cc8dc1f35c8f35359db900a5b096 Mon Sep 17 00:00:00 2001 From: rvm4 Date: Mon, 18 Apr 2016 11:41:49 -0700 Subject: [PATCH 2/2] remove link changes, the decision was to not worry about these links into an implementation option has been selected, at which point the conflicting definitions won't be a problem --- specs/method-identifiers.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/specs/method-identifiers.html b/specs/method-identifiers.html index 7ecc3532..b953763e 100644 --- a/specs/method-identifiers.html +++ b/specs/method-identifiers.html @@ -305,7 +305,7 @@

    Dependencies

    This section relies on several other underlying specifications.

    URL
    -
    The terms URL, absolute URL, URL parser, and URL equivalence are defined by [[!url-1-20141209]] (or the editor's draft).
    +
    The terms URL, absolute URL, URL parser, and URL equivalence are defined by [[!url-1-20141209]] (or the editor's draft).