Re: [w3c/browser-payment-api] Should payment app registration be included in the conformance criteria of the browser API spec? (#8)

No, the conformance criteria should state what is needed to implement the spec, which is the PaymentRequest API. Conformance criteria for the registration spec should be in the registration spec. The documentation architecture is designed to allow these to be in their own documents proceeding at their own pace to get to Recommendation and lock in associated commitments when they are ready.

> Unless there is a need for user agents to support registration of, at a minimum, web-based payment apps there is a risk that independent payment app publishers become beholden on browser and platform vendors.

In my experience, changing the conformance criteria of a W3C Recommendation has little impact in whether various implementations choose to implement all or part of a set of specifications or in what order different parts might be implemented. I propose we don't spend time on this exercise and instead describe the conformance required to get interop of the content of each spec.


---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/browser-payment-api/issues/8#issuecomment-212538597