Aaron Coburn

If you want to support storing Verifiable Credentials in a Pod as native RDF, I would suggest reconsidering these criteria. In particular, the `proof` portion of a VC will typically...

> Also, the graph component is allowed to be a blank node, which means that it can not always refer to a resource location. This is quite typical for Verifiable...

> Can't I just have a list of storages? I do not understand the use case motivating the feature that lists all storage locations on a Solid server. Surely there...

We probably need a bit more implementation experience before specifying this endpoint, but it would be good to clarify some expectations. Some initial thoughts based on implementation experience: * There...

> Must auxiliary resource identifiers have same origin as of their subject resource? There is no such restriction

The combination of an [external Memento timegate](https://datatracker.ietf.org/doc/html/rfc7089#section-4.2) would likely suffice in addressing this case without the need to extend or change the Solid (or LDP) specifications. Using [pattern 2.1](https://datatracker.ietf.org/doc/html/rfc7089#section-4.2.1), a...

We have implemented only standard SPARQL 1.1

Before implementing support for `application/sparql-update-single-match` (or any new content type), please first show me a formal specification (even in draft form) that formalizes the semantics. A github discussion is a...

Cognito and KeyCloak are following the [OpenID spec requirement](https://openid.net/specs/openid-connect-discovery-1_0.html#ProviderConfig). There, the `.well-known` path starts not (necessarily) at the root of the server, rather it is appended to the issuer URL....

Closing as requested in https://github.com/solid/specification/pull/409#pullrequestreview-981830187