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 18:14:15 -0800
To: w3c/webpayments <webpayments@noreply.github.com>
Message-ID: <w3c/webpayments/issues/63/174777492@github.com>
To be honest, I am very confused by the notion being put forward that a shipping address is a "credential" in the first place. In the Credential CG group's [own glossary][1] a credential is defined as:

> A set of claims that refer to a qualification, achievement, personal quality, aspect of an identity such as a name, government ID, preferred payment processor, home address, or university degree typically used to indicate suitability.

A shipping address is none of these things. It **may** be a home address, but it equally may be an address a friend gave me and I have no proof that it is or isn't real.

Surely nobody would propose a latitude/longitude coorindate be a "credential"? So why is a shipping address any different? Like a pair of coordinates it represents a physical location. Calling it a credential seems like some serious overreaching.

[1]:http://opencreds.org/specs/source/glossary/

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments/issues/63#issuecomment-174777492
Received on Tuesday, 26 January 2016 02:14:52 UTC

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