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

@ianbjacobs,

I think Manu's comment (https://github.com/w3c/webpayments/issues/27#issuecomment-178752652) should be the way we go about achieving JSON messages (which can really be JSON-LD) in the Browser API without Web developers or API implementers having to think about/do any LD processing at all. It is subtly different from your four points, but achieves the same higher level goals, IMO.

The main difference is that we'd be specifying how (*if desired*) you interpret a message as JSON-LD -- what you do is look for a `@context` and if not present, assume a default one. Otherwise we're saying the same thing: the message for the Browser API is JSON, it can definitely be interpreted as JSON-LD, but no conforming implementation of the API needs to do so.

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