[w3c/permissions] Aspects and integration with Permissions Policy (Issue #459)

antosart created an issue (w3c/permissions#459)

The Permissions specification allows powerful features to have [aspects](https://w3c.github.io/permissions/#aspects) that further restrict or enlarge the allowed capability. However, policy-controlled features in Permissions Policy are simple string which are either allowed or not. So "aspects" are not controllable via Permissions Policy.

What is the guidance on defining new powerful features for which aspects would in principle make sense, but where it would also make sense to control those aspects via Permissions Policy?

One concrete existing example could be ["midi"](https://webaudio.github.io/web-midi-api/#permissions-integration), which specifies a "sysex" aspect.  There is a corresponding ["midi"](https://webaudio.github.io/web-midi-api/#permissions-policy-integration) policy-controlled feature, but in Permissions Policy there is no way of distinguishing between midi-with-sysex and midi-without-sysex.

One perhaps more realistic (future) example could come up with [approximate geolocation](https://github.com/w3c/geolocation/issues/182): it would likely make sense to distinguish between the two variants (precise vs approximate geolocation) both in Permissions and in Permissions Policy, but that seems only doable via two distinguished policy-controlled features (e.g. `geolocation-precise` and `geolocation-approximate`).

Related to #410.

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

Message ID: <w3c/permissions/issues/459@github.com>