Skip to content
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

Report imports for contexts that aren't included in the current RDFLib store #37

Open
mwatts15 opened this issue Dec 23, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@mwatts15
Copy link
Contributor

When saving statements to a Context, it is often the case that we add imports that are defined in another Bundle. When we then try to query against the importing context, then we can, rather confusingly, fail to get expected triples (e.g., lacking rdfs:subClassOf statements -> can't query by super-class). To avoid this problem we should do two things:

  1. When saving a context's imports, check that all imported contexts are either defined in the current RDFLib store or that they import (transitively) a context that is stored in the current RDFLib store.
  2. When creating an owmeta_core.context_store.RDFContextStore, check that any imported contexts are either defined in the current RDFLib store or they import (transitively) a context that is stored in the current RDFLib store.

In either case, a warning should be reported to the developer or user (depending on context and configuration) by using the warnings module indicating which context is missing and which context(s) are declared to import it.

@mwatts15 mwatts15 added the enhancement New feature or request label Dec 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant