From conversation with @situx
There are two use case where it would be good for an example to be a reference to an object instead of a standalone file or snippet:
- When the file already exists - such as the set of test cases for GeoSPARQL
- When the objects are being developed as part of a richer information model, and it is painful to snip out each section and update the component building block when the main example is a coherent complex object with cross-references.
By default, if an object is referenced from a graph it should be the implicit SHACL closure - this will also simplify configuration.
A graph reference would be a URI.
JSON path or Xpath could be used for JSON, XML
For JSON, the JSON-LD context would need to be the building block - since it wont know the rest of the containing structure. This may require more @context decoration - examples allow prefixes, we can see how this takes it and allow injection of more context into examples if really needed.
From conversation with @situx
There are two use case where it would be good for an example to be a reference to an object instead of a standalone file or snippet:
By default, if an object is referenced from a graph it should be the implicit SHACL closure - this will also simplify configuration.
A graph reference would be a URI.
JSON path or Xpath could be used for JSON, XML
For JSON, the JSON-LD context would need to be the building block - since it wont know the rest of the containing structure. This may require more
@contextdecoration - examples allow prefixes, we can see how this takes it and allow injection of more context into examples if really needed.