Closed reitzig closed 5 years ago
This may be related to json-schema-org/json-schema-spec/issues#672, in which case it's not a bug at all but the specified (or at least intended, at draft 4) behaviour.
I have confirmed that with the corrected schema the result is as expected. My apologies.
The following pair should validate:
JSON:
For reference, this exact pair validates with Ruby's json-schema.
However, with
json-schema-validator
(2.2.10) I get:There are two three-way
oneOf
s in this schema:A case distinction over
patient
,physician
, andstaff
(see top-level schema) -- but those schemas (given by reference) have mutually exclusive singletonenum
properties, e.g.for
patient
, and similar for the other two types.Different combinations of
method
andmethodId
in the referencedmember-key
schema. There, we have three cases like so:Again, we see that the three cases are mutually exclusive.
In summary, it is impossible for any JSON to cause this error (and the given one certainly doesn't), There must be a bug in the validator.