Ethan

> `contentSchema` ... shouldn't be processed at schema load time like a subschema of an applicator or location ($defs) would be. In other words, you shouldn't be able to target...

yeah, I had started commenting here and then saw the new one after.

Prior discussion on the general idea testing of undefined behavior: - https://github.com/json-schema-org/JSON-Schema-Test-Suite/issues/397 - https://github.com/json-schema-org/JSON-Schema-Test-Suite/pull/361 Prior (and current) discussion about testing particular undefined behaviors: - https://github.com/json-schema-org/json-schema-spec/issues/1276 - https://github.com/json-schema-org/JSON-Schema-Test-Suite/pull/386 - more, I'm...

I've just been implementing RJP today. (because apparently I wasn't already sidetracked enough from actually finishing / releasing my 2020-12 implementation.) I also have it operating primarily on my representation...

I think there is no technical reason that this could not be supported and behave like a schema with only a $ref keyword, but I am against it as it...

> Ah, so it's the validator spec that describes this better. If the validation vocabulary is optional, that would explain why the `zeroTerminatedFloats.json` test is optional. the validation vocabulary isn't...

interesting. thank you for the clarification.

Agreed entirely, not a problem that should be addressed for current or past drafts, and not in the future until the spec has found solid stability. Behavior that has become...

allowing pointer fragments in $id was an oversight to begin with. disallowing it resolved a confusing/undefined situation where a schema could identify itself as being at one pointer, while actually...

@MikeRalphson that is interesting and worth thinking about in this context, although I think that embedded metaschema will almost certainly have an $id, and so not need to use any...