You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The effect of specifying the same fragment name multiple times within the same resource, using any combination of "$anchor" and/or "$dynamicAnchor", is undefined. Implementations MAY raise an error if such usage is detected.
A schema MAY (and likely will) have multiple IRIs, but there is no way for an IRI to identify more than one schema. When multiple schemas try to identify as the same IRI, validators SHOULD raise an error condition.
It would be good to have 8.2.2 refer to 9.1.2 (as it is more general), so that the "SHOULD raise an error" requirement is consistent regardless of how the schemas came to have the same IRI.
The text was updated successfully, but these errors were encountered:
The spec mentions duplicate IRIs in two places with slightly different requiremetns:
§8.2.2 "Defining location-independent identifiers (last paragraph):
§9.1.2 "Loading a referenced schema" (last paragraph):
It would be good to have 8.2.2 refer to 9.1.2 (as it is more general), so that the "SHOULD raise an error" requirement is consistent regardless of how the schemas came to have the same IRI.
The text was updated successfully, but these errors were encountered: