Skip to content

Fix scoped context and conflicting properties#263

Open
mielvds wants to merge 5 commits into
masterfrom
204-conflicting-value-override
Open

Fix scoped context and conflicting properties#263
mielvds wants to merge 5 commits into
masterfrom
204-conflicting-value-override

Conversation

@mielvds
Copy link
Copy Markdown
Collaborator

@mielvds mielvds commented May 12, 2026

This PR fixes #204 and two related tests in the test-suite:

https://w3c.github.io/json-ld-api/tests/toRdf-manifest.html#tc037

Nesting terms may have property-scoped contexts defined.

https://w3c.github.io/json-ld-api/tests/toRdf-manifest.html#tc038

Nesting terms may have property-scoped contexts defined.

The issue was that @nest keys were delayed for later expansion before their property-scoped context was applied. This fix first gets the scoped @context from the @nest term and stores this property-scoped context with the key. The delayed nested object expansion then later uses that property-scoped context, so p2 expands to http://example.org/ns#P2 instead of falling back to outer @vocab.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 12, 2026

@mielvds mielvds marked this pull request as ready for review May 12, 2026 19:30
@PonteIneptique
Copy link
Copy Markdown

The tests correspond to the initial issue 👍 Thanks for your work !

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.

@nested node with own vocab has conflicting value overriden

2 participants