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

> The Web Payments CG proposal defines the messages as un-typed objects and asserts that JSON-LD would be used to define the format of these messages.
> The paymentRequest proposal defines the messages using WebIDL in the spec

As long as we're not involving methods -- I see no reason why *both* of these can't be true. You could specify messages in JSON-LD format, limit them to a particular context for the browser API, and define the basic properties that are required for interop via WebIDL. I think we can get the best of both worlds without causing issues in either.

This *sounds* somewhat like what you propose, but I'm not sure if it's the same thing.

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