]> 2008/06/10 OpenCyc Knowledge Base Copyright© 2001-2008 Cycorp, Inc., http://www.cyc.com/, Austin, TX, USA This file contains an OWL representation of information contained in the OpenCyc Knowledge Base. The content of this OWL file is licensed under the Creative Commons Attribution 3.0 license whose text can be found at http://creativecommons.org/licenses/by/3.0/legalcode. The content of this OWL file, including the OpenCyc content it represents, constitutes the "Work" referred to in the Creative Commons license. The terms of this license equally apply to, without limitation, renamings and other logically equivalent reformulations of the content of this OWL file (or portions thereof) in any natural or formal language, as well as to derivations of this content or inclusion of it in other ontologies. externalID A unique, language-neutral, variable-sized identifier for a concept that can be used to refer unambiguously to that concept across OWL exports or across Cyc inference engines. label A natural-language representation for a concept that is both human readable and readable by the Cyc inference engine. These terms are not guaranteed to refer to the same concept across time but are guaranteed to be consistent within a particular OWL export. Use 'cycAnnot:externalID' for unambiguously referring to a concept across OWL exports or across Cyc inference engines. ComputerDataStructure A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwFn8s5wpEbGdrcN5Y29ycA" class="cyc_term">ComputerAIS</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r3NMwBjgtEdaHLgACs0uFOQ" class="cyc_term">ComputerDataStructure</a> is data structured in such a way that when it is stored a computer can use it efficiently. Important specializations include <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r3NMwBzgtEdaHLgACs0uFOQ" class="cyc_term">Array_DataStructure</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r3NNXEDgtEdaHLgACs0uFOQ" class="cyc_term">HashTable_DataStructure</a>. datastructure datastructures data structure data structures http://en.wikipedia.org/wiki/Data_structure Cyc KB datastructure CycKBDatastructure A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r3NMwBjgtEdaHLgACs0uFOQ" class="cyc_term">ComputerDataStructure</a> each instance of which is a part of some instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjqoZwpEbGdrcN5Y29ycA" class="cyc_term">CycKB</a> (q.v.). Some (but not all) <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rj31mKIobEdaAAACQJ5T1Bg" class="cyc_term">CycKBDatastructure</a>s store information about particular indexed CycL expressions, such as <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV281JwpEbGdrcN5Y29ycA" class="cyc_term">CycLAssertion</a>s or <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvzSRxJwpEbGdrcN5Y29ycA" class="cyc_term">CycLConstant</a>s. index data structure A data structure which permits the efficient lookup of data by maintaining an 'index' of pointers to the data. IndexDataStructure Array-DataStructure A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r3NMwBjgtEdaHLgACs0uFOQ" class="cyc_term">ComputerDataStructure</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r3NMwBzgtEdaHLgACs0uFOQ" class="cyc_term">Array_DataStructure</a> arranges a group of data elements in a continuous block of memory. Individual elements are accessed by index using integers. array Cyc inference data structure CycInferenceDataStructure The collection of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r3NMwBjgtEdaHLgACs0uFOQ" class="cyc_term">ComputerDataStructure</a>s which denote Cyc internal inference objects. A specialization of both <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r3NMwBjgtEdaHLgACs0uFOQ" class="cyc_term">ComputerDataStructure</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rmUy0ojIYEdaAAACQJ5pZBw" class="cyc_term">StructuredKnowledgeSource</a>. Each instance of FileHashTable-DataStructure is a data structure that contains a stream (in a way, a pointer) to a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4riFMd4Xy9EdaIRQABAkLVdg" class="cyc_term">FileHashTable_File</a>, as well as information about what type of encoding/decoding will need to be used while writing/reading to/from the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4riFMd4Xy9EdaIRQABAkLVdg" class="cyc_term">FileHashTable_File</a> at hand. A <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4riFMd4ny9EdaIRQABAkLVdg" class="cyc_term">FileHashTable_DataStructure</a> is a gateway to the information stored in a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4riFMd4Xy9EdaIRQABAkLVdg" class="cyc_term">FileHashTable_File</a>. It has a functional interface that is very similar to that of a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r3NNXEDgtEdaHLgACs0uFOQ" class="cyc_term">HashTable_DataStructure</a>, in that they both support functions that look up values for given keys or assign values to given keys. Only, in one case (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r3NNXEDgtEdaHLgACs0uFOQ" class="cyc_term">HashTable_DataStructure</a>) the key/value pairs are stored in memory while in the other case (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4riFMd4ny9EdaIRQABAkLVdg" class="cyc_term">FileHashTable_DataStructure</a>) they are stored on disk (that is, in a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4riFMd4Xy9EdaIRQABAkLVdg" class="cyc_term">FileHashTable_File</a>). file hash table data structure FileHashTable-DataStructure inode FileIndexNode ComputerDataStructure datastructure A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwFn8s5wpEbGdrcN5Y29ycA" class="cyc_term">ComputerAIS</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r3NMwBjgtEdaHLgACs0uFOQ" class="cyc_term">ComputerDataStructure</a> is data structured in such a way that when it is stored a computer can use it efficiently. Important specializations include <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r3NMwBzgtEdaHLgACs0uFOQ" class="cyc_term">Array_DataStructure</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r3NNXEDgtEdaHLgACs0uFOQ" class="cyc_term">HashTable_DataStructure</a>. clarifying collection type ClarifyingCollectionType A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAzJwpEbGdrcN5Y29ycA" class="cyc_term">Collection</a>. Instances are collections that are usefully invoked for purposes of resolving ambiguity and confusion that arise from the use of non-perspicuous languages. Suppose a human or other intelligent agent uses a language, such as a natural language, that is rife with ambiguity, and uses a word WORD of that language whose intended reference is unclear: in the context WORD might refer to THING1 or to THING2, but not both. One strategy for resolving this ambiguity is to find properties of THING1 and THING2, say P1 and P2, that distinguish them from one another, and ask the speaker whether by "WORD," s/he intended to refer to something with P1, or to something with P2. For example, the speaker might use the word "bank," and in response one might ask whether a financial institution or a piece of shoreline was meant. Clearly, what values of P1 and P2 are chosen cannot be arbitrary; asking whether the speaker meant to refer to a multi-individual agent versus a non-agentive place is not as effective as asking the speaker to choose between the "financial institution" and "shoreline" interpretations described above. Instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r_4bScKNtQdiVw7XtX-HN0Q" class="cyc_term">ClarifyingCollectionType</a> just are those collections -- such as the collection of financial institutions -- that might plausibly be invoked to resolve cases of ambiguity of the kind described here. In particular, suppose TYPE1 is an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r_4bScKNtQdiVw7XtX-HN0Q" class="cyc_term">ClarifyingCollectionType</a> and TYPE2 is not, and THING is an instance of both TYPE1 and TYPE2. The fact that (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViBBJwpEbGdrcN5Y29ycA" class="cyc_term">isa</a> TYPE1 <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r_4bScKNtQdiVw7XtX-HN0Q" class="cyc_term">ClarifyingCollectionType</a>) is a reason to prefer TYPE1 over TYPE2 when calculating possible clarifying properties for THING. Pretty String (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwLSVCpwpEbGdrcN5Y29ycA" class="cyc_term">prettyString</a> TERM STRING) means that STRING is the English word or expression (sequence of words) commonly used to refer to TERM. The predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwLSVCpwpEbGdrcN5Y29ycA" class="cyc_term">prettyString</a> is used by the code which generates CycL to English paraphrases, but its applicability is not restricted to this use. prettyString SKSIDataTypeDescriptions-Topic SKSI data type descriptions topic <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r6Gb7tJodQdiTM88iSyMLmg" class="cyc_term">SKSIDataTypeDescriptions_Topic</a> is the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rgQsP1F2xEdif1wACs2IMlQ" class="cyc_term">Topic</a> containing the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViqDZwpEbGdrcN5Y29ycA" class="cyc_term">CycL</a> terms used to describe data types for SKSI. ComputerDataStructure datastructure A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwFn8s5wpEbGdrcN5Y29ycA" class="cyc_term">ComputerAIS</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r3NMwBjgtEdaHLgACs0uFOQ" class="cyc_term">ComputerDataStructure</a> is data structured in such a way that when it is stored a computer can use it efficiently. Important specializations include <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r3NMwBzgtEdaHLgACs0uFOQ" class="cyc_term">Array_DataStructure</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r3NNXEDgtEdaHLgACs0uFOQ" class="cyc_term">HashTable_DataStructure</a>. composite data type A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rF8Vc5VFnEdaCtgACs0uXdw" class="cyc_term">ComputerDatatypeType</a>. The collection of all data types that are compositional in nature, usually consisting of several named data fields. Examples include structs in <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViLJ5wpEbGdrcN5Y29ycA" class="cyc_term">C_ProgrammingLanguage</a> and objects in <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwQfjYJwpEbGdrcN5Y29ycA" class="cyc_term">JavaProgrammingLanguage</a>. CompositeDatatypeType StructuredInformationSource A specialization of both <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvu__KJwpEbGdrcN5Y29ycA" class="cyc_term">InformationStore</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwBObNJwpEbGdrcN5Y29ycA" class="cyc_term">PartiallyIntangibleIndividual</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj4OZwpEbGdrcN5Y29ycA" class="cyc_term">StructuredInformationSource</a> is an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvu__KJwpEbGdrcN5Y29ycA" class="cyc_term">InformationStore</a> in which bits of information are represented as related in a systematic way that is easily characterized by some type of formal structure, including spatial or architectural terms (used metaphorically). Examples include: a database organized in fields and values; a spreadsheet organized in rows and columns with entries; an organizational tree diagram with nodes and branches; a topographical map; a document written in HTML (hyper-text markup language). Negative examples include computer programs, poems, and novels. structured information source ComputerDataStructure datastructure A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwFn8s5wpEbGdrcN5Y29ycA" class="cyc_term">ComputerAIS</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r3NMwBjgtEdaHLgACs0uFOQ" class="cyc_term">ComputerDataStructure</a> is data structured in such a way that when it is stored a computer can use it efficiently. Important specializations include <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r3NMwBzgtEdaHLgACs0uFOQ" class="cyc_term">Array_DataStructure</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r3NNXEDgtEdaHLgACs0uFOQ" class="cyc_term">HashTable_DataStructure</a>. ComputerDataStructure datastructure A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwFn8s5wpEbGdrcN5Y29ycA" class="cyc_term">ComputerAIS</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r3NMwBjgtEdaHLgACs0uFOQ" class="cyc_term">ComputerDataStructure</a> is data structured in such a way that when it is stored a computer can use it efficiently. Important specializations include <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r3NMwBzgtEdaHLgACs0uFOQ" class="cyc_term">Array_DataStructure</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r3NNXEDgtEdaHLgACs0uFOQ" class="cyc_term">HashTable_DataStructure</a>. A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwFn8s5wpEbGdrcN5Y29ycA" class="cyc_term">ComputerAIS</a>. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rDkbmEUvwEdaZRgACs0uXdw" class="cyc_term">ProgramObject</a> is the collection of all data structures that are explicitly referenced in computer programs. All data types are considered to be specializations of this collection. programming datastructure ProgramObject