Henry Andrews

@martingkelly why would you try to do anything other than edit the files in YAML? The build step would happen before you try to load anything, so you shouldn't need...

> My point is just that I would then have to (non-intuitively) write schema.json in my file instead of schema.yaml, even though I am referring to schema.yaml No, you're referring...

The spec already makes a point of saying that it interprets instances according to a [data model](https://tools.ietf.org/html/draft-handrews-json-schema-01#section-4.2.1) rather than as JSON text. This holds true when the schema is an...

`contentMediaType` is for media types encoded as JSON strings, so I don't _think_ it helps here? > but since it's not specified how a parser should interpret a given $ref,...

The idea of treating `$ref` as an RFC 8288 web link and allowing target hints has come up at least once before (with OpenAPI), but in a somewhat different context....

Depending on your workflow, if you don't need the custom meta-schema at runtime, as a workaround you can validate pre-existing schemas against a custom meta-schema by just treating then as...

The instance location for `required` should be the object that's supposed to contain the required properties, rather than individual properties. The actual missing properties would have to be listed in...

@steffen-l would you be receptive to pull requests? I didn't see a contributors' guide but perhaps I overlooked it somewhere. Not promising anything but I am really liking this tool...

@steffen-l great to hear on both counts. I'll hold off on this one and wait for the next release.

@JamesMessinger thanks for digging into this! I know it poses more of a challenge for your packages than for most implementations that focus on validation. There are a lot of...