Currently the implementation expects that the schema provided is the properties of an object type. For most cases, this is probably fine, but I am finding it a little limiting because I am unable to define top-level properties, such as required, propertyNames, additionalProperties, et al.

As such, I feel like projects could benefit from being able to define their own schema at any level, or default to the preexisting behavior: if the top level of the given schema doesn't define either definitions or type, then assume it's the original schema style and wrap it in its own properties key. Otherwise, allow the schema writer to define any level of the JSON schema.

I'd be willing to work on this, but only if there is buy in.