- From: Tim Holborn <timothy.holborn@gmail.com>
- Date: Fri, 11 Apr 2014 23:26:21 +1000
- To: Manu Sporny <msporny@digitalbazaar.com>
- Cc: Web Payments CG <public-webpayments@w3.org>
whilst it is outside of scope; perhaps a space somewhere for apps being developed that plan to be web payments compatible / compliant (etc.). in-turn providing a playpen for people to test-out theories and develop using practical works… In any-case; it’s good to hear what collaborators are passionate about, understanding the potential issues of scope-creep if the group focus on these projects as core deliverables, within the scope of the forum. helps define interest areas more specifically, etc. timh. On 12 Apr 2014, at 12:22 am, Manu Sporny <msporny@digitalbazaar.com> wrote: > On 04/11/2014 01:14 AM, Anders Rundgren wrote: >> On 2014-04-11 01:44, Pindar Wong wrote: >>> and 'running code' ;) >> >> ... in browsers supporting some new and for the purpose (payments) >> necessary features. > > No, browser implementation should never be a requirement for the Web > Payments work. We can build a solid Web payment system today without any > browser upgrades. The solutions that this community creates > shouldn't depend on browser manufacturers implementing particular features. > > More on this in a later email, but tying success to the implementation > of particular features in a browser is a losing proposition. That said, > if new security or interaction mechanisms (like TrustedUI, U2F, > WebCrypto) become available natively in the browsers, then the whole > payment ecosystem improves. We shouldn't put browser manufacturers in > the critical path. > > -- manu > > -- > Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny) > Founder/CEO - Digital Bazaar, Inc. > blog: The Worlds First Web Payments Workshop > http://www.w3.org/2013/10/payments/ >
Received on Friday, 11 April 2014 14:29:20 UTC