For spec's, required terms are now included in the required array at the end of each Class JSON-Schema file
Arrays for repeatable terms (e.g. for ltc:typeOfCollection) include "type" and "description", not "$ref"
For now, "type" within the array defaults to "string" until the datatypes CSV includes array-datatype
Related: String "formats" also can't be auto-generated until the terms or datatype CSVs can define the format-requirements.
e.g. - see notes below from #433 :
The terms or datatype CSVs may need a new column or value to specify string "format" -- e.g. to regenerate the date/date-time format specified for these 4 terms:
"endedAtTime": {
"description": "The date or time when a Person stopped fulfilling the role specified in the role property.",
"type": "string",
"oneOf": [
{
"format": "date"
},
{
"format": "date-time"
}
]
}
@essvee & @jbstatgen -- When you have a chance does this pull-request / auto-generated JSON-Schema look good on your end?
I reverted the current review branch standard/json-schema files to how they were before auto-generated JSON-schema files were added.
Recap:
These JSON terms were autogenerated by running
csv_to_json.py
with the current review-branch CSVsif "tdwgutility_required" = "Yes" in CSV:
"minItems"
(for array-terms) is currently set to1
in JSONrequired
array at end of json file."uniqueItems"
defaults totrue
in JSONShould term names in JSON-Schema be formatted "namespace:term_localName"?
$id &
$ref` URI-values point to resolvable 'raw' github URLS on the "review" branch, rather than "master"python3 csv_to_json.py
Fixes:
required
array at the end of each Class JSON-Schema fileIf anything looks mangled, all ears!