Dave Vieglais

See also #41

Yeah, I think the intent of #48 is to clarify that everything with a `@type` should also have an `@id` to avoid blank nodes in the json-ld graph (i.e. nodes...

Agreed that this can't be a requirement, more a recommendation. It would be absolutely useless to assign a bunch of short lived or otherwise fragile URIs to the `@id`s just...

Perhaps a general recommendation could be to have the JSON-LD present at the location where the Dataset identifier resolves to, and relative URIs for components of the dataset (unless components...

The relative URI is a valid semantic web identifier. The URI is relative to the location of the document - since the document was retrieved to be viewed, it must...

+1 for SHACL. The European Legislation Identifier (ELI) system is a good example of a community using SHACL shapes for promoting consistent content representation [1]. I expect a similar library...

Suggesting this for release 1.3 primarily to support inclusion of practical, executable examples within the guidelines.

It's an interesting suggestion. Creating a new class and the associated management it encumbers feels a little heavy for this case. It does raise a couple questions for me: Is...

There is a `schema.org` [`ChooseAction`](https://schema.org/ChooseAction) construct that may be applicable. I think the example might be like the following, but not sure action is even appropriate for this: ``` {...

Excellent point @rduerr. When I first posed the question, my perspective was quite narrow with the goal being "simply" to determine which `identifier` should be presented in a user interface...