At first glance this looks compatible with the approach used in the OGC Building Blocks [1] which annotate schemas from JSON-LD contexts to allow simple, testable JSON-LD to be combined to support real-world levels of complexity of objects. The tools allow direct embedding of these keywords inline. We have chosen a subset of the same x-jsonld-* naming pattern.
"properties": {
"interestLink": {
"$ref": "#/$defs/coderef",
"x-jsonld-type": "@id",
"x-jsonld-id": "https://w3id.org/ogc/ladm/parcels/interestLink"
},
Of particular interest is the requirements for "structural translation" beyond JSON-LD 1.1 capabilities. [2]
The big advantage of a "fully expressed" JSON-LD context document is that it can use available libraries to resolve.
Here is an example:
https://ogcincubator.github.io/bblocks-examples/bblock/ogc.bbr.examples.linkeddata.forestStandCollection/examples/example-1/map-view
if you click on the map you will get a locale-specific LD version of attributes looked up by LD to a multi-lingual SKOS resource. This is enabled by a reusable LD enabled Leaflet plugin [3]
Let's see if we can find a path to a single library for different functions using the keyword contracts - annotation, rdf conversion and json-ld context aggregation.
[1] https://ogcincubator.github.io/bblocks-docs/create/semantic-uplift
[2] https://ogcincubator.github.io/bblocks-docs/create/semantic-uplift#additional-semantic-uplift-steps
[3] https://ogcincubator.github.io/jsonld-ui-utils/#leaflet-plugin
At first glance this looks compatible with the approach used in the OGC Building Blocks [1] which annotate schemas from JSON-LD contexts to allow simple, testable JSON-LD to be combined to support real-world levels of complexity of objects. The tools allow direct embedding of these keywords inline. We have chosen a subset of the same x-jsonld-* naming pattern.
Of particular interest is the requirements for "structural translation" beyond JSON-LD 1.1 capabilities. [2]
The big advantage of a "fully expressed" JSON-LD context document is that it can use available libraries to resolve.
Here is an example:
https://ogcincubator.github.io/bblocks-examples/bblock/ogc.bbr.examples.linkeddata.forestStandCollection/examples/example-1/map-view
if you click on the map you will get a locale-specific LD version of attributes looked up by LD to a multi-lingual SKOS resource. This is enabled by a reusable LD enabled
Leafletplugin [3]Let's see if we can find a path to a single library for different functions using the keyword contracts - annotation, rdf conversion and json-ld context aggregation.
[1] https://ogcincubator.github.io/bblocks-docs/create/semantic-uplift
[2] https://ogcincubator.github.io/bblocks-docs/create/semantic-uplift#additional-semantic-uplift-steps
[3] https://ogcincubator.github.io/jsonld-ui-utils/#leaflet-plugin