Sarven Capadisli

We've both intended as additive, so all is good.

Documentation of operations and access modes from discussions. * Write (class of write operations - `acl:Write`) * Append (to add information to resource state - `acl:Append`) * Create (to create...

The WIP table here can be used to get a deeper understanding of operations and access modes. Operations may be determined by the nature of an HTTP request but they...

Provided that we have consensus on the finite set of access modes that can be used by different authorization systems. See also Access Mode Extensions: https://github.com/solid/web-access-control-spec/issues/85

If WAC-Allow is defined in the Solid Protocol ( https://github.com/solid/specification/pull/277#issue-685018474 ) as opposed to the WAC spec, then we can do two things: * Solid Protocol can define the WAC-Allow...

I think we should consider the possibility of clients to suggest the URI of the ACL they want to assign to a resource when creating or updating the resource. It...

PR to follow documenting the URI Template for the Solid technical reports: In a Solid Editors meeting (link to the minutes to follow), an agreement was reached to allocate URIs...

The Protocol does not require that a profile includes pim:storage. I don't think it is a CSS bug. But @Vinnl I think what @NoelDeMartin is referring to this instead: >Clients...

We should not publish duplicate content at both `/TR` and `/TR/`. `/TR/` is the resource we are committing to, whereas `/TR` happens to be a Netlify software bug, an opinion,...

What should be the priority for proper URI allocation, publication and management of Solid Technical Reports on behalf of the W3C Solid Community Group? (Deep breath) If it helps to...