W3C home > Mailing lists > Public > public-webpayments@w3.org > May 2015

RE: Bloomberg recommending Browser Extension Community Group. Vote yes!

From: SULLIVAN, BRYAN L <bs3131@att.com>
Date: Fri, 8 May 2015 15:38:14 +0000
To: "'Anders Rundgren'" <anders.rundgren.net@gmail.com>, "'Erik Anderson'" <eanders@pobox.com>, Web Payments CG <public-webpayments@w3.org>, "public-webpayments-comments@w3.org" <public-webpayments-comments@w3.org>
Message-ID: <59A39E87EA9F964A836299497B686C352107F758@CAFRFD1MSGUSRIA.ITServices.sbc.com>
I saw the other (NFC/BLE native function access-focused as an example) but there is only one supporter so far.
I think these are two very different use cases, but will bring up similar things to be considered (native APIs as accessed through the browser extension, or an explicit native API call mechanism). It might be good to consider both in the same CG, though IMO the browser extension use case seems more feasible.

Thanks,
Bryan Sullivan | AT&T

-----Original Message-----
From: Anders Rundgren [mailto:anders.rundgren.net@gmail.com] 
Sent: Thursday, May 07, 2015 10:44 PM
To: SULLIVAN, BRYAN L; 'Erik Anderson'; Web Payments CG; public-webpayments-comments@w3.org
Subject: Re: Bloomberg recommending Browser Extension Community Group. Vote yes!

On 2015-05-08 07:09, SULLIVAN, BRYAN L wrote:
> Sounds like a great idea.
> I added our support and it looks like this put it over the fence.

As I as have been jumping up and down regarding this topic for months, I'm of course very interested.  I don't think the CG description really tells the entire story because there are two fundamentally different browser extensions:

- HTML5/JS-based extensions which may have additional APIs which if used typically require certification

- Extensions that (in some way) "hook" into the native layer

Google and Mozilla have created (completely different) mixtures of HTML5/JS extensions with native support which I consider unfortunate; The Google solution requires a sys-admin-like install of native code + an "AppStore" for the HTML5/JS extension.

Although there's a huge (documented) interest [1,2] for a standardized extension for accessing the native layer, it seems that this is outside of W3C's "jurisdiction".

Now there are two extension proposed browser CGs:
https://lists.w3.org/Archives/Public/public-web-security/2015Apr/0012.html

Mr. Rybka is free to contact me any day!

Cheers,
Anders

1] http://blog.chromium.org/2014/11/the-final-countdown-for-npapi.html
2] https://twitter.com/shimonamit/status/571046844488245248
>
> Thanks,
> Bryan Sullivan | AT&T
>
> -----Original Message-----
> From: Erik Anderson [mailto:eanders@pobox.com]
> Sent: Thursday, May 07, 2015 2:16 PM
> To: public-webpayments-ig@w3.org
> Subject: Bloomberg recommending Browser Extension Community Group. Vote yes!
>
> A Bloomberg colleague is recommending creating a Browser Extension
> Community Group
>
> https://www.w3.org/community/blog/2015/05/07/proposed-group-browser-extension-community-group/
>
> Please vote yes. This may be needed for Payments anyways.
>
> Erik Anderson
> Bloomberg R&D & Co-chair W3C Web Payments IG/SG
>
>
>
Received on Friday, 8 May 2015 15:39:18 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:07:40 UTC