Re: Doubt about Wallet as W3C Standard

I agree.

What we should be standardising is an interface or API spec right? I
believe that is the general consensus
Any wallet, payment providing application, internet banking service etc
that wishes to be usable as a source of payments would implement the API
spec.

On 28 October 2014 21:45, Joseph Potvin <jpotvin@opman.ca> wrote:

> I always assumed that the browser would simply interact with any
> spec-compliant digital wallet, and that the owner of the funds has the
> prerogative to decide the whereabouts and characteristics of their digital
> wallet. The browser would just as easily interact with a digital wallet
> that's on the local client device, on a local area network device or
> server, ... , or in "the cloud". In this context, the fund-owner's
> online-banking account is (from the use case point of view) just another
> sort of wallet that a service provide (i.e. a bank) looks after for a fee.
>
> Is the outcome of CG discussion something different than what I have
> summarized here?
>
> Joseph Potvin
>
> On Tue, Oct 28, 2014 at 1:48 PM, Dave Raggett <dsr@w3.org> wrote:
>
>>
>> On 28/10/14 16:40, Mountie Lee wrote:
>>
>>> Hi.
>>>
>>> I have a doubt about payment wallet as w3c standard.
>>>
>>> if wallet is implemented inside of browser,
>>> will it cause the wallet locked into specific browser?
>>>
>>> if user initiated wallet in firefox, is the content of wallet viewable
>>> in chrome?
>>>
>>
>> That's exactly why the wallet should be decoupled from the browser as I
>> proposed in my presentation. We should aim to enable a level playing field
>> and avoid giving control to the browser vendor, device vendor or mobile
>> network operator, etc.
>>
>> --
>> Dave Raggett <dsr@w3.org> http://www.w3.org/People/Raggett
>>
>>
>>
>
>
> --
> Joseph Potvin
> Operations Manager | Gestionnaire des opérations
> The Opman Company | La compagnie Opman
> jpotvin@opman.ca
> Mobile: 819-593-5983
>