Not a valid RDFS axiom

9 views
Skip to first unread message

oltr...@gmail.com

unread,
Dec 7, 2016, 10:46:43 AM12/7/16
to sta...@clarkparsia.com
Hello,
I'm trying to query a modular ontology I created. The ontology (let's call it "A") imports SSN (Sensor Semantic Network), which also imports DUL (Dolce Ultra Light). I first created a db with A, and then added SSN and DUL. The modular framework is correctly visualized when I browse the tree. 
Note A also contains three SWRL rules.
When I try to run query that triggers the rule, setting the reasoner as "ON", I got an Internal Server Error. 
I then tried easier inferences with the reasoner on, but I still get that error.
By opening the log, it seems that the problem depends on DUL, as I get the following warning:
"WARN  2016-12-06 22:39:00,009 [Stardog.Executor-185] com.clarkparsia.blackout.ProfileFilterBase:apply(39): Not a valid RDFS axiom: DisjointClasses(DUL:Object, DUL:Quality) 
"
My questions is: since the reasoner is supposed to manage any OWL sublanguage with modality "SL", why I get an error related to RDFS? I also tried to change the reasoner from "SL" to "DL, but I still get the problem.
I tested the same queries on Protégé, and I don't get the error.
Thanks much for any useful information,
Alessandro
P.S.: I'm using Stardog community. 

Zachary Whitley

unread,
Dec 7, 2016, 11:06:37 AM12/7/16
to Stardog
This doesn't address your entire question or may not even be related since you said that you can visualize it correctly but I bring it up just because you mentioned it. Stardog does not follow owl:imports automatically and they need to be loaded manually http://docs.stardog.com/#_known_issues



--
-- --
You received this message because you are subscribed to the C&P "Stardog" group.
To post to this group, send email to sta...@clarkparsia.com
To unsubscribe from this group, send email to
stardog+unsubscribe@clarkparsia.com
For more options, visit this group at
http://groups.google.com/a/clarkparsia.com/group/stardog?hl=en
---
You received this message because you are subscribed to the Google Groups "Stardog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to stardog+unsubscribe@clarkparsia.com.

Zachary Whitley

unread,
Dec 7, 2016, 11:20:50 AM12/7/16
to Stardog
What version of Stardog are you running? Can you send enough of the ontology and a query to trigger the behavior? (I don't know from your description if that would include your ontology or just DUL)

Alessandro Oltramari

unread,
Dec 7, 2016, 11:21:23 AM12/7/16
to Stardog
I actually noticed that, and I added them manually. 

Alessandro Oltramari

unread,
Dec 7, 2016, 11:21:23 AM12/7/16
to Stardog
Initially I didn't know that, then after reading the documentation I added them manually and it worked.


On Wednesday, December 7, 2016 at 11:06:37 AM UTC-5, Zachary Whitley wrote:
This doesn't address your entire question or may not even be related since you said that you can visualize it correctly but I bring it up just because you mentioned it. Stardog does not follow owl:imports automatically and they need to be loaded manually http://docs.stardog.com/#_known_issues


On Wed, Dec 7, 2016 at 10:46 AM, <oltr...@gmail.com> wrote:
Hello,
I'm trying to query a modular ontology I created. The ontology (let's call it "A") imports SSN (Sensor Semantic Network), which also imports DUL (Dolce Ultra Light). I first created a db with A, and then added SSN and DUL. The modular framework is correctly visualized when I browse the tree. 
Note A also contains three SWRL rules.
When I try to run query that triggers the rule, setting the reasoner as "ON", I got an Internal Server Error. 
I then tried easier inferences with the reasoner on, but I still get that error.
By opening the log, it seems that the problem depends on DUL, as I get the following warning:
"WARN  2016-12-06 22:39:00,009 [Stardog.Executor-185] com.clarkparsia.blackout.ProfileFilterBase:apply(39): Not a valid RDFS axiom: DisjointClasses(DUL:Object, DUL:Quality) 
"
My questions is: since the reasoner is supposed to manage any OWL sublanguage with modality "SL", why I get an error related to RDFS? I also tried to change the reasoner from "SL" to "DL, but I still get the problem.
I tested the same queries on Protégé, and I don't get the error.
Thanks much for any useful information,
Alessandro
P.S.: I'm using Stardog community. 

--
-- --
You received this message because you are subscribed to the C&P "Stardog" group.
To post to this group, send email to sta...@clarkparsia.com
To unsubscribe from this group, send email to

For more options, visit this group at
http://groups.google.com/a/clarkparsia.com/group/stardog?hl=en
---
You received this message because you are subscribed to the Google Groups "Stardog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to stardog+u...@clarkparsia.com.

Evren Sirin

unread,
Dec 7, 2016, 11:24:31 AM12/7/16
to Stardog
If there is an error or a timeout during reasoning the reasoning level
automatically be set to the lowest level which is RDFS. There must be
another error message before those warnings you see.

Best,
Evren

Alessandro Oltramari

unread,
Dec 7, 2016, 11:48:55 AM12/7/16
to Stardog
Here's what I see in the log before the warnings:

ERROR 2016-12-07 11:42:23,128 [Stardog.Executor-0] com.complexible.common.protocols.server.rpc.ServerHandler:exceptionCaught(413): exceptionCaughtServerHandler
com.complexible.stardog.server.UnknownDatabaseException: Database 'watchdog' does not exist.
at com.complexible.stardog.server.UnknownDatabaseException.create(UnknownDatabaseException.java:28) ~[stardog-core-shared-4.2.jar:?]
at com.complexible.stardog.protocols.http.annex.WebConsole.handleMessage(WebConsole.java:86) ~[stardog-webconsole-annex-4.2.jar:?]
at com.complexible.common.protocols.server.rpc.ServerHandler.lambda$handleMessage$1(ServerHandler.java:336) ~[stardog-protocols-api-server-4.2.jar:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_101]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_101]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_101]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_101]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_101]

Alessandro Oltramari

unread,
Dec 8, 2016, 10:18:40 AM12/8/16
to Stardog
As far as I understood from other posts, the error about watchdog is linked to the High Availability Cluster. Is it then related to the fact that I'm using the "Community" version of Stardog? 


On Wednesday, December 7, 2016 at 10:46:43 AM UTC-5, Alessandro Oltramari wrote:

Michael Grove

unread,
Dec 8, 2016, 10:23:40 AM12/8/16
to stardog
Correct, neither watchdog or the cluster is part of the community edition.

Cheers,

Mike 

--
-- --
You received this message because you are subscribed to the C&P "Stardog" group.
To post to this group, send email to sta...@clarkparsia.com
To unsubscribe from this group, send email to
Reply all
Reply to author
Forward
0 new messages