Update output schema to describe new structure #1285
Conversation
| "type": "string", | ||
| "format": "json-pointer" | ||
| }, | ||
| "absoluteKeywordLocation": { | ||
| "schemaLocation": { | ||
| "type": "string", | ||
| "format": "uri" |
There was a problem hiding this comment.
Shouldn't this be iri now?
There was a problem hiding this comment.
ah I see you're already on it, re the other PR about uri->iri changes.
There was a problem hiding this comment.
I'm going to push this forward as I can't wait on your PR any longer. It needs to be rebased anyway.
| "$ref": "#/$defs/outputUnitArray" | ||
| } | ||
| }, | ||
| "required": [ "valid", "nested" ] |
There was a problem hiding this comment.
Why does the 'basic' format contain 'nested'? My understanding was that basic is still a flat structure.
There was a problem hiding this comment.
Basic is an object with only valid and nested at the root. The rest is normal output units in the nested array.
{
"valid": true,
"nested": [ <flat list> ]
}This provides the overall validation result at the root and a flat list. It's the same as 2020-12, except that the location properties aren't required at the root (because they're always just / and redundant).
gregsdennis
force-pushed
the
gregsdennis-update-output-schema
branch
from
f365c65
to
0431059
Compare
|
Shouldn't this have gone into draft-next, not main? |
|
@karenetheridge draft-next was merged some time ago. |
Updates the output schema file to match the new structure as described by the specification. Follow-up to #1249.
I've tested this against the example output in the spec.
Resolves #949