doc: JSON with JSON Schema in list of validators#6
doc: JSON with JSON Schema in list of validators#6candleindark wants to merge 1 commit intocon:mainfrom
Conversation
JSON doesn't provide validation of any data instances but JSON Schema does.
|
well, there is more to the story:
|
|
In that case, may be I should have added "JSON Schema" to the list instead of replacing "JSON" with "JSON Schema". They are two different standards. What do you think? For a widely used standard like JSON Schema, should our efforts to harmonize validation outputs focus solely on a specific validator implementation, such as python-jsonschema? There are many validator implementations available. |
|
I think it might be worth refactoring that listing into a table since we keep talking about different aspects and would be useful to disentangle and not conflate
edit: @candleindark rightfully mentions that standard itself is not necessarily defines the format/standard for the validation results -- those are typically "validation tool" specific. |
|
note: as for BIDS we elaborated a diagram which includes its components in |
JSON doesn't provide validation of any data instances but JSON Schema does. I think JSON Schema is what was originally intended.
Additionally, is the listing of
YAMLneeded since it seems thatYAMLis reallyJSON Schemaspecified in YAML format?