On 10 Feb 2016, at 15:31, Gabriele Morlini <[email protected]> wrote: > > Thanks for the timely answer, but my question is why the fact "property p is > just as 'possible' for I1 as for I0" have been showed, in the Domain tab, > before any reasoner is started from GUI. > I'm expecting that the "possibility" could be translate in an axioms that > could by added in the ontology, as any other inference, but this could not be > done.
These properties appear in the UI because users find that useful. When you use the Instances tab it pre-fills the UI with possible properties to populate. If you do not put a value in that property for the instance there is no connection between the instance and those properties other than in the UI, so there is no downside really. > > I'm asking Consequently how TopBraid was able to done this > "inference"(Reasoner? Spin? Other?), and why this inference is not showed as > any other inference. I hope I’ve explained that this is just a nice little feature in the UI for the Instances Tab. There is some bit of RDFS inference happening in the background to support that UI feature, but it’s just a kind of UI helper. Also note that in the SPARQL Tab you can tell it to run those inferences first or not before running the query - it’s up to you to control the behaviour. However, in the SPARQL Tab if you say inference On it does not save them anywhere. > My dupt is that inference is not compliant with other inference or simply in > TopBraid lack of the possibility of add this axioms to ontology. Composer is not going to change your ontology or dataset without you explicitly telling it to do so. That would shock most users. Users decide whether to persist inferred triples or not. > > My scope is use TobBraid as "reasoner" and generator of more complete > ontology as base for futher investigation. Then you should actually Run a reasoner to infer the triples and save them somewhere e.g. back into the ontology graph itself or in the instance dataset graph as appropriate. Cheers, David > > On Wednesday, February 10, 2016 at 10:59:23 AM UTC+1, David Price wrote: > Hi, > > You’ve stated this : > > A rdf:type owl:Class > B rdf:type owl:Class > B rdfs:subClassOf A > p rdf:type owl:DatatypeProperty > p rdfs:domain A > > and now let’s add individuals: > > I0 rdf:type A > I1 rdf:type B > > an OWL reasoner will infer > > I1 rdf:type A > > so if you look at the inferences, I1 is an member of A just like I0 is a > member of A and therefore the property p is just as “possible” for I1 as for > I0. You do not need the concept of “inheritance” in this picture at all, it’s > “subset" that is in play (B being a subset of A … i.e. ALL members of B are > members of A). Anything you say wrt members of A and their > properties/restrictions is applicable to members of B in the same way because > members of B ARE members of A via inference. > > Cheers, > David > > UK +44 7788 561308 > US +1 336 283 0606 > > > > >> On 10 Feb 2016, at 09:17, Gabriele Morlini <[email protected] >> <javascript:>> wrote: >> >> Hi, >> >> When I define a property "P" with a domain Class "A", TopBraid automatically >> add property as "inferred" in the domain of all class and subclass of "A". >> >> I have already read the previous post: >> https://groups.google.com/forum/#!topic/topbraid-users/90SizV7nmWM >> <https://groups.google.com/forum/#!topic/topbraid-users/90SizV7nmWM> >> https://groups.google.com/forum/#!topic/topbraid-users/90SizV7nmWM >> <https://groups.google.com/forum/#!topic/topbraid-users/90SizV7nmWM> >> where they debeate of the correctness and semantics of the >> inference/Inheritance in OWL/RDFS. >> >> My question is How it's done by TobBraid? >> With a SPIN rule? with a reasoner? other? >> >> Thanks in advance >> Gabriele >> >> -- >> You received this message because you are subscribed to the Google Group >> "TopBraid Suite Users", the topics of which include Enterprise Vocabulary >> Network (EVN), Reference Data Manager (RDM), TopBraid Composer, TopBraid >> Live, TopBraid Insight, SPARQLMotion, SPARQL Web Pages and SPIN. >> To post to this group, send email to [email protected] >> <javascript:> >> --- >> 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] <javascript:>. >> For more options, visit https://groups.google.com/d/optout >> <https://groups.google.com/d/optout>. > > > -- > You received this message because you are subscribed to the Google Group > "TopBraid Suite Users", the topics of which include Enterprise Vocabulary > Network (EVN), Reference Data Manager (RDM), TopBraid Composer, TopBraid > Live, TopBraid Insight, SPARQLMotion, SPARQL Web Pages and SPIN. > To post to this group, send email to [email protected] > --- > 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 > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary Network (EVN), Reference Data Manager (RDM), TopBraid Composer, TopBraid Live, TopBraid Insight, SPARQLMotion, SPARQL Web Pages and SPIN. To post to this group, send email to [email protected] --- 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.
