1 / 1

Using PSI’s in inferencing (Peter-Paul Kruijsen ~ Morpheus) p.kruijsen@mssm.nl

Mail from pp to larsga (14 march 2005)

valin
Download Presentation

Using PSI’s in inferencing (Peter-Paul Kruijsen ~ Morpheus) p.kruijsen@mssm.nl

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Mail from pp to larsga (14 march 2005) "Is there a possibility to link a PSI to a predicate in an inference rule?" Imagine one topic map that defines a 'brother' association type with 'http://psi.somedomain.org/brother' as PSI, and another topic map that defines only 'parenthood' associations with 'father', 'mother' and 'child' role players. In the second topic map an inference rule can be created: brother($X, $Y) :-parenthood($MOTHER, $FATHER, $X),parenthood($MOTHER, $FATHER, $Y),$X /= $Y,male($X). Could the two concepts of 'brother' be linked via PSI's, in other words, can a PSI be attached to a predicate in an inference rule. I could imagine creating only a 'brother' topic in the topic map with a PSI, and leaving it non-typing, but where does the logic kick in, saying the semantics are to be found in the inference rule. More general question: "can inference rules be placed within a topic map?" Is there any logic in this? Mail from larsga to pp (14 march 2005) Very good question. I've been thinking about the relationship between inference rules and associations for years now without really finding a good way to unify them. I think you are right to want what you describe, but so far we don't have a good way to do this in tolog. I keep thinking about this and hoping to either get it into tolog or, at the very least, getting it right in TMQL. I think that's as much as I can tell you right now. In the end, it could be about ontology mapping, i.e. mapping information between sources that use similar (= not equal) ontologies Compare (various topic maps / ontologies) [john : person = "John"] {john, gender, "Male"} [john : person = "John"] gender-of(john, male) [john : male = "John"] super-sub(person : super, male : sub) Another example (within same topic map) customer-provider(some-provider : provider, morpheus : customer) [p1 : project = “Some project”] project-performance(p1 : project, morpheus : performer) project-towards(p1 : project, some-customer : customer) Dynamic topic typing instance-of($P, composer) :-instance-of($P, person),composed-by($P : composer). Dynamic typing allows notion of interface from Java (Puccini of class person, implements composer) use those inference rules (via PSI) to constraints- opera should be composed by a composer- a project should be lead by an ontopian Requirements PSI's in inference rules tolog statements and inference rule heads with constants (PSI or strings) Use of constants in inference rule head Use of existing association-types in inference rule head Caching of inferred facts Using PSI’s in inferencing (Peter-Paul Kruijsen ~ Morpheus) p.kruijsen@mssm.nl

More Related