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

In my mind the question we need to answer is this: Do we have use cases where the data needs to live outside of the APIs we develop? If the answer is "no" then I believe the benefit of using JSON-LD is minimized and the cost of using it (lack of interest from developers that use of JavaScript APIs, and lack of support in browsers for the LD part) is predominant.

Another question I have is this: 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. Would that work? Would it suffice for those who wish to send JSON-LD?


Reply to this email directly or view it on GitHub:

Received on Tuesday, 2 February 2016 15:05:59 UTC