Support for sh:sparql and sh:severity in shacl constraints #4258
-
|
I am learning shacl and is trying the examples from https://www.w3.org/TR/2017/REC-shacl-20170720/. When I try example "5.1 An Example SPARQL-based Constraint" it doesn't report a validation failure. I think it is because sh:sparql and related instructions, e.g. sh:SPARQLConstraint and sh:select are not implemented. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 3 replies
-
|
Here is a list of our supported SHACL features: https://rdf4j.org/documentation/programming/shacl/#supported-shacl-features We have both SPARQL based validation and support for severity in our plans. The current SHACL implementation is geared towards users who need to add constraints to a database and have the validation engine reject any transactions that would make the data in the database invalid. We use a novel approach to analyse the changes in a transaction to optimise the validation approach. This allows us to quickly validate a small change regardless of if you currently have a million or a billion triples in your database. |
Beta Was this translation helpful? Give feedback.
-
|
Hello Håvard
Do you know when SPARQL based validation and support for severity will be available?
In case it is far in future I will investigate other solutions.
Many thanks for responding / Lars-Ola
Från: Håvard M. Ottestad ***@***.***>
Skickat: den 1 november 2022 09:32
Till: eclipse/rdf4j ***@***.***>
Kopia: Lars-Ola Osterlund ***@***.***>; Author ***@***.***>
Ämne: Re: [eclipse/rdf4j] Support for sh:sparql and sh:severity in shacl constraints (Discussion #4258)
Here is a list of our supported SHACL features: https://rdf4j.org/documentation/programming/shacl/#supported-shacl-features
We have both SPARQL based validation and support for severity in our plans.
The current SHACL implementation is geared towards users who need to add constraints to a database and have the validation engine reject any transactions that would make the data in the database invalid. We use a novel approach to analyse the changes in a transaction to optimise the validation approach. This allows us to quickly validate a small change regardless of if you currently have a million or a billion triples in your database.
—
Reply to this email directly, view it on GitHub <#4258 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AN4NIQ6MRHPRJWP7GGBWNQDWGDIORANCNFSM6AAAAAARS5VBAQ> .
You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AN4NIQZJXQFLSWBUZZDXVYLWGDIORA5CNFSM6AAAAAARS5VBASWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAHVV46.gif> Message ID: ***@***.*** ***@***.***> >
|
Beta Was this translation helpful? Give feedback.
-
|
At the moment we don’t have a specific date in mind. What is your use case and timeframe? |
Beta Was this translation helpful? Give feedback.
-
|
Currently I am investigating how to translate from OCL to SPARQL, see if I can do it with antlr. Will take to the end of this year. Once I have the SPARQL I will embed them in SHACL shapes, hope to begin next year.
Br / Lars-Ola
Från: Håvard M. Ottestad ***@***.***>
Skickat: den 1 november 2022 17:18
Till: eclipse/rdf4j ***@***.***>
Kopia: Lars-Ola Osterlund ***@***.***>; Author ***@***.***>
Ämne: Re: [eclipse/rdf4j] Support for sh:sparql and sh:severity in shacl constraints (Discussion #4258)
At the moment we don’t have a specific date in mind.
What is your use case and timeframe?
—
Reply to this email directly, view it on GitHub <#4258 (reply in thread)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AN4NIQ6RYPTC54J3CXIFJ6DWGE7C3ANCNFSM6AAAAAARS5VBAQ> .
You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AN4NIQ5QBJN3WVCCYXRQYWTWGE7C3A5CNFSM6AAAAAARS5VBASWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAHV5DC.gif> Message ID: ***@***.*** ***@***.***> >
|
Beta Was this translation helpful? Give feedback.
-
|
That sounds interesting. Is it a part of a research project or a thesis? Or maybe a commercial use? Are you going to use SPARQL exclusively or will you be using the other constraint components in SHACL? |
Beta Was this translation helpful? Give feedback.
-
|
I am just a retired guy interested in the topic. I have been working both with SHACL/SPARQL and EMF/OCL. I have a contact at KTH in Sweden and will suggest a paper on the topic if I find a conversion feasible. To convert OCL you will need SHACL for the logic and SPARQL for the model navigation.
Från: Håvard M. Ottestad ***@***.***>
Skickat: den 5 november 2022 09:59
Till: eclipse/rdf4j ***@***.***>
Kopia: Lars-Ola Osterlund ***@***.***>; Author ***@***.***>
Ämne: Re: [eclipse/rdf4j] Support for sh:sparql and sh:severity in shacl constraints (Discussion #4258)
That sounds interesting. Is it a part of a research project or a thesis? Or maybe a commercial use?
Are you going to use SPARQL exclusively or will you be using the other constraint components in SHACL?
—
Reply to this email directly, view it on GitHub <#4258 (reply in thread)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AN4NIQ5XXJLLVB34ARHCOMDWGYOWZANCNFSM6AAAAAARS5VBAQ> .
You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AN4NIQZUYT7HUOZY26YLR4DWGYOWZA5CNFSM6AAAAAARS5VBASWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAHX7CC.gif> Message ID: ***@***.*** ***@***.***> >
|
Beta Was this translation helpful? Give feedback.
-
|
Maybe the SHACL Playground would be helpful during your development: https://shacl-playground.zazuko.com |
Beta Was this translation helpful? Give feedback.
Here is a list of our supported SHACL features: https://rdf4j.org/documentation/programming/shacl/#supported-shacl-features
We have both SPARQL based validation and support for severity in our plans.
The current SHACL implementation is geared towards users who need to add constraints to a database and have the validation engine reject any transactions that would make the data in the database invalid. We use a novel approach to analyse the changes in a transaction to optimise the validation approach. This allows us to quickly validate a small change regardless of if you currently have a million or a billion triples in your database.