Relation pm#binary_relation (?,?)  in WebKB, most relation types are binary and some have a variable number of arguments (as in KIF), hence this type is currently only specialized by types that I do not want to see as direct subtypes of pm#relation
  exclusion:  pm#ternary_relation  pm#quaternary_relation  pm#relation_with_variable_arity
  supertype:  pm#relation_with_particular_property  this rather fuzzy type permits to group categorization schemes less common than those covered by the previous sibling categories
  instance of:  pm#binary_relation_type
  subtype:  pm#unary_function__unaryfunction (? -> ?)  function that requires a single argument; currently not specialized by the SUMO ternary relations since this seems useless (for now)
  subtype:  dc#Relation (?,?)  to specify a reference to a related resource; in WebKB, pm#relation or MORE PRECISE RELATION TYPES SHOULD BE USED INSTEAD
     subtype:  sumo#refers (?,?)  the 1st argument mentions or includes a reference to the 2nd argument, e.g., an article whose topic is a recent change in the price of oil may refer to many other things, e.g., the general state of the economy, the weather in California, the prospect of global warming, the options for alternative energy sources, the stock prices of various oil companies, etc.
        subtype:  sumo#names__name (pm#string,?)  the string names the 2nd argument
           subtype:  sumo#unique_identifier (pm#string,?)  the string uniquely identifies the 2nd argument
        subtype:  sumo#represents (?,?)  the 1st argument in some way indicates, expresses, connotes, pictures, describes ... the 2nd argument
           subtype:  sumo#contains_information (sumo#content_bearing_object,sumo#proposition)  relates a content_bearing_object to the proposition it expresses; examples include the relationships between a physical novel and its story and between a printed score and its musical content
           subtype:  sumo#realization (?,?)
        subtype:  rdfs#see_also__seealso (?,pm#entity)
           subtype:  rdfs#is_defined_by (?,pm#entity)  in WebKB, pm#definition SHOULD BE USED INSTEAD
              subtype:  pm#definition (?,pm#description_content/medium/container)  see also #definition
                 subtype:  rst#definition (pm#description_content/medium/container,pm#description_content/medium/container)  a logical relation should be used instead of this relation
           subtype:  owl#imports__import (?,pm#entity)  if imports(X,Y) and you believe X, then you should believe what is in Y
  subtype:  dc#Type (?,pm#entity)  to specify the nature or genre of the content of a resource; SHOULD NOT BE USED IN WEBKB
     subtype:  sumo#instance (?,sumo#set_or_class)  if the common reading conventions of parameters had been respected, this type would have been named instance_of; an object is an instance of a set_or_class if it is included in that set_or_class; an individual may be an instance of many classes, some of which may be subclasses of others; thus, there is no assumption in the meaning of instance about specificity or uniqueness
        subtype:  pm#kind__type___class___instance_of__instanceof (?,rdfs#class)  the '^' link in the FT notation
        subtype:  sumo#immediate_instance__immediateinstance (?,sumo#set_or_class)  if the common reading conventions of parameters had been respected, this type would have been named immediate_instance_of; an object is an immediate_instance of a set_or_class if it is an instance of the set_or_class and there does not exist a subclass of set_or_class such that it is an instance of the subclass
  subtype:  dc#Description (?,pm#entity)  to specify an account of the content of a resource; in WebKB, pm#topic or pmdescr SHOULD BE USED INSTEAD
     subtype:  pm#topic (?,pm#entity)
        subtype:  pm#annotation (?,pm#description_content/medium/container)
           subtype:  pm#descr (?,pm#description_content/medium/container)  for connecting an object to a formal representation of it, e.g., a representation written with a fcg
           subtype:  dc#Subject (pm#description,pm#entity)  to specify 1 or several topics; in WebKB, pm#descr SHOULD BE USED INSTEAD
           subtype:  pm#origin (?,pm#description_content/medium/container)
           subtype:  pm#use (?,pm#description_content/medium/container)
           subtype:  pm#advantage (?,pm#description_content/medium/container)
           subtype:  pm#disadvantage (?,pm#description_content/medium/container)
           subtype:  pm#definition (?,pm#description_content/medium/container)  see also #definition
           subtype:  pm#role (?,pm#description_content/medium/container)
           subtype:  pm#requirement (?,pm#description_content/medium/container)
           subtype:  pm#issue (?,pm#description_content/medium/container)
           subtype:  pm#trap (?,pm#description_content/medium/container)
     subtype:  pm#url (?,pm#URL)
     subtype:  pm#file_or_file_element (?,pm#description_container)
        subtype:  pm#file (?,pm#document_element)
           subtype:  pm#home_page (?,pm#document_element)
        subtype:  pm#file_element (?,pm#document_element)
        subtype:  pm#descr_in__descrin (?,pm#description_container)  when a thing t has a description stored in a description container dc, there is a relation pm#descr_in from t to dc
           subtype:  pm#descr_container__description_support___descr_support (pm#description,pm#description_container)  permits to associate a statement with an object on which it is represented
     subtype:  owl#version_info__versioninfo (? -> pm#entity)  generally, a string giving information about this version; e.g., RCS/CVS keywords
     subtype:  pm#title (? -> pm#string)  for connecting an object to its "title" in a natural language
     subtype:  rdfs#comment  for connecting an object to an informal representation of it, typically a node with a string inside; in WebKB, the FT and FCG notations permit to avoid using this relation type
  subtype:  pm#relation_from_or_to_WordNet_type (*)
     subtype:  pm#menu (pm#meal_shop,#food_or_beverage)
  subtype:  nsm#before (?,?)
     subtype:  pm#before (pm#time_measure,pm#time_measure)
     subtype:  pm#before_time (pm#situation,pm#time_measure)
     subtype:  pm#later_situation__latersituation (pm#situation,pm#situation)
        subtype:  pm#next_situation (pm#situation -> pm#situation)
           subtype:  pm#successor (pm#situation -> pm#situation)
        subtype:  pm#ending_situation__termination (pm#situation -> pm#situation)
        subtype:  pm#postcondition (pm#process,pm#situation)
        subtype:  pm#consequence (pm#situation,pm#situation)  see also rst#effect
  subtype:  nsm#after (?,?)
     subtype:  pm#after (pm#time_measure,pm#time_measure)
     subtype:  pm#until_time__untiltime__to_time (pm#situation -> pm#time_measure)
        subtype:  pm#arrival_time__arrivaltime (pm#process -> pm#time_measure)
     subtype:  pm#before_situation (pm#situation,pm#situation)  in WebKB, do not use these relations, use their inverses
        subtype:  pm#previous_situation (pm#situation -> pm#situation)
        subtype:  pm#beginning_situation__beginningsituation (pm#situation -> pm#situation)
        subtype:  pm#precondition (pm#process,pm#situation)
        subtype:  pm#cause (pm#situation,pm#situation)  see also rst#cause
           subtype:  sumo#causes (sumo#process,sumo#process)  the process in the 1st argument brings about the process in the 2nd argument