Henry Andrews

Now it 's in both places.

Yes, this should be fixed, thanks! The first part dates from when unknown keywords SHOULD be ignored but really now that they're SHOULD collect as annotations it makes even less...

@gregsdennis I see what you're doing with the `anyOf` to potentially still produce a valid outcome, but just to make sure I understand, even this: ```JSON { "$ref": "https://uresolvable.uri/schema" }...

@gregsdennis I think this gets into some really important design questions that we've touched on in our IM discussions. my mental model for JSON Schema evaluation is something like: ```Python...

(let me just note that I am aware that @gregsdennis was not suggesting that output was the only way to handle this, and I should have made that more clear...

I was making a distinction between using the full error output (in which case I would probably embed it in an `application/problem-detail+json` response, assuming the likely required action was the...

> So I think the best first step is simply to have a file with an array of the schemas and descriptions themselves, and no assertion. @Julian I'm not sure...

So people writing test executors would write something like: ```Python if 'valid' in test_case: # run validation and check against the valid field else: # run valid and fail the...

> I think it'll be even easier to match based on the directory and we not mix test types between the two -- so errors/ contains tests with different structure....

> unknown media type referenced in `contentEncoding` or `contentMediaType` This is no longer a concern in 2020-12, as these keywords are just annotations. > unknown vocabulary referenced in $vocabularies This,...