-
Notifications
You must be signed in to change notification settings - Fork 29
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
Unused @context
reference policy
#615
Comments
I think it’s akin to declaring prefixes which are unused, which is also a common practice. I don’t consider it a bug, although it might be nice to get some feedback that there a contexts which are unused, although this could be complicated due to the way in which contexts interact. |
I'm not sure it's an alike case, unused prefixes and unused +1 to get feedback |
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?The text was updated successfully, but these errors were encountered: