Aaron Coburn

@csarven one possible issue with this proposal is whether a client _suggests_ an ACL location or whether a client _assigns_ an ACL location to a resource. And also whether a...

The GNAP terminology is very useful here, even if one is not using the GNAP protocol. I am :+1: on any mechanism that is able to distinguish between an App...

The important subtlety is that WAC and the Solid Protocol are separate, orthogonal specifications. The Solid Protocol requires WAC, but WAC does not require Solid. In fact, there are other,...

The mime-type `application/json+ld` is not valid. Perhaps you mean `application/ld+json`?

@scenaristeur the server may not support arbitrary external contexts. If you must use JSON-LD for writes, try embedding the context in the data payload.

In order to support content negotiation (per Solid protocol) for RDF resources, if a client uploads a JSON-LD document and then tries to content negotiate the representation as Turtle, the...

JSON-LD is an RDF resource. Unless you are uploading that with `Content-Type: text/plain` or `Content-Type: application/octet-stream`, that resource will be treated as RDF. Therefore, a client can content negotiate it....

Jena doesn't currently support Titanium directly: https://issues.apache.org/jira/browse/JENA-1948, but it would be quite possible to swap this in at the `JenaIOService` layer in the `::read` and `::write` methods.

Given that Titanium uses the `jakarta.*` namespace (JakartaEE 9), it will be a little while until Titanium support can be integrated into Trellis. We need to wait until (1) MicroProfile...

Much of the current work related to authentication in Solid is being conducted in the context of the [Authentication Panel](https://github.com/solid/authentication-panel), and the current [draft specification](https://solid.github.io/authentication-panel/solid-oidc/) will have the most up-to-date...