Re: [webpayments] How should the message schemas for the payment request and response be defined? (#27)

Can we get agreement on these points?

- Implementers of the Browser API (browsers) must not have to do any JSON-LD processing.
- It must be possible to interpret messages passed into the Browser API as JSON-LD.
- Implementations must ignore (and pass through) unrecognized message data.

If so, I believe the remaining decisions have to do with what guidance the spec provides on how payment apps should interpret messages as JSON-LD. @msporny has proposed a "default context" mechanism. That mechanism makes sense to me, but @ianbjacobs suggested that it would "require something of processors related to JSON-LD". It seems like it shouldn't, so isn't this just a matter of getting the language right?

Reply to this email directly or view it on GitHub:

Received on Tuesday, 2 February 2016 21:39:50 UTC