examples: normalize JSON-LD structure in data-quality example #149
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jgeluk
requested review from
FroehlichMarcel,
andrea-gioia,
joshcornejo,
nvar,
rivettp and
tonyseale
as code owners
Member
Author
|
@joshcornejo can you review this one? |
This was referenced Oct 27, 2025
Contributor
|
Looks fine. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses and closes #119 by normalizing the JSON-LD structure in the data-quality example:\n\n- Single top-level @context (use published DPROD context)\n- Move multiple nodes into @graph\n- Consistent use of JSON-LD keywords (@id, @type)\n\nThis should satisfy RIOT validation and align examples with the fixed context model from #93 / PR #135.