Friday, September 10, 2004

a practical problem in modern computational epistemology

To me the idea that humans represent knowledge as stories is one of the more compelling arguments for the need to have rich knowledge representations like those used by Cyc. Simpler representations simply lack the power to express the variety of content and structures that stories contain -- situations, places, times, objects, events, beliefs, goals, emotions, and so forth.

That said, I am dubious of the proliferation of symbol names that seems to be the product of most ontological approaches to AI. The problem is that it is difficult to decide when to stop. Pat Hayes once recounted to me a story about a group of ontological engineers arguing about whether a painting that was hanging on the wall was “in" the room--but then an even fiercer argument broke out about whether the paint on the wall was "in" the room! It's certainly an interesting exercise to produce and refine such distinctions, but my sense is that this is not a well-defined task outside of some purpose or goal that guides the production of these distinctions.

Stories, however, open up an interesting new possibility. Rather than using a large collection of special symbol names that distinguish between an ever-increasing collection of cases of "in-ness", we can instead say ‘in’ as in the story STORY-532. At some point symbolic distinctions could begin to be made by exploiting their extrinsic contexts of use to provide a basis for further refinement, as opposed to trying to shoehorn that context into the symbol name itself.

1 Comments:

Blogger Olmy said...

Using words as unit names can lead to problems.

For example:

Frame: water
event: motion drink boil wash make putoutfire freeze heat flow fall swim spill reflect mix rain clean
toolused: wateringcan
actor: plant liquid
wetness: wet

This mixes up watering a plant with a liquid which is an event and water as a physical thing which can be in a number of events boil,wash,...

Mature cyclists might learn from this and write things like...
WaterVehicleTypeByDesign
Type43-SupportWatercraft
UnderseaMedicineSpecialist
Underwater rdf:type SpatialThingTypeByGenericLocation


Using stories as an implicit context might get around the problem of confusion of meaning or the exhaustive deliniation of ever more obscure differences.

http://www.cyc.com/2004/06/04/cyc

http://homepage.eircom.net/~cornagill/frames/water.html

September 15, 2004 at 11:31 AM  

Post a Comment

<< Home