]> 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. ComputerActivityType An instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViA4pwpEbGdrcN5Y29ycA" class="cyc_term">SiblingDisjointCollectionType</a>. Each instance of this (second-order) collection is a subcollection of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViFUJwpEbGdrcN5Y29ycA" class="cyc_term">ComputerActivity</a> all of whose instances are a particular and distinct type of activity. Examples include <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvdMvgJwpEbGdrcN5Y29ycA" class="cyc_term">EMailSending</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjYgJwpEbGdrcN5Y29ycA" class="cyc_term">BootingAComputer</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjkXZwpEbGdrcN5Y29ycA" class="cyc_term">ComputerCrashing</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvm2Dx5wpEbGdrcN5Y29ycA" class="cyc_term">OnlineChat</a>. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvv-fq5wpEbGdrcN5Y29ycA" class="cyc_term">AttackByComputerOperation</a> is not an instance as it is not distinct enough. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvzTVp5wpEbGdrcN5Y29ycA" class="cyc_term">EnteringAComputerPassword</a> is an instance, but <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwOH4i5wpEbGdrcN5Y29ycA" class="cyc_term">EnteringADomainAdministratorPassword</a> is not as it is too specific. This collection is an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViA4pwpEbGdrcN5Y29ycA" class="cyc_term">SiblingDisjointCollectionType</a> because it is assumed that computer-related activities are analysed fine-grainedly enough that if a putative instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViFUJwpEbGdrcN5Y29ycA" class="cyc_term">ComputerActivity</a> would fall under two sibling <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rzJQyqGkeEdaAAAABAxv-7A" class="cyc_term">ComputerActivityType</a>s, it should be analysed as two events. computer activity type computer activity types AttackByComputerOperationActionType The collection of all action types which are typically involved in electronic attack. At present, this collection is extensionally defined. attack by computer operation type employee computer activity type EmployeeComputerActivityType A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rzJQyqGkeEdaAAAABAxv-7A" class="cyc_term">ComputerActivityType</a>. Each instance of this (second-order) collection is a subcollection of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViFUJwpEbGdrcN5Y29ycA" class="cyc_term">ComputerActivity</a> all of whose instances are a particular and distinct type of computer-involving activity which is typically performed by employees as part of their work duties. Examples include <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rotstM0daEdaEEQACs0uFOQ" class="cyc_term">EMailCommunication</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4ra59ZgACDEdeEDgCgyeeBIg" class="cyc_term">PreparingPresentationSlides</a>. Examples of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rzJQyqGkeEdaAAAABAxv-7A" class="cyc_term">ComputerActivityType</a> which are not instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r41GBACfpQdePaar6Yq-hJg" class="cyc_term">EmployeeComputerActivityType</a> include <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r6hdz8bxBEdaD8QCgyeeBIg" class="cyc_term">InterfacingBetweenComputerDeviceAndOS</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvfPj0JwpEbGdrcN5Y29ycA" class="cyc_term">HomecamBroadcasting</a>. Activities such as <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvjMHfZwpEbGdrcN5Y29ycA" class="cyc_term">ModifyingAFile</a>, though often performed by employees, are assumed to be too fine-grained and not distinct enough to warrant inclusion in this collection. database referential integrity constraint type <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rw3Z_1uBOEdqAAAACs6hO_g" class="cyc_term">DatabaseReferentialIntegrityConstraintType</a> is the collection of selected specializations of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwwjQqOBOEdqAAAACs6hO_g" class="cyc_term">EnforcingADatabaseReferentialIntegrityConstraint</a> which correspond to the types of referential integrity constraints that a database management system enforces between the primary key of a database table and references to that key from within the same, or other tables. DatabaseReferentialIntegrityConstraintType <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rs3gJBuBOEdqAAAACs6hO_g" class="cyc_term">DatabaseModificationType</a> is a partitioning (See <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwA9k15wpEbGdrcN5Y29ycA" class="cyc_term">facets_Partition</a>) collection for <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rsstm7OBOEdqAAAACs6hO_g" class="cyc_term">ModifyingARecordInADatabase</a>. Its three members are <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwfX1JOBOEdqAAAACs6hO_g" class="cyc_term">DeletingARecordFromADatabase</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwhwvtOBOEdqAAAACs6hO_g" class="cyc_term">InsertingARecordIntoADatabase</a>, and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwoeLuuBOEdqAAAACs6hO_g" class="cyc_term">UpdatingARecordInADatabase</a>. DatabaseModificationType database modification type BugzillaBugReportActionType bugzilla bug report action type <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rh1WRYmfFQdiKx4-H8yoVvg" class="cyc_term">BugzillaBugReportActionType</a> is a specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rzJQyqGkeEdaAAAABAxv-7A" class="cyc_term">ComputerActivityType</a> whose instances are collections of actions performed on <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r8BS9oDL1Qdec54Cn4tsnZQ" class="cyc_term">BugzillaBugReport</a>s. Salient instances include <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rhT3yhGfFQdiG5LqHyuBOYA" class="cyc_term">CreatingABugzillaBugReport</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rOUC28mPCQdibYYquX6sxRw" class="cyc_term">UpdatingABugzillaBugReport</a>. See also the specialization <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rP__vimPCQdiMJIo6opoVKQ" class="cyc_term">BugzillaBugReportUpdateType</a>.

A collection of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViADZwpEbGdrcN5Y29ycA" class="cyc_term">Event</a>s. Each <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvc-PwZwpEbGdrcN5Y29ycA" class="cyc_term">ChatRoom</a> is an event of a program running on a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWU7IpwpEbGdrcN5Y29ycA" class="cyc_term">ComputerServer</a> that accepts contributions to an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvm2Dx5wpEbGdrcN5Y29ycA" class="cyc_term">OnlineChat</a> from multiple users logged on remotely, sending their 'utterances' over the Internet. The program sends each participant's utterances more-or-less in real time in the order in which they were received to all clients connected to the chat room. Typically, a user's utterance is identified by their username or graphical 'avatar'. chat room ChatRoom

<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4ra58LYgCDEdeEDgCgyeeBIg" class="cyc_term">LockingComputerDisplay</a> is a specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViFUJwpEbGdrcN5Y29ycA" class="cyc_term">ComputerActivity</a>. Each instance involves either a person-iniated or an automatic computer process that locks the computer when it is not used for a period of time. A person is generally required to enter a password to unlock the computer. The computer is generally running a screen saver while it is locked. locking computer display LockingComputerDisplay

computer process crash ComputerProcessCrashing A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj8AZwpEbGdrcN5Y29ycA" class="cyc_term">ComputerProcessRunning</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rywKbCOX9QdaPsb4-z5qOsw" class="cyc_term">ComputerProcessCrashing</a> is an event in which a computer process fails exits unexpectedly. Typically, an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjkXZwpEbGdrcN5Y29ycA" class="cyc_term">ComputerCrashing</a> (q.v.) is comprised of many instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rywKbCOX9QdaPsb4-z5qOsw" class="cyc_term">ComputerProcessCrashing</a>.

backing up a file BackingUpAComputerFile

ProvidingRequestedInformationToComputerProcess providing requested information to computer process The collection of all communication acts [<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVieg5wpEbGdrcN5Y29ycA" class="cyc_term">CommunicationAct_Single</a>] in which a computer user provides input to a running computer process [<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj8AZwpEbGdrcN5Y29ycA" class="cyc_term">ComputerProcessRunning</a>] which the process asked the user to provide.

ProgramSelfReplication This is the collection of all events of programs replicating themselves. It includes the propagation of instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwBbPnZwpEbGdrcN5Y29ycA" class="cyc_term">ComputerWorm</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViKVpwpEbGdrcN5Y29ycA" class="cyc_term">ComputerVirus</a>. program self-replication

The subcollection of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv5kxb5wpEbGdrcN5Y29ycA" class="cyc_term">ComputerProcess_Generic</a> whose instances execute in parallel on multiple CPUs. ComputerProcess-Distributed computer process distributed

accepting program user communication AcceptingProgramUserCommunication The collection of all events in which an instance of #$SoftwareAgent accepts information from an interactive user of an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj8AZwpEbGdrcN5Y29ycA" class="cyc_term">ComputerProcessRunning</a>.

A collection of actions done by computers on files. In each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvu41-ZwpEbGdrcN5Y29ycA" class="cyc_term">UploadingAFile</a>, a computer copies a file from a local <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjEJ5wpEbGdrcN5Y29ycA" class="cyc_term">ComputerDisk</a> or other long-term storage device, i.e. one that it <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi4ApwpEbGdrcN5Y29ycA" class="cyc_term">physicallyContains</a> or that is located within a few yards of it, to a file system that it is <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkKt5wpEbGdrcN5Y29ycA" class="cyc_term">remotelyConnectedTo</a> over a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVirUZwpEbGdrcN5Y29ycA" class="cyc_term">ComputerNetwork</a>. UploadingAFile uploading

sending e-mail A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwUv8oZwpEbGdrcN5Y29ycA" class="cyc_term">InformationTransferEvent_Electronic</a>. Each instance of this collection is an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViADZwpEbGdrcN5Y29ycA" class="cyc_term">Event</a> in which somebody or something sends an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvgIDb5wpEbGdrcN5Y29ycA" class="cyc_term">EMailMessage</a> to some <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjYb5wpEbGdrcN5Y29ycA" class="cyc_term">EMailAddress</a>. If successful, an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvdMvgJwpEbGdrcN5Y29ycA" class="cyc_term">EMailSending</a> ends when the email message reaches the intended recipient's <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv1lRdJwpEbGdrcN5Y29ycA" class="cyc_term">MailServer_Network</a>, at which point it is likely that an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv_55X5wpEbGdrcN5Y29ycA" class="cyc_term">EMailReceiving</a> will ensue. See also <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rotstM0daEdaEEQACs0uFOQ" class="cyc_term">EMailCommunication</a> -- events in which an email message is successfully sent and received. EMailSending

port scan PortScan A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rZRQyWhO3QdiZBM3niRcXaQ" class="cyc_term">PacketScanningAComputationalSystem</a>. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwPae0JwpEbGdrcN5Y29ycA" class="cyc_term">PortScan</a> is the collection of all scans to determine which ports are open on a given machine or network, as performed by a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwAZIbZwpEbGdrcN5Y29ycA" class="cyc_term">PortScanningProgram</a>.

computer booting A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViLSJwpEbGdrcN5Y29ycA" class="cyc_term">ProgramAction</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjH_JwpEbGdrcN5Y29ycA" class="cyc_term">DeviceStartingARun</a> -- the collection of events in which an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjXzZwpEbGdrcN5Y29ycA" class="cyc_term">Computer</a> runs the instructions on its boot sector, generally in order to get in normal operating mode. This may entail the instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjXzZwpEbGdrcN5Y29ycA" class="cyc_term">Computer</a>'s <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r4081In8AEdaAAAABAjVgzA" class="cyc_term">stateOfDevice</a> being changed from <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r19FsDHS5EdaAAACgyZzFrg" class="cyc_term">Device_Off</a> to <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rKqORBnS8EdaAAACgyZzFrg" class="cyc_term">Device_On</a>, but not necessarily. BootingAComputer

buffer overflow BufferOverflow A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj8AZwpEbGdrcN5Y29ycA" class="cyc_term">ComputerProcessRunning</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rPxlZ8KveEdaAAAACs0uFOQ" class="cyc_term">BufferOverflow</a> is an event in which data is input to a running process that pushes commands into the execution stack of the computer on which the program is running. As a consequence, the program may crash, or the the return address may be overwritten so that it points back into the buffer. Buffer overfloews invlove supplying the program a data string that is larger than the buffer for the program can handle, via a function in the program that does not perform bounds checking. In the standard C library there are a number of functions that copy or append strings without bounds checking: strcat(), strcpy(), sprintf(), vsprintf(), gets(). See <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv6x-eZwpEbGdrcN5Y29ycA" class="cyc_term">VulnerableToBufferOverflow</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv57LgpwpEbGdrcN5Y29ycA" class="cyc_term">BufferOverflowFault_ProgramCrashing</a>, and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvno0UZwpEbGdrcN5Y29ycA" class="cyc_term">BufferOverflowFault_CommandExecution</a>.

InformingProgramUser informing program user The collection of all events in which an instance of #$SoftwareAgent provides information to an interactive user of an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj8AZwpEbGdrcN5Y29ycA" class="cyc_term">ComputerProcessRunning</a>.

EnteringAUsername entering a username The collection of events in which an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvxMRzJwpEbGdrcN5Y29ycA" class="cyc_term">Username</a> is entered into a computer in order to gain access to a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwGq7AZwpEbGdrcN5Y29ycA" class="cyc_term">ComputationalSystem</a>. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvzTVp5wpEbGdrcN5Y29ycA" class="cyc_term">EnteringAComputerPassword</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvqJIppwpEbGdrcN5Y29ycA" class="cyc_term">EnteringAUsername</a> are the key subevents in instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjJt5wpEbGdrcN5Y29ycA" class="cyc_term">LoggingInOnAComputer</a>.

entering info into computer Collection of events where information is being added into a computer system. EnteringInfoIntoComputer

moving A computer file metaphorically A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwQr2aJwpEbGdrcN5Y29ycA" class="cyc_term">FileOperation</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOtpwpEbGdrcN5Y29ycA" class="cyc_term">GeneralizedTransfer</a>. In each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rZibjyI2WQdiVk_xcnOSl5w" class="cyc_term">MovingAComputerFile_Metaphorically</a>, a computer changes or indexes a file in such a way that it appears in a user interface to have moved to a different location. For events in which a file really is moved (or rather deleted and copied) to a new physical location in a computer's memory, see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv73W3ZwpEbGdrcN5Y29ycA" class="cyc_term">MovingAComputerFile_CopyingAndDeleting</a>. MovingAComputerFile-Metaphorically

The collection of all events in which an instance of #$SoftwareAgent converts information input by an interactive user into a form which can be reasoned with by the system. interpreting program user input InterpretingProgramUserInput

EMailReceiving The collection of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViADZwpEbGdrcN5Y29ycA" class="cyc_term">Event</a>s in which an e-mail message is pulled down from a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv1lRdJwpEbGdrcN5Y29ycA" class="cyc_term">MailServer_Network</a> by the recipient's <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv2oLopwpEbGdrcN5Y29ycA" class="cyc_term">EMailClientProgram</a>. receiving e-mail

A collection of actions performed by computers. In each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r6hdz8bxBEdaD8QCgyeeBIg" class="cyc_term">InterfacingBetweenComputerDeviceAndOS</a>, a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVirAZwpEbGdrcN5Y29ycA" class="cyc_term">DeviceDriverProgram</a> interfaces between some piece of computer hardware and the operating system; permitting the latter to manipulate the former in a standard way. interfacing between computer device and OS InterfacingBetweenComputerDeviceAndOS

IP discovery scan A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rZRQyWhO3QdiZBM3niRcXaQ" class="cyc_term">PacketScanningAComputationalSystem</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rVtRXshO_Qdibq914FGs2XQ" class="cyc_term">IPDiscoveryScan</a> is a scan of a computational system performed with the goal of determining whether or not certain IP addresses are active. Typically, a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rpSLOpArSEdaQqAABAxv-7A" class="cyc_term">PingCommandProgram</a> is used. IPDiscoveryScan

ModifyingAFileInPlace modifying a file in place A collection of actions done by computers on files. In each instance of this collection, a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvrgHFpwpEbGdrcN5Y29ycA" class="cyc_term">ComputerFileCopy</a> is modified in place. If a file is modified in this way, its low-level attributes like its size, the disk sectors (or memory region, etc.) it occupies, etc. must all remain the same.

LoggingInToAComputerProgram login A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvlkpTZwpEbGdrcN5Y29ycA" class="cyc_term">AuthenticationEvent</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rmcNycCbDQdmCnrKwBWqLcg" class="cyc_term">LoggingInToAComputerProgram</a> is an event in which a computeruser authenticates himself or herself to a running computer program. Typically the authentication involves checking a username/password combination entered by the computer user.

accessing a file The collection of actions done by computers in which a computer reads information from a file. AccessingAFile

enforcing A database referential integrity constraint <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwwjQqOBOEdqAAAACs6hO_g" class="cyc_term">EnforcingADatabaseReferentialIntegrityConstraint</a> is the collection of all events in which a database management system enforces a referential integrity constraint that is imposed upon one or more fields in a database. It is faceted by <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rw3Z_1uBOEdqAAAACs6hO_g" class="cyc_term">DatabaseReferentialIntegrityConstraintType</a>. EnforcingADatabaseReferentialIntegrityConstraint

<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4ra5_OsQCDEdeEDgCgyeeBIg" class="cyc_term">PacketSniffing</a> is the collection of all events where packets, which are sent over the Internet, are examined and information is extracted from them. packet sniffing PacketSniffing

copying a file A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvtHXDJwpEbGdrcN5Y29ycA" class="cyc_term">AccessingAFile_ReadOnly</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwKGcipwpEbGdrcN5Y29ycA" class="cyc_term">CreatingAFile</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWYG5pwpEbGdrcN5Y29ycA" class="cyc_term">IBTCopying</a>. In each instance of this collection a computer reads a file and creates a new file with the same contents. Immediately after the event, the original file and the new file will contain exactly the same information. The two files may be stored on the same or different storage media. Notable specializations of this collection include <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvu41-ZwpEbGdrcN5Y29ycA" class="cyc_term">UploadingAFile</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwGRHKpwpEbGdrcN5Y29ycA" class="cyc_term">DownloadingAFile</a>. See also <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv73W3ZwpEbGdrcN5Y29ycA" class="cyc_term">MovingAComputerFile_CopyingAndDeleting</a>. CopyingAComputerFile

emulation Emulation A collection of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViADZwpEbGdrcN5Y29ycA" class="cyc_term">Event</a>s; a specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj8AZwpEbGdrcN5Y29ycA" class="cyc_term">ComputerProcessRunning</a>. In every instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv0wUyZwpEbGdrcN5Y29ycA" class="cyc_term">Emulation</a>, one computer system performs in exactly the same way (although perhaps not at the same speed) as another system of a different type. The emulator may consist solely of software, or be a combination of software and hardware. See also <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvvJde5wpEbGdrcN5Y29ycA" class="cyc_term">EmulatorProgram</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvaYx6JwpEbGdrcN5Y29ycA" class="cyc_term">EmulatorHardware</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwNBKb5wpEbGdrcN5Y29ycA" class="cyc_term">emulatesType</a>.

computer network traffic monitoring A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViLSJwpEbGdrcN5Y29ycA" class="cyc_term">ProgramAction</a> -- the collection of all events in which computer network traffic is monitored by some program designed for that purpose. ComputerNetworkTrafficMonitoring

CommunicatingByTelnet <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViexZwpEbGdrcN5Y29ycA" class="cyc_term">Communicating</a> that occurs through using the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvxNZKpwpEbGdrcN5Y29ycA" class="cyc_term">TelnetProtocol</a>. communicating by telnet

system overload This is the collection of all events in which a computer system suffers some kind of malfunction due to an excessive burden placed on its computing resources. SystemOverload

ProgramInterfacing program interfacing In each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r6hfCELxBEdaD8QCgyeeBIg" class="cyc_term">ProgramInterfacing</a>, a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOxZwpEbGdrcN5Y29ycA" class="cyc_term">InterfaceProgram</a> is used to interface with another program; permitting a user to manipulate the latter in a standard way.

moving a computer file MovingAComputerFile-CopyingAndDeleting A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwQr2aJwpEbGdrcN5Y29ycA" class="cyc_term">FileOperation</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOtpwpEbGdrcN5Y29ycA" class="cyc_term">GeneralizedTransfer</a>. In each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv73W3ZwpEbGdrcN5Y29ycA" class="cyc_term">MovingAComputerFile_CopyingAndDeleting</a>, a computer reads a file, creates a new file with the same contents in a different physical location (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvzyGRpwpEbGdrcN5Y29ycA" class="cyc_term">CopyingAComputerFile</a>) and then deletes the original file (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv-9WepwpEbGdrcN5Y29ycA" class="cyc_term">DeletingAFile</a>). For events in which a computer file is only metaphoricallyI> moved, see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rZibjyI2WQdiVk_xcnOSl5w" class="cyc_term">MovingAComputerFile_Metaphorically</a>.

AccessingAFile-ReadOnly accessing a read only file The collection of actions done by computers in which a computer reads information from a file without modifying the file.

A collection of actions done by computers on files. In each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rQ2aGsbrDEdaD7wCgyeeBIg" class="cyc_term">RippingACompactDisk</a>, a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvjsMTpwpEbGdrcN5Y29ycA" class="cyc_term">CDRipper</a> program converts digital audio from a CompactDisc-Audio into computer files (usually WAVFiles). ripping A compact disk RippingACompactDisk

CreatingAFile <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwKGcipwpEbGdrcN5Y29ycA" class="cyc_term">CreatingAFile</a> is the collection of actions done by computers to generate instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvrgHFpwpEbGdrcN5Y29ycA" class="cyc_term">ComputerFileCopy</a>. In each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwKGcipwpEbGdrcN5Y29ycA" class="cyc_term">CreatingAFile</a>, a computer stores information on an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjyH5wpEbGdrcN5Y29ycA" class="cyc_term">InformationStorageMedia</a>. computer file creation

computer crashing ComputerCrashing An instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rzJQyqGkeEdaAAAABAxv-7A" class="cyc_term">ComputerActivityType</a> and a specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjRLZwpEbGdrcN5Y29ycA" class="cyc_term">ChangingDeviceState</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwSCjMpwpEbGdrcN5Y29ycA" class="cyc_term">PerformanceDegradation_Computer</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjkXZwpEbGdrcN5Y29ycA" class="cyc_term">ComputerCrashing</a> is an event in which a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjXzZwpEbGdrcN5Y29ycA" class="cyc_term">Computer</a>, often unexpectedly, loses its ability to function properly. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjkXZwpEbGdrcN5Y29ycA" class="cyc_term">ComputerCrashing</a> does not include events in which a computer shuts down by following a program provided for the purpose of carefully shutting it down. A user may, however, intentionally crash a computer system. Often an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjkXZwpEbGdrcN5Y29ycA" class="cyc_term">ComputerCrashing</a> will have multiple instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rywKbCOX9QdaPsb4-z5qOsw" class="cyc_term">ComputerProcessCrashing</a> as <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViQmZwpEbGdrcN5Y29ycA" class="cyc_term">subEvents</a>.

A collection of actions done by computers on files. In each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvaFsAZwpEbGdrcN5Y29ycA" class="cyc_term">SavingAFile</a>, a computer writes the contents of a file it has in its <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVitYZwpEbGdrcN5Y29ycA" class="cyc_term">ComputerMemory</a> (usually in its <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkA_ZwpEbGdrcN5Y29ycA" class="cyc_term">RAM</a>) to a long-term, computer-readable storage medium like a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjEJ5wpEbGdrcN5Y29ycA" class="cyc_term">ComputerDisk</a>. SavingAFile saving

banner scan BannerScan A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rZRQyWhO3QdiZBM3niRcXaQ" class="cyc_term">PacketScanningAComputationalSystem</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rbC1TUhO_QdiGG56DCH1G8g" class="cyc_term">BannerScan</a> is a scan of a computational system performed with the intent of determining which particular processes are running by examining the banners they produce when prompted.

alerting user to operational fault AlertingUserToOperationalFault The collection of all instances of #$ProvidingSystemStatusInformationToUser in which the information provided is about an operational fault of the system and in which an out-of-the-ordinary output is generated to draw the attention of the user to the information. Flashing screen regions, other flashing lights, sound output, and tactile response on input devices in continuous use are all such methods. Instances of #$ProvidingContinuousSystemStatusInformationToUser in which the status indicator changes to mark a fault, but in no way calls attention to itself do not fall in this collection. Changing the color of a screen region or output light may or may not fall within this collection depending upon the ergonomics of the situation. Informing the user of an operational fault upon request for current status would not be an instance of this collection.

Computers transferring information. This is not a communicating event, since it doesn't necessarily involve transfer of information into or out of agents' heads. CommunicatingBetweenComputers networking

<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rsstm7OBOEdqAAAACs6hO_g" class="cyc_term">ModifyingARecordInADatabase</a> is the collection of all events in which an agent (human or computer) modifies (inserts, updates, or deletes) a record in a database. ModifyingARecordInADatabase modifying A record in A database

modifying a file A collection of actions done by computers on files. In each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvjMHfZwpEbGdrcN5Y29ycA" class="cyc_term">ModifyingAFile</a>, a computer reads a file, modifies it, creates a new file with the new contents in a different location, and then deletes the original file. It is possible that no information from the original file survives in the modified copy. ModifyingAFile

The collection of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViADZwpEbGdrcN5Y29ycA" class="cyc_term">Event</a>s in which information packets from a network are filtered; often for security purposes. NetworkPacketFiltering network packet filtering

porting PortingAComputerProgram The collection of events in which an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwJxiRJwpEbGdrcN5Y29ycA" class="cyc_term">ComputerProgram_CW</a> which was written to run on a particular kind of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjXzZwpEbGdrcN5Y29ycA" class="cyc_term">Computer</a> is altered in order to be able to run on another kind of machine.

download A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvzyGRpwpEbGdrcN5Y29ycA" class="cyc_term">CopyingAComputerFile</a>. In each instance of this collection, a computer copies a file from a file system that it is <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkKt5wpEbGdrcN5Y29ycA" class="cyc_term">remotelyConnectedTo</a> over a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVirUZwpEbGdrcN5Y29ycA" class="cyc_term">ComputerNetwork</a> to a local <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjEJ5wpEbGdrcN5Y29ycA" class="cyc_term">ComputerDisk</a> or other long-term storage device. DownloadingAFile

ComputerKeyboardTyping computer keyboard typing Typing using a computer or word processor keyboard.

The collection of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViADZwpEbGdrcN5Y29ycA" class="cyc_term">Event</a>s in which information packets from a network are received and forwarded toward their proper destination. network packet routing NetworkPacketRouting

packet scan PacketScanningAComputationalSystem A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViLSJwpEbGdrcN5Y29ycA" class="cyc_term">ProgramAction</a>. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rZRQyWhO3QdiZBM3niRcXaQ" class="cyc_term">PacketScanningAComputationalSystem</a> is the collection of all scans on computers or computer networks. Important specializations include <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rVtRXshO_Qdibq914FGs2XQ" class="cyc_term">IPDiscoveryScan</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwPae0JwpEbGdrcN5Y29ycA" class="cyc_term">PortScan</a>, and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rbC1TUhO_QdiGG56DCH1G8g" class="cyc_term">BannerScan</a>.

A collection of events. In an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv5XTApwpEbGdrcN5Y29ycA" class="cyc_term">ConnectingToAComputerNetwork</a>, a user gains communications access to a computer network, either locally, or via a dial-up connection. ConnectingToAComputerNetwork connecting to A computer network

deleting A collection of actions done by computers on files. In each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv-9WepwpEbGdrcN5Y29ycA" class="cyc_term">DeletingAFile</a>, a computer changes the directory information on a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjEJ5wpEbGdrcN5Y29ycA" class="cyc_term">ComputerDisk</a> or other long-term storage medium so that the file that is the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi65pwpEbGdrcN5Y29ycA" class="cyc_term">objectActedOn</a> in the event is no longer represented as being stored on that disk, etc. Furthermore, the space on the disk that was used to store the file immediately before the event is designated immediately after the event as available to be written to. Note that in an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv-9WepwpEbGdrcN5Y29ycA" class="cyc_term">DeletingAFile</a> it is necessary only that the disk directory be changed. The actual encoding of the file itself may or may not be changed. Thus a deleted file is sometimes recoverable. DeletingAFile

clever programming Hacking A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjuvJwpEbGdrcN5Y29ycA" class="cyc_term">ProgrammingAComputer</a>, comprising particularly clever or expert programming feats. Contrary to popular usage of the word "hacking", this constant is not intended to refer to acts of breaking into computer systems (for that, see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv0hea5wpEbGdrcN5Y29ycA" class="cyc_term">PenetratingAComputerNetwork</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvv-fq5wpEbGdrcN5Y29ycA" class="cyc_term">AttackByComputerOperation</a>).

A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwKWcUJwpEbGdrcN5Y29ycA" class="cyc_term">AccessingAFile</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rNQg8FH-QQdmdhNklnF0aqg" class="cyc_term">OpeningAFile</a> is an event in which a computer file is opened by another program, such as, for example, when Microsoft Word is used to open a ".doc" file, or when an email client program is used to display an email. OpeningAFile opening A file

FormattingADisk A collection of actions performed by computers. In each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjD5ZwpEbGdrcN5Y29ycA" class="cyc_term">FormattingADisk</a>, a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjXzZwpEbGdrcN5Y29ycA" class="cyc_term">Computer</a> prepares an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjEJ5wpEbGdrcN5Y29ycA" class="cyc_term">ComputerDisk</a> to have data written to it under a particular file system. After the event, the disk will be recognized by computers that use the file system for which the disk was formatted as a readable, blank disk. format

ComputerActivityType An instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViA4pwpEbGdrcN5Y29ycA" class="cyc_term">SiblingDisjointCollectionType</a>. Each instance of this (second-order) collection is a subcollection of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViFUJwpEbGdrcN5Y29ycA" class="cyc_term">ComputerActivity</a> all of whose instances are a particular and distinct type of activity. Examples include <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvdMvgJwpEbGdrcN5Y29ycA" class="cyc_term">EMailSending</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjYgJwpEbGdrcN5Y29ycA" class="cyc_term">BootingAComputer</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjkXZwpEbGdrcN5Y29ycA" class="cyc_term">ComputerCrashing</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvm2Dx5wpEbGdrcN5Y29ycA" class="cyc_term">OnlineChat</a>. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvv-fq5wpEbGdrcN5Y29ycA" class="cyc_term">AttackByComputerOperation</a> is not an instance as it is not distinct enough. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvzTVp5wpEbGdrcN5Y29ycA" class="cyc_term">EnteringAComputerPassword</a> is an instance, but <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwOH4i5wpEbGdrcN5Y29ycA" class="cyc_term">EnteringADomainAdministratorPassword</a> is not as it is too specific. This collection is an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViA4pwpEbGdrcN5Y29ycA" class="cyc_term">SiblingDisjointCollectionType</a> because it is assumed that computer-related activities are analysed fine-grainedly enough that if a putative instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViFUJwpEbGdrcN5Y29ycA" class="cyc_term">ComputerActivity</a> would fall under two sibling <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rzJQyqGkeEdaAAAABAxv-7A" class="cyc_term">ComputerActivityType</a>s, it should be analysed as two events. computer activity type 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 <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 DurativeEventType A collection of collections. If TYPE is an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwNyXxJwpEbGdrcN5Y29ycA" class="cyc_term">DurativeEventType</a>, each instance of TYPE is a "durative event" extended through time, i.e., it endures continuously between its starting and ending points, and such points are not simultaneous. As an example, writing a letter is a durative event type, since an event of this type will (except in "degenerate" cases) have a distinct starting point, a period of time in the middle during which writing occurs, and an end point at which the letter is written. By contrast, winning a prize is an instantaneous change: up to the moment the event takes place, you don't have the prize, after that you do. Granted, the awarding of the prize might in fact have a physical duration, but from a conceptual or logical point of view it might as well have none. If one thinks of events as the occurrence of "changes", one may regard durative events as changes that intrinsically occupy a continuous, non-zero chunk of time, and non-durative events (for which see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv4unQpwpEbGdrcN5Y29ycA" class="cyc_term">PunctualEventType</a>) as instantaneous changes. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv9vChJwpEbGdrcN5Y29ycA" class="cyc_term">CumulativeEventType</a> is a proper specialization of this collection, because the cumulativity property (see the salient assertion for <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv9vChJwpEbGdrcN5Y29ycA" class="cyc_term">CumulativeEventType</a>) implies that all process types can have temporal extension. Naturally, many <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwNyXxJwpEbGdrcN5Y29ycA" class="cyc_term">DurativeEventType</a>s are not cumulative, but rather <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv48ocpwpEbGdrcN5Y29ycA" class="cyc_term">AccomplishmentType</a>s. type of durative event 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 ComputerActivityType An instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViA4pwpEbGdrcN5Y29ycA" class="cyc_term">SiblingDisjointCollectionType</a>. Each instance of this (second-order) collection is a subcollection of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViFUJwpEbGdrcN5Y29ycA" class="cyc_term">ComputerActivity</a> all of whose instances are a particular and distinct type of activity. Examples include <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvdMvgJwpEbGdrcN5Y29ycA" class="cyc_term">EMailSending</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjYgJwpEbGdrcN5Y29ycA" class="cyc_term">BootingAComputer</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjkXZwpEbGdrcN5Y29ycA" class="cyc_term">ComputerCrashing</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvm2Dx5wpEbGdrcN5Y29ycA" class="cyc_term">OnlineChat</a>. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvv-fq5wpEbGdrcN5Y29ycA" class="cyc_term">AttackByComputerOperation</a> is not an instance as it is not distinct enough. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvzTVp5wpEbGdrcN5Y29ycA" class="cyc_term">EnteringAComputerPassword</a> is an instance, but <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwOH4i5wpEbGdrcN5Y29ycA" class="cyc_term">EnteringADomainAdministratorPassword</a> is not as it is too specific. This collection is an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViA4pwpEbGdrcN5Y29ycA" class="cyc_term">SiblingDisjointCollectionType</a> because it is assumed that computer-related activities are analysed fine-grainedly enough that if a putative instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViFUJwpEbGdrcN5Y29ycA" class="cyc_term">ComputerActivity</a> would fall under two sibling <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rzJQyqGkeEdaAAAABAxv-7A" class="cyc_term">ComputerActivityType</a>s, it should be analysed as two events. computer activity type