To: | "[ontolog-forum]" <ontolog-forum@xxxxxxxxxxxxxxxx> |
---|---|
From: | Ali Hashemi <ali.hashemi+ontolog@xxxxxxxxxxx> |
Date: | Sun, 15 Feb 2009 23:16:14 -0500 |
Message-id: | <5ab1dc970902152016oed271cene0a37b7395ee4100@xxxxxxxxxxxxxx> |
Hello all, thanks to those who took the time to respond! @ Alex - As an exercise the past few weeks, I've been trying to formalize semi-formal natural language claims made by various people. One such (concrete) example, is indeed Hilbert's geometry axioms, where he claims to only commit to points, lines and planes; yet entities such as linesegments, rays, space etc. seem to pop-up. For this particular example, I'm uncertain whether creating a thing called "linesegment" changes in any substantive way Hilbert's ontology.
The dilemma is exactly as you describe it, and while I am asking the question in general, it is motivated by several concrete examples. Alex wrote:
in general if I have chance to define something (entity) using relation, then I define it. Why do you opt for relations over a specifying a new entity (or are you doing both)? What's the reasoning behind your choice?
I used the word "implicit," because, as in the example, such a relation (in my mind) points to the existence of some unnamed entity (thing that we can quantify over).
@ Pat - Thanks for your response, this is along the lines of what i'm looking for. Pat wrote:
Yes, exactly. Though in CL, there is less to choose between them as the first is also committing to the existence of the linesegment relation itself. This is true, and in CL we can quantify over named relations, so perhaps this distinction is academic, though in TFOL such a distinction has practical implications. Additionally, this is a grey area of ontologies for me. For example, if you say
(forall (x) (entity x) <---> S (some sentences) it's almost as though you are naming a set of axioms in the relation. It seems a skip/hop away from 2nd or higher order logic, yet it clearly isn't. In terms of mimicking natural language, and convenience in terms of referring to S in such a way, such a construction seems tremendously useful. Does it however introduce problems in reasoning time / complexity? Pat wrote: And what does OVER commitment mean, here? Meaning I have now introduced some new thing that i need to account for explicitly - might it have some unintended consequences? For example, if I try to convert a relation to a function, if I have it undefined in some places, it would introduce an inconsistency to my ontology. Along the same lines, I'm trying to figure out whether this choice actually has practical ramifications beyond stylistic choices; it's a relatively opaque question for me at the moment.
Pat wrote: Philosophers are often leery of admitting to the existence of things because they have a philosophical agenda to reduce everything to some small subclass of entities (for example, nominalists like Chris Partridge tend to think that only actual concrete physical things are really real), but when writing ontologies for practical use, we should not be guided by merely philosophical agendas. Aside from some aesthetic appeal to simplicity / elegance is there a more grounded motivation? I imagine there are stronger reasons than simply a desire for a small subclass of entities. My initial (naive) impression is that a universe that has fewer things defined, is pragmatically, easier to reason with. Yet defining a relation would seem to introduce just as much complexity as a new entity which captures the same restrictions on things that already exist in the U of D.
Pat wrote: I see very few practical problems arising from having ontologies commit to the existence of things fairly freely, and having the relevant things in ones ontology tends to make it a lot easier to say what you need to say. Would you care to elaborate what these practical problems might be? @Ravi - I'm not entirely sure what you mean, can you expand a bit?
I should clarify, when I wrote "behaviour", i mean to say when you write (forall (x) (entity x) <--> S , you are defining the "behaviour" of entity X. Choosing whether you do so explicitly by naming some new thing X, or implicitly, by defining relations which capture S, is the crux of the question here.
I would like to catalog the benefits / disadvantages of each approach. I intuitively prefer naming new things (both for convenience and explicitness), yet how much are we changing an ontology by adding these new constructs?
Cheers, Ali On Sun, Feb 15, 2009 at 6:14 PM, Ravi Sharma <ravisharma@xxxxxxxxxxx> wrote:
-- (•`'·.¸(`'·.¸(•)¸.·'´)¸.·'´•) .,., _________________________________________________________________ Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/ Config Subscr: http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/ Unsubscribe: mailto:ontolog-forum-leave@xxxxxxxxxxxxxxxx Shared Files: http://ontolog.cim3.net/file/ Community Wiki: http://ontolog.cim3.net/wiki/ To join: http://ontolog.cim3.net/cgi-bin/wiki.pl?WikiHomePage#nid1J To Post: mailto:ontolog-forum@xxxxxxxxxxxxxxxx (01) |
Previous by Date: | Re: [ontolog-forum] Ur-Elements, paola . dimaio |
---|---|
Next by Date: | Re: [ontolog-forum] a skill of definition - "river", Ali Hashemi |
Previous by Thread: | Re: [ontolog-forum] Relevance of Aristotelian Logic, Ravi Sharma |
Next by Thread: | Re: [ontolog-forum] Relevance of Aristotelian Logic, Pat Hayes |
Indexes: | [Date] [Thread] [Top] [All Lists] |