Aaron Coburn

The OpenID client metadata does refer to email addresses. That said, these documents will be written by third-parties, so any sort of data is possible, including malicious data. One option...

> This will allow the WAC and the ACP systems to come together. I don't understand the motivation for this. WAC and ACP address different use cases.

While a Memento resource may carry with it a promise of immutability, there is a very practical need to be able to delete these resources. In order to comply with...

I would be careful about over-specifying such things. Providing guidance is great, but if the Solid protocol is combined with other, future, specifications, there may be cases where you encounter...

All of this seems fine to me. What would be useful for the multi-resource creation case (neither `/foo` nor `/foo/bar` exist when a server receives a `PUT` request for `/foo/bar/baz`)...

I would rephrase the question here to be something more like: > A client needs a mechanism for finding descriptions of contained resources to further support navigation and application interaction....

> It is quite a burden for applications to fetch each resource to get a hold of what they need This is not what I am suggesting. I agree that...

@csarven Re: Trellis, that code works as described by @jeff-zucker (authZ decisions are made based on container permissions, not based on access to the child resource). Trellis also does not...

Having the server perform weak comparison in this case would deviate from RFC 7231. Quoting from [section 3.1](https://datatracker.ietf.org/doc/html/rfc7232#section-3.1) > An origin server MUST use the strong comparison function when comparing...

> this is hard, because neither really fits with RDF [...] I think we concluded we need another type of validator Yes, indeed! > It seems like if we get...