Review ready Core Messages and HTTP API specs

Hi all,

Just a quick update to note that the Core Messages and HTTP API specs
have been aligned a bit more with the latest Web Payments Architecture
Summary document and the Browser API. They are ready to review:

Web Payments Core Messages:
https://w3c.github.io/webpayments-core-messages/

Web Payments HTTP API:
https://w3c.github.io/webpayments-http-api/

If you've done a review in the past two months, not a whole lot has
changed from a conceptual standpoint. We don't have complete alignment
with the Browser API yet for at least the following reasons:

* There is no type inferencing in HTTP messages (like there is in
   Javascript), and so you need to be explicit about the type.
* The key/value pair names don't quite match up with the WebIDL
   in the Browser API due to the possibility of the generic names in
   the Browser API clashing with other payment/object vocabularies
   in JSON-LD (for example).
* The Browser API takes 3 arguments to construct the PaymentRequest
   while the HTTP API uses a single argument due to the
   "strangeness" of passing arrays to HTTP APIs.
* The HTTP API supports digital signatures on the entire payment
   request, we're not quite sure if/how the Browser API is going
   to do this.

The request at the Web Payments WG F2F will be to publish both of these
documents as FPWDs. Please review them before the face to face and be
ready to weigh in on that question.

-- manu

Received on Wednesday, 29 June 2016 02:15:43 UTC