Re: [w3c/permissions] Rename document (Issue #478)

riannella left a comment (w3c/permissions#478)

I think there is an underlying assumption here that is worth challenging.

The Permissions document defines a particular model for browser-managed permissions, and within that scope it is entirely appropriate. However, the Web is considerably broader than that model.

Many specifications define concepts of permissions, authorisation, rights, entitlements, capabilities, policies, or constraints that operate at different architectural layers (application, protocol, content, enterprise, distributed systems, etc.). These are not replacements for the "Permissions" document, nor are they necessarily intended to integrate with it.

If the implication is that all permission concepts on the Web should be represented through, or aligned with, the "Permissions" document, that seems to be an unnecessarily broad interpretation of the document's scope. No single specification should be expected to define the complete semantics of “permissions” for the entire Web ecosystem.

It may therefore be more productive to acknowledge that “permission” is a broader architectural concept, with the "Permissions" document being one important, but specialised, realization of that concept. Recognising that distinction would avoid giving the impression that the document is intended to be the authoritative model for every use of the term “permission” across W3C and the wider Web.


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

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