Dave Vieglais

A more general solution may be to support Link headers [1, 2] for resolving the location of external contexts (when not available in a local cache). See also #85. When...

I have the same issue trying Marta 0.8.1 on Intel Mac running 13.5.1 (22G90). The app does run successfully when started from the downloaded .dmg but not after copying the...

DataONE services use `SSLVerifyClient optional` for clients to optionally authenticate using a client certificate which is one reason for TLS renegotiation occurring. RFC 5746 identifies the TLS renegotiation extension that...

JSON-LD is a serialization of RDF, so is describing a graph. I'm not sure there's a definitive "root object" in these examples. Instead there's a graph of related nodes, any...

I believe this is the type of issue that is addressed by JSON-LD Framing [^1]. So instead of suggesting a preferred pattern of serialization (generally cumbersome when serializing from an...

Reading through the examples above, it strikes me that neither option 1 or 2 above provide an identifier for the described resources. So although this issue seems to be about...

Note that conceptually, the graph `ex:URIforImageObjectNode` and the document identified by `ex:URIforTheMetadata` (i.e. the document itself, not the `ex:URIforDigitalDocumentNode` node in the graph) fill the same role. They both describe...

Sure, you could do that, but I think it is incorrect to always infer that `@id` has the same purpose as `schema:identifier`. To me at least it is much clearer...

@smrgeoinfo In your example, what is returned when resolving `ex:URIforDescribedResource`?

So I managed to get myself confused about a subject of the graph (i.e. `ex:URIforDescribedResource`) and the graph itself (i.e. the entire JSON-LD document). Steve is correct that the `@id`...