All of the JSON schemas define the@type property within the properties property, but data_repository_schema.json is unique in that it has a @type property inside of properties and also at the top-level of the schema object. See the 6th and last lines of the following code snippet:
{
"id": "https://w3id.org/dats/schema/data_repository_schema.json",
"$schema": "http://json-schema.org/draft-04/schema",
"title": "DATS data repository schema",
"description": "A repository or catalog of datasets. It could be a primary repository or a repository that aggregates data existing in other repositories.",
"@type": "DataRepository",
"type": "object",
"properties": {
"@context": {
"anyOf": [
{
"type": "string"
},
{
"type": "object"
}
]
},
"@id": { "type": "string", "format": "uri" },
"@type": { "type": "string", "enum": [ "DataRepository" ]},
I'm pretty sure this is a typo because the top-level @type declaration implies that the JSON schema object is itself a DataRepository instance, which it is not.
All of the JSON schemas define the
@type
property within theproperties
property, butdata_repository_schema.json
is unique in that it has a@type
property inside ofproperties
and also at the top-level of the schema object. See the 6th and last lines of the following code snippet:I'm pretty sure this is a typo because the top-level
@type
declaration implies that the JSON schema object is itself a DataRepository instance, which it is not.