Aaron Coburn

My preference is to use two digits in the versioning scheme: `solid.0.1-alpha`. Three digits makes sense for software but protocols tend to use only one or two digits.

Dropping `alpha` is fine with me

In the context of shape validation, it is suggested that Write access on the resource would allow an agent to modify the corresponding shape for that resource. If that is...

For machine readability, we could also make use of Link headers with [`rel="http://www.w3.org/ns/ldp#constrainedBy"`](https://www.w3.org/TR/ldp/#h-ldpr-gen-pubclireqs). That could point to an IRI that gives lots of additional information. I would also note that,...

It is important not to conflate things. Firstly, WebIDs can and are used to identify applications. Applications that use this mechanism will also need to be capable of managing private...

@elf-pavlik I very much agree with https://github.com/solid/specification/issues/463#issuecomment-1279315991 I would also emphasize that, given that we are using the OpenID Connect framework for authentication, there are several distinct conceptual entities: *...

To me, it seems that there are two reasonable solutions here, using the various specifications in their current form: 1. Use separate identifiers, one to align with WebID and the...

@RubenVerborgh I share your concerns about cookie-based auth on the RS, which is why I have generally resisted any form of cookies at that layer. However, there are some practical...

FWIW, I'm also inclined to say "implementation", though some non-normative language guiding implementers would be great, especially as this relates to security.

Hi @joepio! if I am not mistaken, it is possible to do what you propose right now, without modifying the solid specification (or any other specification). What is required is...