]> 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. A collection of types of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r3NNXFjgtEdaHLgACs0uFOQ" class="cyc_term">Filesystem</a>, divided by their means of implementation. One widely deployed instance is <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r3NN-IjgtEdaHLgACs0uFOQ" class="cyc_term">NetworkFileSystem</a>. type of file system FileSystemTypeByImplementation types of file system Second Extended filesystem SecondExtendedFilesystem The collection of all VFAT. A type of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r87uGaAGRQdefa_uVdxD6Rw" class="cyc_term">FATFilesystem</a>. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4ryhCmqAGSQdeAmrG1HN9C0w" class="cyc_term">VFATFileSystem</a> is a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r5itnkP2sQdaPT_fytzyaGQ" class="cyc_term">FileSystemTypeByImplementation</a>. VFATFileSystem VFAT New Technology filesystem NewTechnologyFilesystem ThirdExtendedFileSystem Ext3fs NetworkFileSystem NFS FATFilesystem FAT The collection of all FAT. A type of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r3NNXFjgtEdaHLgACs0uFOQ" class="cyc_term">Filesystem</a>. File Allocation Table (FAT) is the main file system developed for MS-DOS and Windows. The FAT file system is considered relatively uncomplicated, and because of that it is popular format for floppy disks. It is also often used to share data between several operating systems booting on the same computer. FAT is a relatively early file system design, and because of that it suffered from several problems. First, its simple file layout allows for fragmentation, which lead to significant slow-ups during the file system operation. Secondly, FAT was not designed for redundancy in the case of system failure. Thirdly, the first versions of FAT allowed file name sizes of only up to 11 characters. With <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVivY5wpEbGdrcN5Y29ycA" class="cyc_term">MSWindowsNT</a> operating systems, FAT began to be superceded by NTFS (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rYhcn1DqzEdac-wACs0uFOQ" class="cyc_term">NewTechnologyFilesystem</a>). <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r87uGaAGRQdefa_uVdxD6Rw" class="cyc_term">FATFilesystem</a> is a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r5itnkP2sQdaPT_fytzyaGQ" class="cyc_term">FileSystemTypeByImplementation</a>. A collection of types of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r3NNXFjgtEdaHLgACs0uFOQ" class="cyc_term">Filesystem</a>, divided by their means of implementation. One widely deployed instance is <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r3NN-IjgtEdaHLgACs0uFOQ" class="cyc_term">NetworkFileSystem</a>. type of file system FileSystemTypeByImplementation A <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rtGXkHpNaEdqAAAACs0uFOQ" class="cyc_term">KBDependentCollection</a> of collections of collections (and thus an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rviPYH5wpEbGdrcN5Y29ycA" class="cyc_term">CollectionTypeType</a> and a specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvtppU5wpEbGdrcN5Y29ycA" class="cyc_term">CollectionType</a>). A sibling-disjoint collection type is such that its known (i.e. KB-represented) instances are collections that -- save for any that are related to each other by <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViBDpwpEbGdrcN5Y29ycA" class="cyc_term">genls</a> and any that are explicitly asserted to be exceptions (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwQtVmpwpEbGdrcN5Y29ycA" class="cyc_term">siblingDisjointExceptions</a>) -- are disjoint from each other. More precisely, each instance <code>SIB</code> of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViA4pwpEbGdrcN5Y29ycA" class="cyc_term">SiblingDisjointCollectionType</a> is a collection of collections that has the following KB-dependent property: For any two known instances <code>COL1</code> and <code>COL2</code> of <code>SIB</code>, at least one of the following is known to hold: <pre> (a) (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViBDpwpEbGdrcN5Y29ycA" class="cyc_term">genls</a> COL1 COL2) (b) (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViBDpwpEbGdrcN5Y29ycA" class="cyc_term">genls</a> COL2 COL1) (c) (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwQtVmpwpEbGdrcN5Y29ycA" class="cyc_term">siblingDisjointExceptions</a> COL1 COL2) (d) (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViA45wpEbGdrcN5Y29ycA" class="cyc_term">disjointWith</a> COL1 COL2) </pre> Moreover, note that if <code>MT</code> is a context (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViA1ZwpEbGdrcN5Y29ycA" class="cyc_term">Microtheory</a>) in which (i) both <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViBBJwpEbGdrcN5Y29ycA" class="cyc_term">isa</a> COL1 SIB)</code> and <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViBBJwpEbGdrcN5Y29ycA" class="cyc_term">isa</a> COL2 SIB)</code> hold and (ii) neither <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViBDpwpEbGdrcN5Y29ycA" class="cyc_term">genls</a> COL1 COL2)</code> nor <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViBDpwpEbGdrcN5Y29ycA" class="cyc_term">genls</a> COL2 COL1)</code> nor <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwQtVmpwpEbGdrcN5Y29ycA" class="cyc_term">siblingDisjointExceptions</a> COL1 COL2)</code> is known to hold (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP-JvpwpEbGdrcN5Y29ycA" class="cyc_term">knownSentence</a>), then <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViA45wpEbGdrcN5Y29ycA" class="cyc_term">disjointWith</a> COL1 COL2)</code> holds by default in <code>MT</code>. For example, in <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjakJwpEbGdrcN5Y29ycA" class="cyc_term">BiologyMt</a> both <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAkpwpEbGdrcN5Y29ycA" class="cyc_term">Person</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjaoJwpEbGdrcN5Y29ycA" class="cyc_term">Dog</a> are instances of the sibling-disjoint collection type <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjK65wpEbGdrcN5Y29ycA" class="cyc_term">BiologicalSpecies</a>, while neither (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViBDpwpEbGdrcN5Y29ycA" class="cyc_term">genls</a> <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAkpwpEbGdrcN5Y29ycA" class="cyc_term">Person</a> <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjaoJwpEbGdrcN5Y29ycA" class="cyc_term">Dog</a>) nor (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViBDpwpEbGdrcN5Y29ycA" class="cyc_term">genls</a> <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjaoJwpEbGdrcN5Y29ycA" class="cyc_term">Dog</a> <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAkpwpEbGdrcN5Y29ycA" class="cyc_term">Person</a>) nor (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwQtVmpwpEbGdrcN5Y29ycA" class="cyc_term">siblingDisjointExceptions</a> <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAkpwpEbGdrcN5Y29ycA" class="cyc_term">Person</a> <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjaoJwpEbGdrcN5Y29ycA" class="cyc_term">Dog</a>) is known to hold in that context; consequently, (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViA45wpEbGdrcN5Y29ycA" class="cyc_term">disjointWith</a> <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAkpwpEbGdrcN5Y29ycA" class="cyc_term">Person</a> <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjaoJwpEbGdrcN5Y29ycA" class="cyc_term">Dog</a>) holds by default in <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjakJwpEbGdrcN5Y29ycA" class="cyc_term">BiologyMt</a>. Instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViA4pwpEbGdrcN5Y29ycA" class="cyc_term">SiblingDisjointCollectionType</a> include <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVji6JwpEbGdrcN5Y29ycA" class="cyc_term">BiologicalTaxon</a> (and its specializations), <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwKTnSJwpEbGdrcN5Y29ycA" class="cyc_term">OrganismPartType</a>, and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwE01SZwpEbGdrcN5Y29ycA" class="cyc_term">RelationshipTypeByArity</a>. See the generalization <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rk8dxOFcGEdaLwgACs0uFOQ" class="cyc_term">SiblingDisjointSetOrCollectionType</a>. Also cf. the stronger notion of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWPoRpwpEbGdrcN5Y29ycA" class="cyc_term">DisjointCollectionType</a>. sibling disjoint collection type SiblingDisjointCollectionType The collection of all specializations of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rHIBS0h_TEdaAAABQ2rksLw" class="cyc_term">FirstOrderCollection</a>, that is, of all collections of (first-order) collections, and an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rHUFI8h_TEdaAAABQ2rksLw" class="cyc_term">ThirdOrderCollection</a>. Instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rHQdVmB_TEdaAAABQ2rksLw" class="cyc_term">SecondOrderCollection</a> are collections of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rHIBS0h_TEdaAAABQ2rksLw" class="cyc_term">FirstOrderCollection</a>s. Any instance of any instance of any instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rHQdVmB_TEdaAAABQ2rksLw" class="cyc_term">SecondOrderCollection</a> is an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjaApwpEbGdrcN5Y29ycA" class="cyc_term">Individual</a>. SecondOrderCollection second-order Cyc collection A collection of types of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r3NNXFjgtEdaHLgACs0uFOQ" class="cyc_term">Filesystem</a>, divided by their means of implementation. One widely deployed instance is <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r3NN-IjgtEdaHLgACs0uFOQ" class="cyc_term">NetworkFileSystem</a>. type of file system FileSystemTypeByImplementation ObjectType The collection of all collections that are "object-like" in at least one respect. A collection <code>COL</code> is object-like just in case there is some sense of 'part' according to which any (or nearly any) given proper part of an instance of <code>COL</code> is not itself an instance of <code>COL</code>; when this happens <code>COL</code> is said to be object-like with respect to that sense of 'part'. More precisely, for a collection <code>COL</code> to be an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVirnZwpEbGdrcN5Y29ycA" class="cyc_term">ObjectType</a> it is sufficient that there be some specialization <code>PARTPRED</code> of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwgfukKs8QdePzLB9nLNpTw" class="cyc_term">properParts</a> such that, for any <code>OBJ1</code> and <code>OBJ2</code>, if <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViBBJwpEbGdrcN5Y29ycA" class="cyc_term">isa</a> OBJ1 COL)</code> and <code>(PARTPRED OBJ1 OBJ2)</code> both hold, then <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViBBJwpEbGdrcN5Y29ycA" class="cyc_term">isa</a> OBJ2 COL)</code> does not hold. (Also sufficient for <code>COL</code>'s being an object-type is that there be some specialization <code>INVPARTPRED</code> of the inverse of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwgfukKs8QdePzLB9nLNpTw" class="cyc_term">properParts</a> (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWHsNJwpEbGdrcN5Y29ycA" class="cyc_term">genlInverse</a>) such that <code>(INVPARTPRED OBJ2 OBJ1)</code>, with everything else remaining the same as above.) Note that neither of the above sufficient conditions for <code>COL</code>'s being an object-type is strictly necessary: some exceptions are allowed. Thus as long as either one of the above conditionals holds in nearly all cases, <code>COL</code> should be considered an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVirnZwpEbGdrcN5Y29ycA" class="cyc_term">ObjectType</a>. Here are two examples. Consider <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViVwZwpEbGdrcN5Y29ycA" class="cyc_term">Automobile</a>. Take an instance of that, say my car. Now consider one of the proper <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj5FpwpEbGdrcN5Y29ycA" class="cyc_term">physicalParts</a> of my car, say the steering wheel. The steering wheel is not an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViVwZwpEbGdrcN5Y29ycA" class="cyc_term">Automobile</a>. And the same would be true for any proper physical part of any car. So <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViVwZwpEbGdrcN5Y29ycA" class="cyc_term">Automobile</a> is an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVirnZwpEbGdrcN5Y29ycA" class="cyc_term">ObjectType</a>. Consider <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjyV5wpEbGdrcN5Y29ycA" class="cyc_term">CalendarYear</a>. No proper <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWn4OZwpEbGdrcN5Y29ycA" class="cyc_term">timeSlices</a> of a year is itself a year. So <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjyV5wpEbGdrcN5Y29ycA" class="cyc_term">CalendarYear</a> is an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVirnZwpEbGdrcN5Y29ycA" class="cyc_term">ObjectType</a>. See <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVir35wpEbGdrcN5Y29ycA" class="cyc_term">StuffType</a> for the contrasting (though not disjoint) notion of being stuff-like. type of object AtemporalNecessarilyEssentialCollectionType A collection of collections. Each instance <code>COL</code> of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rqEYnNVMqEdaSKAACs0x8nw" class="cyc_term">AtemporalNecessarilyEssentialCollectionType</a> (ANECT) is a collection satisfying three conditions: (1) <code>COL</code> is disjoint with (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViA45wpEbGdrcN5Y29ycA" class="cyc_term">disjointWith</a>) <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAxJwpEbGdrcN5Y29ycA" class="cyc_term">TemporalThing</a>, (2) every instance <code>INST</code> of <code>COL</code> is an instance of <code>COL</code> essentially (i.e. <code>INST</code> is an instance of <code>COL</code>, and could not exist without being an instance of <code>COL</code>), and (3) condition (2) is a necessary truth about <code>COL</code>. Positive examples of ANECTs include <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAzJwpEbGdrcN5Y29ycA" class="cyc_term">Collection</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVieEpwpEbGdrcN5Y29ycA" class="cyc_term">Integer</a>, and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAzZwpEbGdrcN5Y29ycA" class="cyc_term">Relation</a> (each of which is a collection of atemporals and is such that, necessarily, all of its instances are in it essentially). Negative examples include <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjpUZwpEbGdrcN5Y29ycA" class="cyc_term">SpatialThing</a> (though arguably it is necessary that all of its instances are essentially instances of it, it is not disjoint with <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAxJwpEbGdrcN5Y29ycA" class="cyc_term">TemporalThing</a>) and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP4FM5wpEbGdrcN5Y29ycA" class="cyc_term">UniqueAnatomicalPartType</a> (which, though disjoint with <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAxJwpEbGdrcN5Y29ycA" class="cyc_term">TemporalThing</a>, has instances, such as <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjvDpwpEbGdrcN5Y29ycA" class="cyc_term">Heart</a>, that could exist even if they weren't instances of it; e.g. it might have been the case that every creature with a heart had at least two hearts). There are no known examples of Cyc-reified collections satisfying conditions (1) and (2) but not (3), but one can be contrived. Suppose that all of today's winning lottery numbers were primes. Now consider the collection: (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvrhK-JwpEbGdrcN5Y29ycA" class="cyc_term">CollectionUnionFn</a> (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjkdpwpEbGdrcN5Y29ycA" class="cyc_term">TheSet</a> <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjrdZwpEbGdrcN5Y29ycA" class="cyc_term">PrimeNumber</a> TodaysWinningLotteryNumbers)) This collection is clearly disjoint with <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAxJwpEbGdrcN5Y29ycA" class="cyc_term">TemporalThing</a> and, by hypothesis, all of its instances are in it essentially (as each prime number is essentially a prime number). But this last fact is not necessarily true of this collection: the collection might have had instances that belonged to it only contingently (i.e. not essentially), as it might have been the case that one of today's winning lottery numbers was non-prime, and no number is such that it is essentially one of today's winning lottery numbers. When asserting that something is an instance or specialization of a given instance of ANECT, it is appropriate to do so in the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r3_SgQU2iEdaCwAACs0x8nw" class="cyc_term">UniversalVocabularyMt</a> (q.v.). Indeed, ANECT was specially defined to facilitate the movement of appropriate assertions to that microtheory. Cf. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rGeylLJTfEdqAAAACs0uFOQ" class="cyc_term">PragmaticallyDecontextualizedCollection</a>. type of atemporal collection in which membership is necessarily essential 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