RE: need reason description for exclusion of UseCase v1

Initiating function -- just pick a word and define it as such. And ending state -- pick a word for that and define it. Therefore, we have a beginning and end. :)

-- 

David Jackson | Senior Director Financial Services
Mobile: +1.614.560.1237 | VOIP: +1.614.465.6654 
Oracle Industry Solutions Group
New York City | Columbus 

Oracle is committed to developing practices and products that help protect the environment


-----Original Message-----
From: Manu Sporny [mailto:msporny@digitalbazaar.com] 
Sent: Tuesday, June 23, 2015 3:47 PM
To: public-webpayments-ig@w3.org
Subject: Re: need reason description for exclusion of UseCase v1

On 06/23/2015 03:11 PM, Dave Raggett wrote:
> In my talk [1], I was careful to avoid the term wallet given that 
> people differ in what they think it means, and instead referred to the 
> roles for specific tasks, e.g. selection agent, receipt agent and 
> payment instrument.  For V1, we can ignore the receipt agent, and
> just talk about the selection agent and payment instrument.   We can
> leave “wallet” until later, and I expect that when we want to allow 
> one agent to performs multiple roles, then we want indeed want to try 
> to use the term wallet for such agents.

+1, revisiting the "wallet" terminology debate feels like it'll prevent
us from getting more pressing things done.

While the "______ agent" terminology is a bit awkward to use, I have a better idea of what it means than "wallet".

-- manu

--
Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny) Founder/CEO - Digital Bazaar, Inc.
blog: Web Payments: The Architect, the Sage, and the Moral Voice https://manu.sporny.org/2015/payments-collaboration/

Received on Tuesday, 23 June 2015 20:12:12 UTC