Skip to content

Consolidate language around duplicate schema IRIs #1271

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
handrews opened this issue Aug 12, 2022 · 0 comments · Fixed by #1272
Closed

Consolidate language around duplicate schema IRIs #1271

handrews opened this issue Aug 12, 2022 · 0 comments · Fixed by #1272
Labels
clarification Items that need to be clarified in the specification core Priority: Low

Comments

@handrews
Copy link
Contributor

The spec mentions duplicate IRIs in two places with slightly different requiremetns:

§8.2.2 "Defining location-independent identifiers (last paragraph):

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.

§9.1.2 "Loading a referenced schema" (last paragraph):

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarification Items that need to be clarified in the specification core Priority: Low
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants