W3C home > Mailing lists > Public > public-payments-wg@w3.org > June 2016

Re: [w3c/webpayments] Update conformance (#147)

From: ianbjacobs <notifications@github.com>
Date: Wed, 22 Jun 2016 06:48:35 -0700
To: w3c/webpayments <webpayments@noreply.github.com>
Message-ID: <w3c/webpayments/pull/147/c227748916@github.com>
Hi Adrian,

I have some comments on this PR. 

- " A conforming Payment Request API user agent MUST also be a   <em>conforming implementation</em> of the IDL fragments of this specification, as described in the “Web IDL” specification. [[!WEBIDL]]". (But see below for an alternative.)

Your text suggests an interesting point, but I'm not sure I would write it that way. Here is what I understand:

 * Because this spec builds on payment request API, conformance to this specification also requires conformance to that specification.
 * Conformance to this specification includes conformance to the WebIDL parts.

- "This specification uses both the terms "conforming user agent(s)" and "user agent(s)" to refer to this product class." It seems we should add "browser" to that list because that's the one we use most commonly.

-"In this specification, <a>user agent</a> means a <em>Web browser or other interactive user agent</em> as defined in [[!HTML5]]."  Are you sure you want to constrain the document that way? I'm ok to do so but want to be sure you have that in mind. I know you are thinking that some payment apps might not be interactive, for example. So I want to be sure you also don't have in mind non-interactive user agents.

- "A <dfn data-lt="user agents">user agent</dfn> MUST behave as described in this specification in order to be considered conformant." I suggest instead:
    "A conforming user agent is one that implements all of the "MUST" statements and the WebIDL."

In other words:
 * We don't "consider" something to be conformant. It either fulfills requirements for conformance or it doesn't.
 * The requirements are expressed through MUST statements.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Received on Wednesday, 22 June 2016 13:49:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:17 UTC