- From: ianbjacobs <notifications@github.com>
- Date: Thu, 31 Mar 2016 09:03:12 -0700
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
Received on Thursday, 31 March 2016 16:04:14 UTC
@mpsorny, > What's the audience for the text I'm proposing to migrate? People who want to understand how the parts fit together without reading WebIDL. This is the level of information I present, for example to different audiences such as the recent AC meeting. > The text I'm proposing to migrate is tightly bound to the Payment Request API, why does it need to evolve independently? It is rather that it may not have to change even as the API changes. Or, we can augment it to fulfill new communications requirements without having to rev the API document which will be harder to do because if IPR commitments. I don't mind renaming this "Overview" if the word Architecture is a concern to you. Ian --- 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/pull/110#issuecomment-204000709
Received on Thursday, 31 March 2016 16:04:14 UTC