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

@ianbjacobs,

> What if we defined a JSON format and then somebody send a blob of JSON-LD where the additional data that makes it JSON-LD would be ignored by a conforming processor and be treated as "private data" between the merchant and payment app.

I just wanted to point out that that format *is* JSON-LD. That's exactly what it was designed to do: be usable by developers who don't care about LD and also by developers that do.

There should be a basic message format that is reusable by different APIs. The Google/Microsoft proposal doesn't yet do this. If that message format is JSON-LD we can push innovation to the endpoints, as this is what has always worked for the Web. We don't want to force browsers to interpret LD or do anything with it if they don't want to. Again, that's the point of JSON-LD.

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