- From: <tim.glover@bt.com>
- Date: Fri, 31 Jan 2014 16:21:16 +0000
- To: <tim@mlhim.org>, <aidan.hogan@deri.org>
- CC: <pavel.klinov@uni-ulm.de>, <franconi@inf.unibz.it>, <paul.w.warren@btinternet.com>, <dave.e.reynolds@gmail.com>, <semantic-web@w3.org>
- Message-ID: <ABEDE2E0F379C44F9A8A046505B360CF4F0B3B624C@EMV63-UKRD.domain1.systemhost.net>
Hi, (Also speaking from the sidelines, so apologies if this is nonsense). As a software engineer, the striking difference is this. In Java, if a class A has property x, then all objects of that class have property x. If class B extends A, then all objects of class B also have property x. In OWL the logical direction is completely different. In OWL, if property x has domain A, that does NOT mean that all objects of class A have property x. It means that IF an object has property x, it must belong to class A (very roughly speaking - I am aiming for conceptual intuition of the difference here, rather than strict accuracy). IF B is a subclass of A, and IF I can deduce that object b is a B, then it must also be an A. Inheritance in programming languages allows one to deduce properties of an object from a description of a class. In OWL, the idea is to deduce the class of an object from a description of its properties. The OWL specs do not talk about inheritance because inheritance in the usual sense does not apply to OWL. Other people believe that OWL has something to do with inheritance because the terminology of classes and subclasses is the same. But the meaning is quite different. Tim. From: Timothy W. Cook [mailto:tim@mlhim.org] Sent: 31 January 2014 15:41 To: Aidan Hogan Cc: Pavel Klinov; Enrico Franconi; PAUL WARREN; Dave Reynolds; semantic-web@w3.org Subject: Re: Deduced property On Fri, Jan 31, 2014 at 1:12 PM, Aidan Hogan <aidan.hogan@deri.org<mailto:aidan.hogan@deri.org>> wrote: +1 ... and yep, I still maintain my original point that it is *not* helpful to talk about OWL subsumption using phrases like inheritance. :) Speaking from the sidelines, but with a lot of experience in dealing with people from multiple domains and many perspectives. It may not be helpful to talk about it in the specs. But anytime you see that there is confusion over an topic from a segment of people that that is interested in and has a possible use for what you are producing/teaching. Then you would benefit from talking about it in clarifying, informal documents; in a context that they are familiar with using. In this case, 'inheritance' is a word used and understood by computer scientists. If you use that as a starting point and then say what is different in 'OWL subsumption'; you will be a lot more successful in making your points. HTH, Tim -- MLHIM VIP Signup: http://goo.gl/22B0U ============================================ Timothy Cook, MSc +55 21 94711995 MLHIM http://www.mlhim.org Like Us on FB: https://www.facebook.com/mlhim2 Circle us on G+: http://goo.gl/44EV5 Google Scholar: http://goo.gl/MMZ1o LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook
Received on Friday, 31 January 2014 16:22:12 UTC