[charter 2021] Widen scope of Permission API

[marcoscaceres]

We are looking at expanding the scope of Permissions API to have opinions about UI, lifetimes, etc. so the text is overly restrictive.

[mikewest]

Exciting. Are there sketches of these plans anywhere to skim through? I'm certainly not opposed to doing more work in this area; it's important.

/cc @clelland, @engedy, and @dveditz

[marcoscaceres]

Good starting point https://github.com/w3c/geolocation-api/issues/69#issuecomment-805388266

And issue: https://github.com/w3c/permissions/issues/233

If we agree to widen the scope I'll start drafting up some ideas.

[clelland]

I would love to see the permissions policy features covered by this spec in some way, which could influence the text around UI and lifetimes, but I'm excited to see what comes out of this.

[marcoscaceres]

Ok, so, my rough idea is start with adding a section that broadly describes lifetimes or whatever we like.

Then, in the Permissions Registry, we add something like:

Optional UI requirements:

• UI requirements for the given permission.

So, if there are requirements, they can be individually added for each permission as needed (same as other things in the spec).

Then, for example, in the Geolocation Permission we would add something like:

The UI requirements for the Geolocation Permission are as follows: .... [=lifetime=] MUST something something....

[samuelweiler]

I support removing the limit on the scope; we can keep discussing what to actually do in the doc.