- From: Anders Rundgren <anders.rundgren.net@gmail.com>
- Date: Thu, 30 Oct 2014 05:17:30 +0100
- To: Joerg.Heuer@telekom.de
- CC: public-webpayments@w3.org
On 2014-10-29 23:53, Joerg.Heuer@telekom.de wrote: > Hello guys, > > Good discussion - and you are right with what you are saying about the connection to the browser. (I'm going to talk to the Mozilla guys in a few days...) Hi Jörg, A related and IMO even more interesting discussion can be found here: http://lists.w3.org/Archives/Public/public-web-security/2014Oct/0056.html Cheers, Anders > > Basically we were able to find solutions to connect on several browsers, but it required a different solution for every browser on every OS. > > In the IG discussion we have decided ( and that was my intention anyway) to not specify a wallet for standardization's sake, but use it as a 'straw man' wrt/ certain functionality. In the Payment CG case we are looking at the Payment aspect of it - calling it 'Payment User Agent'. > > The connection to the browsers (and their respective makers) should probably best be made upon this topic as it doesn't cut into these company's business. Effectively, however, I can only second what Dave has been saying - if such functionality as payment (or identity, being my ultimate goal, as Anders might have expected) is implemented in the browser we will see silos by browser type/ maker. > > I hope we can help to avoid this... > > Cheers, > > Jörg > > > DEUTSCHE TELEKOM AG > T-Labs (Research & Innovation) > Dipl.-Inform. Jörg Heuer > Research&Innovation Director Payment&Transactions, Innovation Policy > Winterfeldtstr. 21, 10781 Berlin > +49 (30) 8353-58422 (Tel) > +49 (170) 576 26 12 (Mob) > +49 (3915) 80243910 (Fax) > E-Mail: joerg.heuer@telekom.de > www.telekom.com > > LIFE IS FOR SHARING. > > DEUTSCHE TELEKOM AG > Supervisory Board: Prof. Dr. Ulrich Lehner (Chairman) > Board of Management: Timotheus Höttges (Chairman), > Reinhard Clemens, Niek Jan van Damme, Thomas Dannenfeldt, > Dr. Thomas Kremer, Claudia Nemat, Prof. Dr. Marion Schick > Commercial register: Amtsgericht Bonn HRB 6794 > Registered office: Bonn > > BIG CHANGES START SMALL – CONSERVE RESOURCES BY NOT PRINTING EVERY E-MAIL. > > > > -----Original Message----- > From: Anders Rundgren [mailto:anders.rundgren.net@gmail.com] > Sent: Mittwoch, 29. Oktober 2014 02:54 > To: Joseph Potvin > Cc: Web Payments CG > Subject: Re: Doubt about Wallet as W3C Standard > > On 2014-10-29 10:51, Joseph Potvin wrote: >> RE: "What we should be standardising is an interface or API spec right? I believe that is the general consensus" >> RE: "That is a bit of a stretch given that none of the browser-vendors have expressed any sentiment for this work yet." >> >> Consensus amongst the participants in the CG, is what this refers to. > > Yes, and that's not enough particularly if the interface has ties in the browser/UA. > > Anders > >> >> Joseph >> >> >> On Wed, Oct 29, 2014 at 5:26 AM, Anders Rundgren <anders.rundgren.net@gmail.com <mailto:anders.rundgren.net@gmail.com>> wrote: >> >> On 2014-10-29 09:29, Adrian Hope-Bailie wrote: >> >> I agree. >> >> What we should be standardising is an interface or API spec >> right? I believe that is the general consensus >> >> >> That is a bit of a stretch given that none of the browser-vendors have expressed any sentiment for this work yet. >> >> Any wallet, payment providing application, internet banking >> service etc that >> >> > wishes to be usable as a source of payments would implement the API spec. >> >> This is based on assumptions about what a wallet actually do. >> I don't know where the line goes between payment systems and wallets, maybe the WebPayment CG has a definition somewhere? >> >> I hate to say this all the time, but the [related] federation part is still anything but resolved. >> It is essentially only a suggestion by Manu. What do Google think about this solution? >> >> Anders >> >> >> On 28 October 2014 21:45, Joseph Potvin <jpotvin@opman.ca <mailto:jpotvin@opman.ca> <mailto:jpotvin@opman.ca <mailto: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 <mailto:dsr@w3.org> <mailto:dsr@w3.org <mailto: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 <mailto:dsr@w3.org> >> <mailto:dsr@w3.org <mailto:dsr@w3.org>>> >> http://www.w3.org/People/____Raggett >> <http://www.w3.org/People/__Raggett> >> <http://www.w3.org/People/__Raggett >> <http://www.w3.org/People/Raggett>> >> >> >> >> >> >> -- >> Joseph Potvin >> Operations Manager | Gestionnaire des opérations >> The Opman Company | La compagnie Opman >> jpotvin@opman.ca <mailto:jpotvin@opman.ca> <mailto:jpotvin@opman.ca <mailto:jpotvin@opman.ca>> >> Mobile: 819-593-5983 <tel:819-593-5983> <tel:819-593-5983 >> <tel:819-593-5983>> >> >> >> >> >> >> >> -- >> Joseph Potvin >> Operations Manager | Gestionnaire des opérations The Opman Company | >> La compagnie Opman jpotvin@opman.ca <mailto:jpotvin@opman.ca> >> Mobile: 819-593-5983 > >
Received on Thursday, 30 October 2014 04:18:19 UTC