W3C home > Mailing lists > Public > public-payments-wg@w3.org > January 2016

Re: [webpayments] PROPOSAL: The Web Payments browser API should not support the collection of shipping information through API calls (#63)

From: bifurcation <notifications@github.com>
Date: Fri, 22 Jan 2016 11:32:02 -0800
To: w3c/webpayments <webpayments@noreply.github.com>
Message-ID: <w3c/webpayments/issues/63/174020350@github.com>
> The FIDO submission, for instance, is starting to explore areas beyond the boundaries of the spec we're working on in WebAppSec, and I do expect to see more of those kinds of concrete proposals in the future.

Nonetheless, these proposals are still dealing with authentication, so they're still very distinct from what the CG has been talking about.

> If this group agrees that the best way to make shipping addresses available is via the `navigator.credentials` API, I'd suggest putting together a concrete proposal, and pitching it to developers and implementers. I'd certainly be interested in reading through it.

As would I.  But to be clear, I would very strongly oppose the addition of such work to the WebAppSec charter.

Reply to this email directly or view it on GitHub:
Received on Friday, 22 January 2016 19:32:38 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:13 UTC