Sarven Capadisli

A couple of things: If you (and others) have concerns about Protocol's requirements/wording, can you raise it in solid/specification? I've tried my best to express "When using Web Access Control"...

I agree that it'd be useful to have a list of access modes needed by some requirements. However, I'm not agreeing on where or how to apply that information (yet)...

Important not to conflate document- and content-level access control! Thus far, WAC's use of ACL's access modes is for resources as opposed to their description. Prefer is a client hint,...

>https://github.com/solid/web-access-control-spec#authorization-schema has clear way of restricting valid values using ShEx Cool. Nice try. Please read the whole section.. starting with the very first sentence: >>This section is non-normative. ( Issue:...

Acknowledging this.. I believe a part of this UC re blocking is covered in https://github.com/solid/authorization-panel/pull/112 . Will follow-up to see if removal of access can be covered beyond the current...

Authorization Capabilities for Linked Data (An object capability framework for linked data systems): https://w3c-ccg.github.io/zcap-spec/ Fetch coffee: https://lists.w3.org/Archives/Public/public-credentials/2020Dec/0028.html

"Draft" at the end is both readable and works with most common template/order (`W3C `).

Can't reproduce this. One possibility is a bug in lower level base URI assignment, e.g., perhaps the fetched document is using relative path in link href. Closing.

I can reproduce at e.g., https://dokie.li/?style=https://www.w3.org/DesignIssues/di.css . Everything generally looks fine, i.e., the selected stylesheet is added to `head` with `link` and all other `link` stylesheets are marked as `alternate`...

Closing issues as there a number of existing issues touching authentication and UI: https://github.com/linkeddata/dokieli/issues?q=is%3Aopen+label%3Aauthentication+label%3AUI