Re: SUO: Axiomatizing lower level WordNet terms
I was very pleased to see the WordNet-SUMO work in progress and
progressing well.
I am now a bit lost though:
WN-food linked to SUMO Artifact ?
WN-rescue linked to SUMO Removing?
So a banana is "A &%CorpuscularObject that is the product of an
&%IntentionalProcess." ?
perhaps the ( subclass
<http://ontology.teknowledge.com:8080/rsigma/SKB.jsp?req=SC&skb=SUMO&id=37>
Cooking
<http://ontology.teknowledge.com:8080/rsigma/SKB.jsp?req=SC&skb=SUMO&id=672>
Making
<http://ontology.teknowledge.com:8080/rsigma/SKB.jsp?req=SC&skb=SUMO&id=665>
) under artifact confuses here, in that not all food is cooked!
And rescue is "The &%Class of &%Processes where something is taken away
from a location. Note that the thing removed and the location are
specified with the &%CaseRoles &%patient and &%origin, respectively."
Can we specify that the location (a SUMO Object) can be abstract
(they were rescued from danger)? In fact, the abstract nature of the
object being a threat seems to be definitional for rescue. You can't
be rescued from something that is not a threat. An Object just
can't *be* a threat, it has to be considered as such by some one,
which makes it more of a semiotic object than just a member
of
"Corresponds roughly to the class of ordinary physical objects. An
&%Object is thought of as continuing through time, but at any particular
time is all there is at that time, in contrast to something that is
thought of as being divided into stages (contrast &%Process). Examples
include normal physical objects, geographical regions, and locations of
&%Processes.
And that was just the first two... how about the next 30,000...... I'll
have to
read more on your method though; a first step is certainly better than none.
This is going to be a wonderful job creation scheme.
Good fun though,
John B.