Dr. ir. H.M. (Michel) Böhms
Senior Data Scientist
T +31888663107
M +31630381220
E [email protected] <mailto:[email protected]>
Location
<https://www.google.com/maps/place/TNO+-+Locatie+Delft+-+Stieltjesweg/@52.000788,4.3745183,17z/data=%213m1%214b1%214m5%213m4%211s0x47c5b58c52869997:0x56681566be3b8c88%218m2%213d52.000788%214d4.376707>
<http://www.tno.nl/>
This message may contain information that is not intended for you. If
you are not the addressee or if this message was sent to you by
mistake, you are requested to inform the sender and delete the
message. TNO accepts no liability for the content of this e-mail, for
the manner in which you use it and for damage of any kind resulting
from the risks inherent to the electronic transmission of messages.
*From:*[email protected]
[mailto:[email protected]] *On Behalf Of *Holger Knublauch
*Sent:* donderdag 26 oktober 2017 09:30
*To:* [email protected]
*Subject:* Re: [topbraid-users] shacl rule inference
The Shapes, Validation, and Targets views will only show up when you
open a file that imports the SHACL namespace (which happens if you
import DASH).
We have seen the "Widget is disposed error" as well in all kinds of
contexts, and haven't found a reliable source of this effect yet. It
could potentially be a general Eclipse bug, because there is nothing
TopBraid-specific in the stack trace. If someone has a reliable
recipe, please send it along.
Holger
On 26/10/2017 17:15, Bohms, H.M. (Michel) wrote:
All clear, thx
Wrt previous post:
After restart (and load file without dash import), the shacl tab
is gone…guess this is not according below right?
Dr. ir. H.M. (Michel) Böhms
Senior Data Scientist
T +31888663107
M +31630381220
E [email protected] <mailto:[email protected]>
Location
<https://www.google.com/maps/place/TNO+-+Locatie+Delft+-+Stieltjesweg/@52.000788,4.3745183,17z/data=%213m1%214b1%214m5%213m4%211s0x47c5b58c52869997:0x56681566be3b8c88%218m2%213d52.000788%214d4.376707>
<http://www.tno.nl/>
This message may contain information that is not intended for you.
If you are not the addressee or if this message was sent to you by
mistake, you are requested to inform the sender and delete the
message. TNO accepts no liability for the content of this e-mail,
for the manner in which you use it and for damage of any kind
resulting from the risks inherent to the electronic transmission
of messages.
*From:*[email protected]
<mailto:[email protected]>
[mailto:[email protected]] *On Behalf Of *Holger
Knublauch
*Sent:* donderdag 26 oktober 2017 09:10
*To:* [email protected]
<mailto:[email protected]>
*Subject:* Re: [topbraid-users] shacl rule inference
So just to be clear on this (for anyone reading).
To use SHACL, people typically import the SHACL namespace, but
it's technically not needed. Having the class and property
definitions around does make it easier for tools, for example to
make suggestions and to have on the fly documentation.
TopBraid also suggests and automatically owl:imports the DASH
namespace, which adding standards-compliant triples to the SHACL
namespace, including executable SPARQL and JavaScript definitions
of most SHACL Core elements. DASH also defines some other
generally useful extensions that should work fine on any
SHACL-compliant system. So there is usually no harm in keeping it
owl:imported. To read more about the DASH namespace, see
http://datashapes.org/
TopBraid also suggests and indirectly owl:imports another
namespace called TOSH, which includes things that cannot be
expressed with "standard SHACL" alone, and require some extensions
such as additional SPARQL functions. All the TOSH features are
supported by TopBraid products but may also be supported by other
implementations in the future. Examples of TOSH features are
properties such tosh:editWidget that are useful to state specific
UI widgets for form building. Within TopBraid, the DASH namespace
automatically owl:imports TOSH, while the official (external)
version of DASH doesn't and thus doesn't carry any ballast.
Since the TopBraid SHACL validation engine relies on SPARQL for
most of its work, and the DASH + TOSH namespaces contain all
machine-readable SPARQL queries to back the SHACL constraint
components, they are needed at run-time and are automatically
added if needed.
HTH
Holger
On 26/10/2017 16:55, Bohms, H.M. (Michel) wrote:
Ahhh, ok perfect!
With the earlier issue you asked whether I included the dash
import. It seemed to solve the issue then which was after all
solved by other changes I guess.
Because I did not really use dash vocab I thought it was
needed anyway for some other internal reason.
Retried myself and indeed not needed.
Thx.
Dr. ir. H.M. (Michel) Böhms
Senior Data Scientist
T +31888663107
M +31630381220
E [email protected] <mailto:[email protected]>
Location
<https://www.google.com/maps/place/TNO+-+Locatie+Delft+-+Stieltjesweg/@52.000788,4.3745183,17z/data=%213m1%214b1%214m5%213m4%211s0x47c5b58c52869997:0x56681566be3b8c88%218m2%213d52.000788%214d4.376707>
<http://www.tno.nl/>
This message may contain information that is not intended for
you. If you are not the addressee or if this message was sent
to you by mistake, you are requested to inform the sender and
delete the message. TNO accepts no liability for the content
of this e-mail, for the manner in which you use it and for
damage of any kind resulting from the risks inherent to the
electronic transmission of messages.
*From:*[email protected]
<mailto:[email protected]>
[mailto:[email protected]] *On Behalf Of *Holger
Knublauch
*Sent:* donderdag 26 oktober 2017 02:38
*To:* [email protected]
<mailto:[email protected]>
*Subject:* Re: [topbraid-users] shacl rule inference
On 25/10/2017 17:26, Bohms, H.M. (Michel) wrote:
Ok, I must be confused with another tool,
final one on dash import…could that somehow be implicit in
case it’s not used explicitly (as in the example)?
Could you help me reproduce this? I tried your example file,
removing the owl:import statement. Running inferences still
works for me. The API has code to automatically add the
missing graph, which should trigger.
Holger
Dr. ir. H.M. (Michel) Böhms
Senior Data Scientist
T +31888663107
M +31630381220
E [email protected] <mailto:[email protected]>
Location
<https://www.google.com/maps/place/TNO+-+Locatie+Delft+-+Stieltjesweg/@52.000788,4.3745183,17z/data=%213m1%214b1%214m5%213m4%211s0x47c5b58c52869997:0x56681566be3b8c88%218m2%213d52.000788%214d4.376707>
<http://www.tno.nl/>
This message may contain information that is not intended
for you. If you are not the addressee or if this message
was sent to you by mistake, you are requested to inform
the sender and delete the message. TNO accepts no
liability for the content of this e-mail, for the manner
in which you use it and for damage of any kind resulting
from the risks inherent to the electronic transmission of
messages.
*From:*[email protected]
<mailto:[email protected]>
[mailto:[email protected]] *On Behalf Of
*Holger Knublauch
*Sent:* woensdag 25 oktober 2017 09:13
*To:* [email protected]
<mailto:[email protected]>
*Subject:* Re: [topbraid-users] shacl rule inference
On 25/10/2017 17:08, Bohms, H.M. (Michel) wrote:
Ok, thx!
Works as expected now.
Gr Michel
Ps
Small one: I noticed that (rdfs) superclass instance
inferencing is ‘automatic’. Was that always the case?
Or is that because it was only not in owl where you
needed explicit inferencing? (anyway I like it 😊)
There have been no changes to these "trivial" inferences
for years, as far as I can remember.
Holger
Dr. ir. H.M. (Michel) Böhms
Senior Data Scientist
T +31888663107
M +31630381220
E [email protected] <mailto:[email protected]>
Location
<https://www.google.com/maps/place/TNO+-+Locatie+Delft+-+Stieltjesweg/@52.000788,4.3745183,17z/data=%213m1%214b1%214m5%213m4%211s0x47c5b58c52869997:0x56681566be3b8c88%218m2%213d52.000788%214d4.376707>
<http://www.tno.nl/>
This message may contain information that is not
intended for you. If you are not the addressee or if
this message was sent to you by mistake, you are
requested to inform the sender and delete the message.
TNO accepts no liability for the content of this
e-mail, for the manner in which you use it and for
damage of any kind resulting from the risks inherent
to the electronic transmission of messages.
*From:*[email protected]
<mailto:[email protected]>
[mailto:[email protected]] *On Behalf Of
*Holger Knublauch
*Sent:* woensdag 25 oktober 2017 01:38
*To:* [email protected]
<mailto:[email protected]>
*Subject:* Re: [topbraid-users] shacl rule inference
Hi Michel,
see the fixed file attached. Property shapes always
require sh:path, so you needed an additional blank node:
ruletry:PropertyShape_1
rdf:type sh:PropertyShape ;
sh:path [
sh:inversePath (
ruletry:hasRadiator
ruletry:size
) ;
] ;
sh:hasValue "large" .
To enter such things, you can use the SPARQL path
surface syntax in TBC at sh:path. I just noticed a bug
in the beta here - there should be a (...) around the
path expression in this case. I'll see if this can be
fixed in time for the final release.
HTH
Holger
On 25/10/2017 7:45, Bohms, H.M. (Michel) wrote:
Hi Holger
Hereby slightly updated simple example.
(right name spaces/imports/domains/ranges now)
Still no inference as expected (a related
MyRadiator with size being “big”).
I must still be doing something wrong with the
inversePath I guess….
(shacl warns me of a missing sh:path so I guess I
need a path INVOLVING an inversePath iso an
inversePath only?)
Thx again, Michel
Dr. ir. H.M. (Michel) Böhms
Senior Data Scientist
T +31888663107
M +31630381220
E [email protected] <mailto:[email protected]>
Location
<https://www.google.com/maps/place/TNO+-+Locatie+Delft+-+Stieltjesweg/@52.000788,4.3745183,17z/data=%213m1%214b1%214m5%213m4%211s0x47c5b58c52869997:0x56681566be3b8c88%218m2%213d52.000788%214d4.376707>
<http://www.tno.nl/>
This message may contain information that is not
intended for you. If you are not the addressee or
if this message was sent to you by mistake, you
are requested to inform the sender and delete the
message. TNO accepts no liability for the content
of this e-mail, for the manner in which you use it
and for damage of any kind resulting from the
risks inherent to the electronic transmission of
messages.
--
You received this message because you are
subscribed to the Google Groups "TopBraid Suite
Users" group.
To unsubscribe from this group and stop receiving
emails from it, send an email to
[email protected]
<mailto:[email protected]>.
For more options, visit
https://groups.google.com/d/optout.
--
You received this message because you are subscribed
to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving
emails from it, send an email to
[email protected]
<mailto:[email protected]>.
For more options, visit
https://groups.google.com/d/optout.
--
You received this message because you are subscribed
to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving
emails from it, send an email to
[email protected]
<mailto:[email protected]>.
For more options, visit
https://groups.google.com/d/optout.
--
You received this message because you are subscribed to
the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails
from it, send an email to
[email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to
the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails
from it, send an email to
[email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the
Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from
it, send an email to
[email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the
Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from
it, send an email to
[email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
