Suggested Upper Merged Ontology

(Redirected from SUMO class)
Suggested Upper Merged Ontology
Entity    
  Physical    
  Object

 

  Process

 

  Abstract    
  Quantity

 

  Proposition

 

  Attribute

 

  Relation

 

  Set or Class

 

Fundamental categories in the Suggested Upper Merged Ontology[1]

The Suggested Upper Merged Ontology (SUMO)[2] is an upper ontology intended as a foundation ontology for a variety of computer information processing systems. SUMO defines a hierarchy of classes and related rules and relationships. These are expressed in a version of the language SUO-KIF, a higher-order logic that has a LISP-like syntax, as well as the TPTP family of languages. A mapping from WordNet synsets to SUMO[3] has been defined. Initially, SUMO was focused on meta-level concepts (general entities that do not belong to a specific problem domain), and thereby would lead naturally to a categorization scheme for encyclopedias. It has now been considerably expanded to include a mid-level ontology and dozens of domain ontologies.

SUMO is organized for interoperability of automated reasoning engines. To maximize compatibility, schema designers can try to assure that their naming conventions use the same meanings as SUMO for identical words (for example, "agent" or "process"). SUMO has an associated open source Sigma knowledge engineering environment.

Initially, Sumo was developed by the Teknowledge Corporation and now is maintained by Articulate Software. SUMO is open source. The first release was in December 2000.

See also

edit

References

edit
  1. ^ Heckmann, Dominikus (2006). Ubiquitous User Modeling. IOS Press. p. 42. ISBN 978-3-89838-297-7.
  2. ^ Niles, I., & Pease, A., (2001), Toward a Standard Upper Ontology, in Proceedings of the 2nd International Conference on Formal Ontology in Information Systems (FOIS-2001), Chris Welty and Barry Smith, eds, pp2-9.
  3. ^ Niles, I., and Pease, A., (2003). Linking Lexicons and Ontologies: Mapping WordNet to the Suggested Upper Merged Ontology, Proceedings of the IEEE International Conference on Information and Knowledge Engineering, pp 412-416.
edit