Missing inference: show by Protege but ignored by Stardog query.

1 view
Skip to first unread message

teo...@gmail.com

unread,
Dec 17, 2014, 11:46:03 AM12/17/14
to sta...@clarkparsia.com
Hi,

I am writing this question to ask for clarification about a strange behaviour I am experiencing when I perform some basic query on a simple ontology created in Protégé. I must admit I am still pretty new to Sparql/inferences rules, so maybe I am just missing something obvious. I am currently evaluating Stardog usage for a research project, and I am still studying the available books so please fell free to tell me if I simply don't  get how this is supposed to work.

I have defined a simple ontology with Protégé.  As you can see from the above screenshot I just have a parent class ItemTypeA with two subclasses (for now, ignore ItemTypeB).

CategoryA1 is defined as equivalent to "ItemTypeA and (not(IsCategory1 value false))"
CategoryA2 is defined as equivalent to "ItemTypeA and (Not(CategoryA1))"

The property IsCategory1 is marked as functional, so the system knows to expect just one instance of the property on each item.

I add two instances of the base class ItemTypeA, one with "IsCategory1" set true and the other one set to false.
Protégé correctly show inference for the two instances and assign them to the CategoryA1 and CategoryA2 classes as expected. Sparql Query plugin misses the inference - but that seems to be expected as far as I know because that plugin inference support is limited. The OWL2Query tab plugin get the inference right.


Yet, Stardog query seems to not infere the above informations, no mater which reasoning level I set. Do I miss something obvious or is this the expected result?


If needed I can provide a simple usecase, just tell me and I will upload the test ontology I am using if you need to see that in more detail.

Thanks for the support

Héctor Pérez-Urbina

unread,
Dec 17, 2014, 2:56:43 PM12/17/14
to stardog
Hi,

Stardog (roughly) supports the OWL profiles [1]. The equivalent class axioms you have in your ontology are not valid for any of the three OWL profiles.


--
-- --
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+u...@clarkparsia.com
For more options, visit this group at
http://groups.google.com/a/clarkparsia.com/group/stardog?hl=en



--
Best,
Héctor

teo...@gmail.com

unread,
Dec 18, 2014, 6:00:12 AM12/18/14
to sta...@clarkparsia.com, hec...@clarkparsia.com
Thanks Héctor.

Think I get it now. I tried to check my ontology model with the online OWL 2 Validation tool provided by Manchester University (http://mowl-power.cs.man.ac.uk:8080/validator/) and noticed that the kind of relation I was expressing would require the OWL 2 DL profile which isn't yet supported by Stardog (correct me if I am wrong).

Thanks again for your quick support, I would like to ask just one more question. Just to know, does the current Stardog road map include plans for future support of the DL profile? As you may have guessed, I don't really need it at the moment - I was just exploring inference types - so fell free to tell me if there aren't current plans for it.

Héctor Pérez-Urbina

unread,
Dec 18, 2014, 9:14:05 AM12/18/14
to teo...@gmail.com, stardog

We support DL for TBox queries only [1]. We are not planning to support DL for ABox queries. The main reason is that, for the sake of completeness, we might require to load the ABox into memory, which might be infeasible. 


--
Best,
Héctor
Reply all
Reply to author
Forward
0 new messages