around this issue The oneOf, anyOf, ... keywords cannot be used for referencing other definitions. They do work for required. The solution is to declare all properties and only require the properties that are needed in the context. My example would become the following:
seems to work fine In JSON Schema if we have "additionalProperties":false at the root level and "additionalProperties":true nested how are we to resolve this putative "conflict" , They don't override. Their scope is limited to the JSON schema level.