Web Payments CG specs updated

Hi all,

The Web Payments CG specs have been updated based on input from the W3C
TPAC face-to-face. The specs are in very rough form right now, focusing
on what the messages, API calls, and flows would look like and ignoring
details and specifics around wording. WARNING: There is a fair bit of
hand waving going on wrt. details.

The documents are a loose collection of ideas that have been explored in
the Web Payments CG over the past several years. Once we identify which
general direction the group would like to head in, we'll add more detail
to each idea.

Please review the specs in this order:

http://wicg.github.io/web-payments-browser-api/
http://web-payments.github.io/web-payments-http-api/
http://web-payments.github.io/web-payments-messaging/

If something doesn't make sense, don't assume it's because you are
missing something. There very well could be a big gap/issue or a part in
the processing flow that we haven't connected/solved.

Feel free to look through the specs and raise issues at this point.
We'll use those issues to refine the text that's there. At this point,
just look for architectural faults/flaws, not details or specifics
around grammar/wording.

-- manu

-- 
Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny)
Founder/CEO - Digital Bazaar, Inc.
blog: Web Payments: The Architect, the Sage, and the Moral Voice
https://manu.sporny.org/2015/payments-collaboration/

Received on Monday, 30 November 2015 04:50:25 UTC