- From: Anders Rundgren <anders.rundgren.net@gmail.com>
- Date: Wed, 29 Oct 2014 11:04:02 +0100
- To: Joseph Potvin <jpotvin@opman.ca>
- CC: Web Payments CG <public-webpayments@w3.org>
On 2014-10-29 10:54, Anders Rundgren wrote: > 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. Follow-up: http://lists.w3.org/Archives/Public/public-webcrypto 209 quite difficult message for October 2014 (after three years of work) gives an indication what W3C standardization is about. You need to get buy-in early on. Anders > > 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 Wednesday, 29 October 2014 10:04:45 UTC