Re: [w3c/browser-payment-api] PROPOSAL: A new document structure for this API (#138)

> An visa versa. Is that a problem?

Yes, that's a big problem. :)

> I think that the HTTP API, browser API, payment method and architecture specs should all be rec track and normatively inter-dependent.

We're miscommunicating.

All W3C specs have a set of dependencies, and those dependencies are directed acyclic graphs.

When an implementer sits down to try and implement something, they pick a leaf spec and end up pulling in all of that's leaf spec's MUST language... and it's dependencies MUST language... all the way up the spec chain.

As a spec editor, you try to minimize the amount of MUST language an implementer pulls in (the less MUST language, the easier the implementation and the easier it is to do conformance testing). The less specs the developer has to read, the easier the implementation.

What you're saying sounds like someone implementing a simple HTTP API payment agent/mediator has to pick up all of the specs including the Browser API one to implement.

What I'm proposing is that they shouldn't have to read anything in the Browser API to do so (because they're not implementing any portion of the Browser API).

---
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/138#issuecomment-210152031