- From: Steven Rowat <steven_rowat@sunshine.net>
- Date: Wed, 21 May 2014 21:38:08 -0700
- To: Web Payments CG <public-webpayments@w3.org>
On 5/18/14 8:21 PM, Manu Sporny wrote: > Below is the refined list, please indicate whether > you approve of the use cases by responding with a "+1 to all use > cases" in your response to the list. If you only want to show your > support for a few of them, +1 each one individually ignoring the > ones that you're ambivalent towards..... > Here's the list: > > Use Case: Store basic identity credentials and payment provider > information on the Web in a way that is easy to share with various > merchants given authorization by the owner of the identity, and > that is easy to synchronize between devices. Notes: This includes > the ability for the identity owner to manage the identity > information. It does not include the ability for the identity owner > to automatically sell their identity information. +1 > Use Case: Transmit one or more pieces of information before a > purchase occurs such that the identification of participants in a > transaction can be performed. +1 > Use Case: Using metadata that is the result of a transaction, > discover attributes associated with the identity of participants in > the transaction. -1, because I believe the word 'attributes' is not sufficiently limiting -- it sounds like you're proposing a universal information-gathering mechanism, for anybody who wants to sniff out some interesting 'attributes' about somebody else. And we know lots of people want to do that, both in government and in commerce. I looked up where this was discussed (the second link you provided), and the wording you had there was "Using metadata that is the result of a transaction, discover the verified identity of participants in the transaction." That sounds better to me, and I'd '+1' that form. But I assume there was some problem with that form, or you would have kept it? > Use Case: Digitally verifiable credentials such that a merchant > and payment processor in a transaction can prove that they have > done due diligence in verifying the customer's identity (KYC). +1 > Use Case: Execute a transaction without revealing secrets (i.e. > identity, passwords, PINs) whose primary purpose is orthogonal to > the actual transaction. +1 > Use Case: Transact with a merchant without revealing any > identifying information. Identifying information is available to > the payment processor. +1 > Use Case: Enable anonymous transactions such that the identity of > the customer is not discoverable by merchants or payment > processors. +1, with the clarification you gave that the legal tracking is still covered where necessary. Steven Rowat
Received on Thursday, 22 May 2014 04:38:32 UTC