Skip to content

Conversation

@dylankerr-bis
Copy link
Contributor

Resolves #787.

Changes confirmed against the NetworkNT JSON Schema Validator, which is where the ambiguity was first noticed. I confirmed that the prior version of the NetworkNT validator fails the new tests as expected (it throws an exception while trying to load the non-existent https://example.com/draftX-Y/ref-and-id3/bar.json), and that the latest/fixed version passes the new tests.

@jdesrosiers might be a suitable reviewer.

@notEthan
Copy link
Contributor

I was having trouble figuring out what exactly was in these that wasn't already covered. The distinction from the existing tests is siblings $id and a $ref resolved relative to that $id in a non-root schema? where previously $id + relative $ref as siblings was only in a root schema

Tests look correct to me, passes in my implementation.

Copy link
Member

@jdesrosiers jdesrosiers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! Please add this test to the v1 folder as well and this is good to go.

Copy link
Member

@jdesrosiers jdesrosiers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@jdesrosiers jdesrosiers merged commit 980e105 into json-schema-org:main Oct 31, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Clarification needed - Sibling $id and $ref in nested schema resources

3 participants