Re: FPWD-ready Web Payments HTTP API and HTTP Messages specs

Sorry, meant to replay-all

Thanks, doc lgtm.

> Based on your comments, I think that there is still a
disconnect on the purpose of this API. We hope to resolve some of that
misalignment at the upcoming face-to-face meeting

Any hints on where we're missing each other?

The ILP CG is keen to put some serious time into exploring micropayments
and this API at TPAC so it would be useful to know ahead of time

On 12 September 2016 at 17:10, Manu Sporny <msporny@digitalbazaar.com>
wrote:

> On 09/12/2016 06:00 AM, Adrian Hope-Bailie wrote:
> > Could the following minor changes be made to make this clearer
>
> Hey Adrian,
>
> Yes, we can and should make most of those changes. We didn't make them
> during the CfC because we didn't want the document changing out from
> underneath folks. Now that the Transition Request is in, we can start
> making modifications again.
>
> Here are the changes that have been made based on your input:
>
> 1. I've merged your PR (and attempted to properly resolve the merge
> conflicts). Based on your comments, I think that there is still a
> disconnect on the purpose of this API. We hope to resolve some of that
> misalignment at the upcoming face-to-face meeting.
>
> 2. I've updated the diagram based on your suggestions. Let us know if
> that works for you:
>
> https://w3c.github.io/webpayments-http-api/
>
> -- manu
>
> --
> Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny)
> Founder/CEO - Digital Bazaar, Inc.
> blog: Advancing the Web Payments HTTP API and Core Messages
> http://manu.sporny.org/2016/yes-to-http-api/
>