Simple Browser : Welcome guest : log in
Home |  Graph |  ]  KB:  Language:   

Formal Language: 




Sigma KEE - names
KB Term: 
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
names
(names ?STRING ?ENTITY) means that the thing ?ENTITY has the SymbolicString ?STRING as its name. Note that names and represents are the two immediate subrelations of refers. The predicate names is used when the referring item is merely a tag without connotative content, while the predicate represents is used for referring items that have such content.
Relationships      
Parents refers (refers ?OBJ1 ?OBJ2) means that ?OBJ1 mentions or includes a reference to ?OBJ2. Note that refers is more general in meaning than represents, because presumably something can represent something else only if it refers to this other thing. For example, 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.
Children agentName(agentName ?STRING ?OBJ) means that ?STRING is a full or partial name for the AutonomousAgent ?OBJ.
 alias(alias ?STRING ?AGENT) means that ?STRING is an alternate identifier for ?AGENT, and is likely being used to hide or obscure ?AGENT's true identity.
 conventionalLongName(conventionalLongName ?NAME ?THING) means that the string ?NAME is the long form of the name conventionally used for ?THING.
 conventionalShortName(conventionalShortName ?NAME ?THING) means that the string ?NAME is the short form of the name conventionally used for ?THING. For a more specialized subset of short names, see abbreviation.
 familyName(familyName ?STRING ?HUMAN) means that the SymbolicString ?STRING denotes a non-optional name that ?HUMAN has inherited by virtue of being born into a particular family (kin group). surname is another word for this type of name. Cf. givenName.
 filenameA relation between a SymbolicString and an instance of DigitalData that specified the filename of the data on a particular computer file system. This relation is for a fully qualified filename including a device specification such as a drive letter or name, a directory, and a name. This can include names that are aliases for a different physical file location. It does not include the specification of a particular machine on a network, such as an internet domain name, although it may reference a device specification that ultimately resolves to a storage device on a network.
 formerName(formerName ?NAME ?THING) means that the string ?NAME is a name formerly used for ?THING.
 fullName(fullName ?STRING ?OBJ) means that ?STRING is a (more or less) complete name for ?OBJ, having all of the parts (fields, name components) possible for ?OBJ's name. The parts of ?STRING, if any, may be in conventional order, or in indexed (for alphabetic sorting) order. Examples: George W. Bush, The White House, The United Kingdom of Great Britain and Northern Ireland.
 givenName(givenName ?STRING ?HUMAN) means that ?STRING is a name selected for ?HUMAN, usually from among many options, as opposed to a mandatory name (cf. familyName) that ?HUMAN has inherited by virtue of being born into a certain kin group, caste, or occupation.
 localLongName(localLongName ?NAME ?THING) means that the string ?NAME is the long form of the name used for ?THING in its local area or language.
 localShortName(localShortName ?NAME ?THING) means that the string ?NAME is the short form of the name used for ?THING in its local area or language.
 middleName(middleName ?CHAR ?INDIV) means that the SymbolicString ?CHAR contains the middle name of the Human ?INDIV.
 nameIndexOrder(nameIndexOrder ?STRING ?OBJ) means that ?STRING is a full or partial name for ?OBJ, and that the first component of ?STRING is the indexed subString identified by keyName. Example: Bush, George.
 password(password ?Password ?Account) means that ?Password is the password associated with the UserAccount that the ComputerUser uses while logging onto a computer system.
 titlesA BinaryPredicate used to indicate the title of a ContentBearingPhysical. Note that the second argument type restriction is a subclass, rather than an instance, of ContentBearingPhysical. Thus, the title Murder_on_the_Orient_Express corresponds to a large class of Books, and not just to a single copy of the book.
 uniqueIdentifierThe class of names that uniquely identify an instance of Entity. Some examples of uniqueIdentifiers are the keys of tables in database applications and the ISBN (International Standard Book Number).
 userName(userName ?Name ?User) means that ?Name is the name the ComputerUser uses to identify himself or herself when logging onto a UserAccount on a computer system.
InstancesAbstractProperties or qualities as distinguished from any particular embodiment of the properties/qualities in a physical medium. Instances of Abstract can be said to exist in the same sense as mathematical objects such as sets and relations, but they cannot exist at a particular place and time without some physical encoding or embodiment.
 BinaryPredicateA Predicate relating two items - its valence is two.
 BinaryRelationBinaryRelations are relations that are true only of pairs of things. BinaryRelations are represented as slots in frame systems.
 EntityThe universal class of individuals. This is the root node of the ontology.
 InheritableRelationThe class of Relations whose properties can be inherited downward in the class hierarchy via the subrelation Predicate.
 PredicateA Predicate is a sentence-forming Relation. Each tuple in the Relation is a finite, ordered sequence of objects. The fact that a particular tuple is an element of a Predicate is denoted by '(*predicate* arg_1 arg_2 .. arg_n)', where the arg_i are the objects so related. In the case of BinaryPredicates, the fact can be read as `arg_1 is *predicate* arg_2' or `a *predicate* of arg_1 is arg_2'.
 RelationThe Class of relations. There are two kinds of Relation: Predicate and Function. Predicates and Functions both denote sets of ordered n-tuples. The difference between these two Classes is that Predicates cover formula-forming operators, while Functions cover term-forming operators.
Belongs to Class Entity


Show simplified definition with tree view
Show full definition (without tree view)
Show full definition (with tree view)


Sigma web home      Suggested Upper Merged Ontology (SUMO) web home
Sigma version 3.0 is open source software produced by Articulate Software and its partners