Errors in @context used for schema file exports

[philbarker]

The JSON-LD files exported from https://credreg.net/qdata/schema (and similar pages for other CTDL namespaces) do not contain entries for some of the rdfs: and owl: properties used in the exported data.

They lack the following:

        {
            "rdfs:subPropertyOf": {
                "@type": "@id"
            }
        },
        {
            "owl:equivalentProperty": {
                "@id": "http://www.w3.org/2002/07/owl#equivalentProperty",
                "@type": "@id"
            }
        },
        {
            "owl:inverseOf": {
                "@id": "http://www.w3.org/2002/07/owl#inverseOf",
                "@type": "@id"
            }
        },
        {
            "owl:equivalentClass": {
                "@id": "http://www.w3.org/2002/07/owl#equivalentClass",
                "@type": "@id"
            }
        }

It is very odd that the context files used in these exports are https://credreg.net/ctdl/schema/context/json, https://credreg.net/ctdlasn/schema/context/json, https://credreg.net/qdata/schema/context/json.

Those context files are meant for JSON documents that use ceterms/ctdlasn/qdata respectively; the schema/term definition files use RDF/S, OWL, VS, VANN etc.

There is a huge amount in the CTDL context files that is not needed for the schema / vocabulary definition files, and conversely nearly all of what is needed for the schema / vocabulary definition files is irrelevant to CTDL instance data.

I would recommend creating a context file for the schema / vocabulary definition files. There is not a huge benefit, the irrelevant stuff just gets ignored, but by slimming down the files there will be a small efficiency saving.

[philbarker]

For comparison, the attached context file has everything necessary for the schema definition JSON-LD file.

It is 145 lines (and some of those may not be needed). The file being used at the moment is 1890 lines.

schema_context.json