Re: Permission API Review: Fwd: [blink-dev] Intent to Ship: Permissions API

Daniel Appelquist <[email protected]>
Newsgroups gmane.org.w3c.tag
Message-ID <[email protected]>
Alex - should we use this week’s call to cover this topic / finalize and agree the feedback?

Thanks,
Dan

> On 6 Apr 2015, at 23:16, Alex Russell <[email protected]> wrote:
> 
> Hey all,
> 
> Per previous conversations, it looks like now would be a great time for others here to give our draft feedback on the Permissions API a look:
> 
>     https://github.com/w3ctag/spec-reviews/blob/master/2015/03/Permissions.md <https://github.com/w3ctag/spec-reviews/blob/master/2015/03/Permissions.md>
> 
> Regards
> 
> ---------- Forwarded message ----------
> From: Alex Russell <[email protected] <mailto:[email protected]>>
> Date: Mon, Apr 6, 2015 at 3:15 PM
> Subject: Re: [blink-dev] Intent to Ship: Permissions API
> To: Marcos Caceres <[email protected] <mailto:[email protected]>>
> Cc: Dimitri Glazkov <[email protected] <mailto:[email protected]>>, Philip Jägenstedt <[email protected] <mailto:[email protected]>>, Elisabeth Morant <[email protected] <mailto:[email protected]>>, Philip Rogers <[email protected] <mailto:[email protected]>>, Mike West <[email protected] <mailto:[email protected]>>, Jake Archibald <[email protected] <mailto:[email protected]>>, blink-dev <[email protected] <mailto:[email protected]>>, Mounir Lamouri <[email protected] <mailto:[email protected]>>
> 
> 
> /me puts TAG hat on
> 
> I'm grateful for Mounir's work on updating the design based on feedback. I think it's getting better VERY quickly.
> 
> Given the time constraints, I spent some time over the weekend updating the TAG feedback based on the latest draft <https://github.com/w3ctag/spec-reviews/blob/master/2015/03/Permissions.md>. The other TAG members (and the list) need to weigh in (I'll circulate it today to get input ASAP), but I think it covers the bases.
> 
> The biggest issues are:
> The "string-ness" of the status value. I worry about the ability to model the full set of permissions without a more extensible type and it will be hard to retrofit later
> Lack of reflection for the majority of web platform permissions
> An inability to enumerate which permissions are supported by the API
> Regards
> 
> 
> On Mon, Apr 6, 2015 at 12:37 PM, Marcos Caceres <[email protected] <mailto:[email protected]>> wrote:
> 
> 
> 
> On April 3, 2015 at 5:28:23 PM, Dimitri Glazkov ([email protected] <mailto:[email protected]>) wrote:
> > Looking over W3C TAG activities, seems like they provided useful feedback
> > on the API: https://github.com/w3ctag/spec-reviews/issues/45 <https://github.com/w3ctag/spec-reviews/issues/45> and
> > https://github.com/w3ctag/spec-reviews/blob/master/2015/03/Permissions.md <https://github.com/w3ctag/spec-reviews/blob/master/2015/03/Permissions.md>
> >
> > Have the issues mentioned been addressed?
> 
> I believe so. Mounir went through each issue raised and made modifications to the spec as needed. Not all recommendations were accepted by the Editors. Having said that, there is still time to iterate over the design as implementation/user experience is gained.
> 
> 
> 
>
signature.asc (application/pgp-signature, 455 B)
-----BEGIN PGP SIGNATURE-----

iQEcBAEBCAAGBQJVI+XiAAoJEKrgifdQB5UFtmkIAJLVuFMSxMDDjiZczFO07069
yHta9Xxyo155Xsd1Pz9NZHo0W9kb3p5QVIRh2UqAI8EjQfg6pdkAxCbII3OMpmzT
qlgjl3YjfKbJoD+E7vMZlwACLourINRHnHKK13XF+cOteorxyBfYPTOrxRnTRoXi
znb5TFxTsTd7ZCx4CFuSVfjN6czdoecSbzgWp0xBg47YdvA/H5t8/9XEUzxXWz44
UV5BVAUr92aU3E52OE+lYZAMLgIZWju6qMuPvRwejXiz+vIA3E8K/4TSRQfgmo4L
ym6wFUmyGIAmAGJeWrrwYfWKs0d+7shD+HkOVUz+i3AYBKYQb8c1lH6z7ioIjCw=
=J044
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.