ata-validator

$vocabulary is honoured when a schema names a custom meta-schema in $schema. A dialect is a set of vocabularies and a vocabulary is a set of keywords, so a keyword whose vocabulary the meta-schema does not declare is not part of that dialect at all: it is an unknown keyword, and an unknown keyword is ignored. A schema written against a meta-schema which declares only the core and applicator vocabularies now has its minimum, type and the rest of the validation keywords ignored, while properties and the other applicators still apply. The keywords belonging to each vocabulary are read from the vendored meta-schemas rather than from a list kept by hand, so they come from the specification. Removing the keyword before compilation means every engine agrees without any of them knowing what a vocabulary is.

bundleStandalone and bundleCompact built the error-reporting function from the schema the caller passed rather than the one the validator compiled. Anything which prepares a schema therefore reached the boolean path and not the error path: with assertFormat: false the bundle reported a format error the caller had turned off, and only once some other keyword failed first, since the error function runs only after the boolean one says no. toStandalone already read the compiled schema; these two now do as well.