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


Achieving broader interoperability is desirable, but is not free. 

In your view, what is the degree of support by "regular Web developers" for JSON-LD in
Web applications?

Here is a my proposal:

 * Payment request data is JSON.
 * The API should not prevent parties that reach "private agreements" to use JSON-LD from doing so.
 * We continue to look for interoperability opportunities beyond the scope of this WG. It may be that
   parties are tired of reaching private agreement and want additional standards. For example, we
   have in our charter an optional deliverable to reach additional interoperability for data sent to
   credit networks. Let's work on that and then continue to pursue interoperability at other points
   in the flow.
 * If in the future we find that different parties agree to use JSON-LD specifically, then when those
   parties use the Web Payments API, they will no longer be using proprietary formats, they will
   be using open (JSON-LD-based) standards over the same Web API rails -- which don't themselves
   need to change to allow JSON-LD to flow over them.


Reply to this email directly or view it on GitHub:

Received on Tuesday, 2 February 2016 19:20:40 UTC