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

SHACL support #200

Open
rmfranken opened this issue Sep 7, 2023 · 1 comment
Open

SHACL support #200

rmfranken opened this issue Sep 7, 2023 · 1 comment

Comments

@rmfranken
Copy link

Dear webVowl team, I'm hoping to find a solution to my problem with your tool. I use SHACL shapes to build my ontology, as this is the way to go for validating RDF graphs. This means I don't include any "informational" properties like rdfs:range, rdfs:domain, rdfs:datatype, rdfs:literal or cardinality constraints in owl or rdfs. Everything has "meaningful" SHACL equivalents - sh:minCount, sh:maxCount for cardinalities, sh:datatype for datatypes, sh:class, sh:property and more - meaning I can validate graphs against my SHACL ontology to see if the instance data matches the ontology schema. See https://spinrdf.org/shacl-and-owl.html for more information.

Is it possible to alter the dictionary which maps a relation to a certain visual element in WebVOWL? Even something simple like the labels and definitions of objects and properties may be defined using different annotative properties like skos:prefLabel, skos:definition or sh:name, sh:description (not referring to owl:annotationProperty here).

if this is not possible yet - is it a feature that would be worth adding in order to support more types of ontologies?

kind regards,
Robin

@vitalis-wiens
Copy link
Contributor

Dear Robin,

SHACL is currently not supported by webVOWL

I would see here two aspects for improvement

  1. OWL2VOWL our backend which translates the owl ontology into a format which is understood by webvowl needs to accommodate for this request
  2. There is currently no visual definition for SHACL shapes therefor the VOWL language needs to define these and then the frontend code webVOWL needs to render them accordingly

I hope this gives you a short overview of implications for this feature

Kind Regards, Vitalis

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants