the output format examples does not validate with the output schema

[santhosh-tekuri]

below is the basic output format example from spec:

{
  "valid": false,
  "errors": [
    {
      "keywordLocation": "",
      "instanceLocation": "",
      "error": "A subschema had errors."
    },
    {
      "keywordLocation": "/items/$ref",
      "absoluteKeywordLocation":
        "https://example.com/polygon#/$defs/point",
      "instanceLocation": "/1",
      "error": "A subschema had errors."
    },
    {
      "keywordLocation": "/items/$ref/required",
      "absoluteKeywordLocation":
        "https://example.com/polygon#/$defs/point/required",
      "instanceLocation": "/1",
      "error": "Required property 'y' not found."
    },
    {
      "keywordLocation": "/items/$ref/additionalProperties",
      "absoluteKeywordLocation":
        "https://example.com/polygon#/$defs/point/additionalProperties",
      "instanceLocation": "/1/z",
      "error": "Additional property 'z' found but was invalid."
    },
    {
      "keywordLocation": "/minItems",
      "instanceLocation": "",
      "error": "Expected at least 3 items but found 2"
    }
  ]
}

if I validate the above json with https://json-schema.org/draft/2020-12/output/schema#/$defs/basic I get following validation errors:

jsonschema validation failed with https://json-schema.org/draft/2020-12/output/schema#/$defs/basic
- at '': validation failed
  - at '': missing properties 'keywordLocation', 'instanceLocation'
  - at '/errors': validation failed
    - at '/errors/0': missing properties 'valid'
    - at '/errors/1': missing properties 'valid'
    - at '/errors/2': missing properties 'valid'
    - at '/errors/3': missing properties 'valid'
    - at '/errors/4': missing properties 'valid'
  - at '': missing properties 'absoluteKeywordLocation'

which one is correct? the example from spec or the schema published ?

[gregsdennis]

I hand-wrote most of this, so there are likely errors.

Secondly, the output isn't really well defined, and has a lot of other issues.

Lastly, the output schema is really informational at best. It's not intended to be prescriptive; it's a convenience.