Sarven Capadisli

Instead of investing further energy on the differences, can we consolidate the flavours? Bring in the good parts from all to the table. Any particular technical or social barriers? If...

Expiry sounds good. "Valid" "from/to" or "not before/after" seems fine too. Just to add to scenarios where this can be useful from an application's perspective: going in/out of offline mode....

This issue is mostly a duplicate of https://github.com/solid/web-access-control-spec/issues/10 and it'd be good to take it up around the same time with that and Kjetil's related PR: https://github.com/solid/web-access-control-spec/pull/37 The essence of...

Naming things is hard. Renaming would be quite costly to deployed software in addition to handling security considerations. I do not see a clear benefit. A container's ACL resource with...

Aaron's review/explanation is correct and as intended. I'd add that WAC currently does not require SPARQL Query or Update - they're used non-normatively. "Mechanisms that can be used to find...

The authority of a resource determines what the resource refers to - generic or specific. The server manages the association of an ACL resource to a resource, sets any constraints...

What aspects of the interaction or flow are expected to be prescribed (as per "spec")? Not that I'm against email, but see the following as to make a "request" via...

As discussed elsewhere issues/chats.. one thing that could be spec'd is the "shape" (SHACL/SheX/Whatever) of the request notification that an application sends to the server's inbox eg. who wants it...

FWIW, the way I see it for the WAC spec is to not require additional dependencies like email. Use cases around requesting should work independently - decoupled from other major...

re "suggestion", I meant the actual text to replace the current with (for PR). I think we're in agreement on the guideline.