W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2014

Re: Proposal for a Permissions API

From: Marcos Caceres <marcos@marcosc.com>
Date: Fri, 5 Sep 2014 08:42:22 -0400
Message-ID: <CAAci2aCz9AKbO9PXsXkcWyU642vf9TeanUmonnOzJMFOBZJGpw@mail.gmail.com>
To: "Kostiainen, Anssi" <anssi.kostiainen@intel.com>
Cc: "Kis, Zoltan" <zoltan.kis@intel.com>, Florian Bösch <pyalot@gmail.com>, "Edward O'Connor" <eoconnor@apple.com>, Webapps WG <public-webapps@w3.org>
On Friday, September 5, 2014, Kostiainen, Anssi <anssi.kostiainen@intel.com>
wrote:

> On 04 Sep 2014, at 23:18, Marcos Caceres <marcos@marcosc.com
> <javascript:;>> wrote:
>
> > Absolutely, we should be addressing them at the API level.
>
> I guess you mean each API should address this in a way that fits the
> design of the particular API the best?


Correct. Sorry if I wasn't clear.


>
> And something like permissions.js could then be used to abstract away the
> differences and provide an API similar to that proposed by Mounir?


I would hope we wouldn't need that, but sure. It's a risk (reality?) that
we end up with inconsistencies across APIs.


>
> > For instance, adding a way to determine if the permission has been
> granted in Geo without actually needing to use the API.
>
> It seems as if Mounir’s proposal addresses exactly this requirement, but
> not at the “[Geolocation] API level”.


Which I'm personally not a huge fan of.


>
> Thanks,
>
> -Anssi
Received on Friday, 5 September 2014 12:42:51 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:26 UTC