- From: Adrian Hope-Bailie <notifications@github.com>
- Date: Mon, 11 Apr 2016 07:11:16 -0700
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
Received on Monday, 11 April 2016 14:11:45 UTC
> The distinction between these channels would be clearer if you refered to the 'mediator' in the second channel. Separation of concerns between UA and mediator needs to be clear in our thinking even if we conflate the implementations. This is a good point but... 1. The UA and mediator are not different roles. The UA assumes many roles and one of these is that of mediator. 1. This is a UA focused spec so in most cases I'd actually talk about a UA (not a mediator) What this suggests is that we should split out a bunch of the browser API spec into a generic mediator spec that defines the conformance criteria for a mediator. The browser API spec would then reference that document and define the specific behavior of a UA (as mediator) including the API it exposes and state changes etc. --- 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/1#issuecomment-208366798
Received on Monday, 11 April 2016 14:11:45 UTC