JSON‐LD Standardizing

For our information model, we need to standardize the structure. Without this, graph performance may be problematic (That is an assumption based on observation of the present, just load it).

In addition, skolemnizing RDF means that node subjects change with each 'release'. We can fix this by creating @id's when informaiton is missing from the json-ld.

We should validate the data, and send to repositorie

This should be done as a watcher in dagster. Watch when a summon is updated, then created standardized representation.ter Or this is a step triggered after gleaner, but before nabu

Proposed rules: Rule: validate @id's if there is a space, or other bad character, this breaks, at least pyld, when transforming to RDF So, if ID is not http, https, uri or a defined namespace in context, if it does not have a prefix, it can be seen a a local reference, see if you can find that reference (has to be rules somewhere)

Rule: @id for objects with @type use identifier, name, or other pattern to come up with a

Rule: standardize @geo, and remove extraneous point lists can be long, and do not add any useful information to Make these WKT objects that can be indexed for geospatial search.

Rule: properties are arrays.

Rule: pull in references

Discussion: Spilt into objects.