Unused `@context` reference policy
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 106
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I've noticed real world examples of JSON-LD documents declaring an array of context URIs from which some of those contexts are not effectively applicable, the terms are not present in the compacted JSON-LD.
This is probably the result of blindly setting the @context URI array to all "variations" of a document.
Extending the compaction algorithm of a new policy on how to proceed unused contexts (Warn|Drop|Keep)? could help with documents generated from RDF.
Does there exist consensus on unused @context declared as dereferenceable URIs? A bad practice or OK?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the compaction algorithm and the JSON-LD documents described in the issue, focusing on unused @context URI arrays. Determine whether the project has consensus on Warn, Drop, or Keep behavior; done requires a decided policy for unused contexts and agreement on the resulting specification change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100