I suspect you are correct in that last statement. I didn't realize inline inverse properties were introduced with OWL 2, good to know.
On Thu, Jan 10, 2013 at 4:05 PM, Holger Knublauch <[email protected]>wrote: > On 1/11/2013 9:58, harschware wrote: > >> Also Holger, >> When I use the corrected Turtle in TBC, and I use OWLIM reasoner I get >> the following error: >> > > TBC only includes a rather old version of OWLIM that didn't yet support > OWL 2, and thus also no inline inverse properties. > > > > Reason: >> java.lang.ClassCastException: org.openrdf.model.impl.**BNodeImpl cannot >> be cast to org.openrdf.model.URI >> at org.openrdf.sesame.sailimpl.**OWLIMSchemaRepository$** >> StatementImpl.getPredicate(**OWLIMSchemaRepository.java:**1105) >> at org.topbraid.owlim.sesame.**Sesame2Jena.getTriple(** >> Sesame2Jena.java:79) >> at org.topbraid.owlim.inference.**OWLIM.addTriples(OWLIM.java:**84) >> at org.topbraid.owlim.inference.**SwiftOWLIMInferenceEngine.** >> addTriples(**SwiftOWLIMInferenceEngine.**java:31) >> at org.topbraid.inference.change.**AbstractInferenceChange.** >> runReallyNow(**AbstractInferenceChange.java:**157) >> at org.topbraid.inference.change.**AbstractInferenceChange.** >> runReally(**AbstractInferenceChange.java:**124) >> at org.topbraidcomposer.**inference.change.** >> InferenceChange.access$0(**InferenceChange.java:1) >> at org.topbraidcomposer.**inference.change.**InferenceChange$3.run(** >> InferenceChange.java:90) >> at java.lang.Thread.run(Thread.**java:680) >> >> But, it DOES give me the resultant triple I'm looking for, despite the >> error, namely :Lloyd rdf:type :Uncle. So that tells me at least that the >> restriction class seems to be defined correctly. However when I switch to >> SPIN with OWL 2 RL profile, I do not get the desired inference result. I >> can imagine that perhaps there is not a rule defined in OWL2-RL that would >> infer the new triple, although I would have thought that it does. I'm now >> wondering, are there other OWL 2 profiles available in TBC? >> > > Yes OWL 2 RL does not define a rule for this, but you could try to add it > if you are really interested in this. But in general for any features that > go very deep into OWL 2 DL reasoning, you should look at tools that focus > on OWL 2 DL. At TopQuadrant we frankly haven't seen enough practical or > commercially relevant use cases that would justify further investment into > OWL DL. > > Holger > > > -- > -- You received this message because you are subscribed to the Google > Group "TopBraid Suite Users", the topics of which include Enterprise > Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, > TopBraid Ensemble, SPARQLMotion, SPARQL Web Pages and SPIN. > To post to this group, send email to > topbraid-users@googlegroups.**com <[email protected]> > To unsubscribe from this group, send email to > topbraid-users+unsubscribe@**googlegroups.com<topbraid-users%[email protected]> > For more options, visit this group at > http://groups.google.com/**group/topbraid-users?hl=en<http://groups.google.com/group/topbraid-users?hl=en> > > > -- -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Ensemble, SPARQLMotion, SPARQL Web Pages and SPIN. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en
