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]] *On Behalf Of *Holger Knublauch
*Sent:* woensdag 25 oktober 2017 09:13
*To:* [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].
For more options, visit https://groups.google.com/d/optout.
