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

Config : read the prefixes from ones declared in the SHACL file #587

Open
tfrancart opened this issue Apr 30, 2024 · 0 comments
Open

Config : read the prefixes from ones declared in the SHACL file #587

tfrancart opened this issue Apr 30, 2024 · 0 comments
Labels
kind: Enhancement 📈 New feature or request priority: Low ⬇️ Low-priority issue what: Configuration Related to how the component is configured

Comments

@tfrancart
Copy link
Contributor

It seems N3Store loses the prefixes once the file is parsed.
We could try to obtain them through a regex, but that's a hack.
The prefixes would be automatically added in the generated SPARQL query
We could read the prefixes declared in SHACL:

<https://exemple.fr/MyOntology> a owl:Ontology;
  rdfs:label "My Ontology"@en;
  sh:declare [
    sh:prefix "owl" ;
    sh:namespace "http://www.w3.org/2002/07/owl#"^^xsd:anyURI ;
  ] ;
  sh:declare [
    sh:prefix "rdf" ;
    sh:namespace "http://www.w3.org/1999/02/22-rdf-syntax-ns#"^^xsd:anyURI ;
  ] ;
  sh:declare [
    sh:prefix "rdfs" ;
    sh:namespace "http://www.w3.org/2000/01/rdf-schema#"^^xsd:anyURI ;
  ] ;
  sh:declare [
    sh:prefix "sh" ;
    sh:namespace "http://www.w3.org/ns/shacl#"^^xsd:anyURI ;
  ] ;
  sh:declare [
    sh:prefix "skos" ;
    sh:namespace "http://www.w3.org/2004/02/skos/core#"^^xsd:anyURI ;
  ] ;
@tfrancart tfrancart added kind: Enhancement 📈 New feature or request priority: Low ⬇️ Low-priority issue what: Configuration Related to how the component is configured labels Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind: Enhancement 📈 New feature or request priority: Low ⬇️ Low-priority issue what: Configuration Related to how the component is configured
Projects
None yet
Development

No branches or pull requests

1 participant