- From: Anders Rundgren <anders.rundgren.net@gmail.com>
- Date: Mon, 05 May 2014 10:14:04 +0200
- To: Manu Sporny <msporny@digitalbazaar.com>, Web Payments <public-webpayments@w3.org>
On 2014-05-05 03:27, Manu Sporny wrote: > This is a general request to the Web Payments CG. We need help writing > use case descriptions. If one or more of you could write out a simple > user story for the following use case, it would help us immensely: > > 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. > > This use case was approved last week during the telecon[1]. An example > of such a story can be seen at the following link: > > https://web-payments.org/specs/source/use-cases/#proof-of-purchase-and-verifiable-digital-receipts > > Don't try to coordinate if you should be the one to write it or not. > Just write it and send it back to the list. The editors of the use cases > document will pick the best one and integrate it. > > Please fill out the template below by replying to this email. If the > description is good, the text you write will be folded into the Web > Payments use case document[2], which will guide the technical work we'll > be doing over the next few years. > > ---------------------------------------------------------------------------- > > 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. DESCRIPTION (aka User Story) --------------------------- [I leave that to other describing when and why you need this information]] REQUIREMENTS (optional) ----------------------- Information about a user on the web should be made accessible to other parties at the user's discretion. I personally do not see how you can fix that without getting into pretty awkward management schemes that few users would be able to cope with. My only remedy is that you rather "carry" such information and selectively disclose it when requested. I'm aware of the fact that such measures require deep patches in browsers... Anders Rundgren ---------------------------------- > > -- manu > > [1] https://web-payments.org/minutes/2014-04-30/#125 > [2] https://web-payments.org/specs/source/use-cases/ >
Received on Monday, 5 May 2014 08:14:35 UTC