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

> Implementers of the Browser API (browsers) must not have to do any JSON-LD processing.

Ok.

>  It must be possible to interpret messages passed into the Browser API as JSON-LD.

I don't agree with that requirement because that would place an obligation on entities 
who are not party to the API. Instead, I think that the API must not prevent the use of
JSON-LD. (It's not clear to me that the spec needs to be explicit about that point, but
by design it should not prevent the use of JSON-LD.)

>   Implementations must ignore (and pass through) unrecognized message data.

I don't agree with that yet because I don't think we've had enough discussion about error handling.

I do think we should consider an attribute such as "custom" and require the processor to
leave custom data untouched.


---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments/issues/27#issuecomment-178845988