Aaron Coburn
Aaron Coburn
> Indeed, parsing can sometimes be tricky. But I think we're losing track of that fact that parsers will be (and already are) available as reusable libraries. This is true...
Also: `If-Modified-Since` and `If-Unmodified-Since` These aren't specifically ETag-related, but they are also part of the family of conditional requests
The jena dependency is currently tied to the `jena-osgi` artifact. I think it would be much better to set the dependency to `jena-arq`. This way, in a non-OSGi context, dependency...
I believe that only `jena-arq` is necessary for `commons-rdf-jena`; as @stain indicates, `apache-jena-libs` may bring in more transitive dependencies than a user really needs. FWIW, I have been using `commons-rdf-jena`...
> we don't intend to rely on OWL reasoning I very much agree with @elf-pavlik on this.
@justinwb for a little background on the format of Client Identifiers -- The Solid OIDC spec requires at least JSON-LD and using the `../solid/oidc-context.jsonld` context is a SHOULD. This format...
Try using a compact JSON-LD serialization. But generally that looks pretty good. The key thing will be to define the right context
schema.org should have those types already defined.
Also, a client_id profile is really meant to be simple and light weight. I also have concerns about having that serve so many different purposes simultaneously
> In the end, if someone really wants to conflate a Social Agent with an Application they can use the same WebID for both, I would just discourage that practice....