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: Nick S <notifications@github.com>
Date: Mon, 25 Jan 2016 20:06:08 -0800
To: w3c/webpayments <webpayments@noreply.github.com>
Message-ID: <w3c/webpayments/issues/63/174807612@github.com>
> It fits the dictionary definition of a credential, so I don't quite see why you think it's overreaching.

Because that definition of 'credential' is so vague as to encompass everything. If you say a credential is a "set of claims about an entity" then it follows that any property of an object is inherently a credential. For example, take a Java interface. An object can claim to implement an interface, making the interface a credential of the object. It's credentials all the way down.

This whole proposal seems to be built around the assumption that a shipping address is *always* a credential, but I don't think that assumption has been proven. Because of that, the proposal seems premature.

Reply to this email directly or view it on GitHub:
Received on Tuesday, 26 January 2016 04:06:44 UTC

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