[w3c/permissions] WIP: Define a permission store (closes #384) (PR #390)

This is a draft attempt at defining a permission store with a couple of questions still to be figured out, some of which are also marked as issues inline. Some high-level thoughts:

- I've so far declared a single global permission store to be maintained by UAs, is that what we were shooting for?
- We should still allow for UAs to have more flexibility in storing smaller-scoped or shorter-lived permissions, e.g. for a single tab. It feels like this needs to be a non-normative note as attempting to specify that might go against the idea that it can be flexible.
- This ignores a lot of details around how we need to cross the process boundary to access permissions, though I've tried to make setting (and removing) permissions an async step.
- As discussed with Anne before, there's the question of whether individual permissions should define their own key generation algorithms or whether they should get if-statements in the central key generation algorithm.

Requesting an early look/advice from @annevk and @jyasskin :)
You can view, comment on, or merge this pull request online at:

  https://github.com/w3c/permissions/pull/390

-- Commit Summary --

  * WIP: Define a permission store (closes #384)

-- File Changes --

    M index.html (117)

-- Patch Links --

https://github.com/w3c/permissions/pull/390.patch
https://github.com/w3c/permissions/pull/390.diff

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/permissions/pull/390
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/permissions/pull/390@github.com>