Brainstorming the space of rendering semantic and linked metadata in a data catalog

[jsheunis]

First, a dirty braindump:

I'm making the type of progress that doesn't feel like progress at all. Been reading a lot to learn more about the tools and standards that we'll deal with when using semantically linked metadata to generate datasets and represent them in catalogs.

I'm focusing on the web-related aspects for now, i.e. structured and linked metadata being represented as dataset pages in catalogs, and wondering about things like: how would one validate a json-ld record being added to a catalog? how would one split up a large jsonld document while not complicating future retrieval? how would one query a whole catalog of linked data? should we consider graph databases? is it possible to have a client side graph database and are there existing javascript tools to deal with parsing, querying, etc?

I'll still order my thoughts and write them down in a sensible way for brainstorming, but at the moment it's mostly a blur of triples and turtles and sparqles and too many open W3C tabs.

Some links that I came across:

• https://github.com/json-ld/json-ld.org
• https://github.com/json-ld/json-ld.org/blob/main/schemas/jsonld-schema.json
• https://github.com/mulesoft-labs/json-ld-schema
• https://docs.ropensci.org/codemetar/articles/validation-in-json-ld.html
• https://www.w3.org/2019/wot/json-schema
• https://blogs.pjjk.net/phil/json-schema-for-json-ld/
• https://www.npmjs.com/package/jsonld
• https://github.com/digitalbazaar/jsonld.js
• https://www.w3.org/TR/shacl/
• https://github.com/zazuko/rdf-validate-shacl
• https://www.w3.org/TR/shacl-js/

[jsheunis]

This issue served its purpose during the research phase and can now be closed.