Gregg Kellogg
Gregg Kellogg
It's reasonable for the frame document to be used as a context. The only thing a JSON-LD processor looks for in a remote document used as a context is the...
Transferred from json-ld-api to json-ld-bp.
These options refer to JSON-LD specific options, defined in the [JSON-LD API](https://www.w3.org/TR/json-ld11-api/#the-jsonldoptions-type) and [JSON-LD Framing](https://www.w3.org/TR/json-ld11-framing/#jsonldoptions) and are only available when the input format is "jsonld". For more information see those...
Yes, the json-ld playground doesn't expose all options, but it's lacking adequate developer support. My UI is built automatically based on options specifically defined for readers and writers. The "expandContext"...
The SQLite3 store will provide persistent storage, and may scale better for even larger graphs, but it is slower for smaller graphs. That would be :store => SQLite3.new(:path => "store.db")....
Riffing off of @pchampin's example in https://github.com/w3c/json-ld-syntax/issues/91#issuecomment-445313785, we might use data indexing to aid access: ```json { "@context": { "occupation": { "@id": "ex:occupation", "@type": "rdf:HTML", "@container": "@data" }, "description": "ex:description"...
Its not a language tag, it’s a data index which has no RDF representation. It’s useful for creating structural indexes.
JSON-LD has also changed quite a bit since the original BP was done. We can do a lot more using a combination of a context specified via _profile_ to application/json,...
This is the intended purpose of `@included`, to contain objects associated with, but not necessarily directly referenced by other objects in the same document. However, if "location" is of type...
> @gkellogg Thank you so much for your quick response. > > I was assuming that `location` would be of type `@id`. I wasn't sure if it was better for...