Search Mailing List Archives
[p4-feedback] Why max operator doesnt work when min operator works
name1390453675 at mail.com
Thu Nov 14 15:57:21 PST 2013
The same principle, open world: OWL ontologies require more explicit (unambiguous) information than you used to supply for old-fashioned databases. A consequence and an advantage is: OWL ontologies cope better with incomplete and incremental information than databases do.
For example, in your ontology, you have Alien title, and you specify: Alien hasYearRelease 1979. Do you expect Alien to be classified under LessThan10YearsCreationTitles after that? No, it is not enough: How would a reasoner know that Alien has no more release years? You need providing more information. For example, if you specify that Alien has type (hasYearRelease max 1 Literal), then a reasoner will classify Alien under LessThan10YearsCreationTitles.
----- Original Message -----
Sent: 11/14/13 09:52 PM
To: p4-feedback at lists.stanford.edu
Subject: Re: [p4-feedback] Why max operator doesnt work when min operator works
and what about the min & max operator? Why does max operator doesn't work? Could you please suggest how to edit ontology to make max operator work? -- View this message in context: http://protege-project.136.n4.nabble.com/Why-max-operator-doesnt-work-when-min-operator-works-tp4659458p4659476.html Sent from the Protege-OWL 4.x Support mailing list archive at Nabble.com. _______________________________________________ p4-feedback mailing list p4-feedback at lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/p4-feedback
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the p4-feedback