]> 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. top-topic Top-Topic

configuration Configuration A specialization of both <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvh5TfJwpEbGdrcN5Y29ycA" class="cyc_term">StaticSituation</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwS68M5wpEbGdrcN5Y29ycA" class="cyc_term">SpatialThing_Localized</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjuI5wpEbGdrcN5Y29ycA" class="cyc_term">Configuration</a> is a static situation consisting of two or more <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj27ZwpEbGdrcN5Y29ycA" class="cyc_term">PartiallyTangible</a> things of certain types standing in a certain type of spatial relationship (or set of relationships). This (set of) spatial relationship(s) "characterizes" the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjuI5wpEbGdrcN5Y29ycA" class="cyc_term">Configuration</a>'s type in the sense that any group of objects of the appropriate types standing in that relationship (or those relationships) correspond to a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjuI5wpEbGdrcN5Y29ycA" class="cyc_term">Configuration</a> of that type; and each of these objects, in turn, is said to be "configured" (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvjz-VJwpEbGdrcN5Y29ycA" class="cyc_term">configuredObjects</a>) in the (individual) <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjuI5wpEbGdrcN5Y29ycA" class="cyc_term">Configuration</a>. For example, a knot configuration might correspond to a particular intertwining of end-segments of two <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj1gZwpEbGdrcN5Y29ycA" class="cyc_term">CordlikeObject</a>s, or to the intertwining of several segments of a single <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj1gZwpEbGdrcN5Y29ycA" class="cyc_term">CordlikeObject</a>. For configurations like the latter, whose characterizing relationship(s) hold between different parts of a single salient object, see the specialization <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv6BkqZwpEbGdrcN5Y29ycA" class="cyc_term">ConfigurationOfComplexObject</a>. Note that a static situation involving an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAB5wpEbGdrcN5Y29ycA" class="cyc_term">Agent_PartiallyTangible</a> might be a configuration, but only so long as it's just the agent's spatial relationship(s) to other partially tangibles that matters (see e.g. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVieCZwpEbGdrcN5Y29ycA" class="cyc_term">WearingSomething</a>); static situations in which an agent's agency or sentience is crucial, on the other hand, are not configurations (cf. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwIV89pwpEbGdrcN5Y29ycA" class="cyc_term">InterAgentSituation</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWbjKJwpEbGdrcN5Y29ycA" class="cyc_term">InterAgentSituation_TwoAgent</a>).

Intangible intangible The collection of things that are not physical -- are not made of, or encoded in, matter. Every <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAzJwpEbGdrcN5Y29ycA" class="cyc_term">Collection</a> is an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjjo5wpEbGdrcN5Y29ycA" class="cyc_term">Intangible</a> (even if its instances are tangible), and so are some <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjaApwpEbGdrcN5Y29ycA" class="cyc_term">Individual</a>s. Caution: do not confuse `tangibility' with `perceivability' -- humans can perceive light even though it's intangible--at least in a sense. For more on this issue, see the relevant #$cyclistNotes.

cotemporalSubEvents The predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkGvpwpEbGdrcN5Y29ycA" class="cyc_term">cotemporalSubEvents</a> is used to relate an event to some sub-event which has the same duration as the whole event, but doesn't necessarily include everything that happens in the whole event. (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkGvpwpEbGdrcN5Y29ycA" class="cyc_term">cotemporalSubEvents</a> WHOLE PART) means that WHOLE and PART are cotemporal events (i.e., they have the same exact duration), and PART is a component of WHOLE. For example, a particular instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rdp8N1ocJQdicUre0IqdPPg" class="cyc_term">RainStormAsEvent</a> may have distinguishable <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkGvpwpEbGdrcN5Y29ycA" class="cyc_term">cotemporalSubEvents</a> for (1) raining and (2) wind blowing, and an instance of swimming <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP3yxJwpEbGdrcN5Y29ycA" class="cyc_term">Backstroke</a> has separable events for (1) kicking and (2) arm motion throughout the swimming. See also <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjWz5wpEbGdrcN5Y29ycA" class="cyc_term">cotemporal</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViQmZwpEbGdrcN5Y29ycA" class="cyc_term">subEvents</a>. Cotemporal Sub Events

A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVirnZwpEbGdrcN5Y29ycA" class="cyc_term">ObjectType</a> (q.v.) whose instances are all and only those collections that are temporally object-like. A collection <code>COL</code> is temporally object-like just in case it generally holds that any proper purely temporal parts (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWn4OZwpEbGdrcN5Y29ycA" class="cyc_term">timeSlices</a>) of an instance of <code>COL</code> is not itself an instance of <code>COL</code>. More precisely, a collection <code>COL</code> is an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViq35wpEbGdrcN5Y29ycA" class="cyc_term">TemporalObjectType</a> just in case it satisfies the following: For any distinct <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>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWn4OZwpEbGdrcN5Y29ycA" class="cyc_term">timeSlices</a> OBJ1 OBJ2)</code>, then not <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViBBJwpEbGdrcN5Y29ycA" class="cyc_term">isa</a> OBJ2 COL)</code>. For example, none of the proper time-slices of a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjyV5wpEbGdrcN5Y29ycA" class="cyc_term">CalendarYear</a> is itself a calendar year. Likewise for <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViYBpwpEbGdrcN5Y29ycA" class="cyc_term">TakingAStep</a>. So <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjyV5wpEbGdrcN5Y29ycA" class="cyc_term">CalendarYear</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViYBpwpEbGdrcN5Y29ycA" class="cyc_term">TakingAStep</a> are both instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViq35wpEbGdrcN5Y29ycA" class="cyc_term">TemporalObjectType</a>. Conversely, a proper time-slice of a given <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVisWZwpEbGdrcN5Y29ycA" class="cyc_term">Date</a> might itself be a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVisWZwpEbGdrcN5Y29ycA" class="cyc_term">Date</a> (e.g. an hour has minutes and seconds as time-slices); so <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVisWZwpEbGdrcN5Y29ycA" class="cyc_term">Date</a> is not a temporal-object-type. See <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVitN5wpEbGdrcN5Y29ycA" class="cyc_term">TemporalStuffType</a> for the disjoint notion of being temporally stuff-like. TemporalObjectType temporal object type

distribution DistributionEvent A specialization of both <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvrOVYpwpEbGdrcN5Y29ycA" class="cyc_term">PurposefulPhysicalAction</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvcFjVpwpEbGdrcN5Y29ycA" class="cyc_term">TransferOut</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj9a5wpEbGdrcN5Y29ycA" class="cyc_term">DistributionEvent</a> is an event in which tangible objects are distributed from a source to various destinations via some distribution network.

MovementEvent A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOtpwpEbGdrcN5Y29ycA" class="cyc_term">GeneralizedTransfer</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvjKor5wpEbGdrcN5Y29ycA" class="cyc_term">MovementOrShapeChangeEvent</a> (qq.v.). This is the most general collection of physical movements. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEAZwpEbGdrcN5Y29ycA" class="cyc_term">MovementEvent</a> is an event in which at least one object (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEjpwpEbGdrcN5Y29ycA" class="cyc_term">objectMoving</a>) either translates some distance or moves from one rotational orientation to another, relative to a frame of reference that is not part of the translating/rotating object. The movement in question might be periodic or not, continuous or not. Notable specializations of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEAZwpEbGdrcN5Y29ycA" class="cyc_term">MovementEvent</a> include <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv4GokJwpEbGdrcN5Y29ycA" class="cyc_term">Translocation</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjLCpwpEbGdrcN5Y29ycA" class="cyc_term">Movement_Rotation</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWWHKZwpEbGdrcN5Y29ycA" class="cyc_term">Movement_Periodic</a>, and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViQzZwpEbGdrcN5Y29ycA" class="cyc_term">MovementProcess</a>. movement

postSituation Post Situation (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWHlf5wpEbGdrcN5Y29ycA" class="cyc_term">postSituation</a> EVENT SIT) means that SIT is a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvh5TfJwpEbGdrcN5Y29ycA" class="cyc_term">StaticSituation</a> that begins after the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViADZwpEbGdrcN5Y29ycA" class="cyc_term">Event</a> EVENT ends, and that SIT is directly (usually causally) related to EVENT. See <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi76ZwpEbGdrcN5Y29ycA" class="cyc_term">postEvents</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWer2ZwpEbGdrcN5Y29ycA" class="cyc_term">preSituation</a> for related predicates.

Time Slices A <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViDSpwpEbGdrcN5Y29ycA" class="cyc_term">TemporalPartPredicate</a> and a specialization of both <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAGZwpEbGdrcN5Y29ycA" class="cyc_term">temporallySubsumes</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj7bpwpEbGdrcN5Y29ycA" class="cyc_term">parts</a> (qq.v.) that relates a temporal thing to any of its "pure" temporal parts. (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWn4OZwpEbGdrcN5Y29ycA" class="cyc_term">timeSlices</a> TEMP SLICE) means that SLICE is a part of TEMP that is distinguished from TEMP purely in terms of its temporal extent, which is subsumed by the temporal extent of TEMP itself. In other words, SLICE is "everything there is to" TEMP during the particular <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAw5wpEbGdrcN5Y29ycA" class="cyc_term">TimeInterval</a> that SLICE occupies. For example, today's noon hour has the interval from 12:00 noon to 12:30 p.m. today as one of its time-slices; the first act of a particular performance of "Hamlet" is a time-slice of that performance of the whole play. There is no general agreement on exactly what types of temporal things have time-slices. Still, a few generalizations can be made. All and only time-slices of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAw5wpEbGdrcN5Y29ycA" class="cyc_term">TimeInterval</a>s are themselves <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAw5wpEbGdrcN5Y29ycA" class="cyc_term">TimeInterval</a>s. Indeed, one time interval temporally subsumes another if and only if the latter is a time-slice of the former. All and only time-slices of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvYjIS5wpEbGdrcN5Y29ycA" class="cyc_term">Situation</a>s are themselves <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvYjIS5wpEbGdrcN5Y29ycA" class="cyc_term">Situation</a>s. It is controversial whether any temporal things besides pure time intervals and temporal situations -- such as ordinary tangible objects -- have time-slices. timeSlices

TransferOut A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOtpwpEbGdrcN5Y29ycA" class="cyc_term">GeneralizedTransfer</a>. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvcFjVpwpEbGdrcN5Y29ycA" class="cyc_term">TransferOut</a> includes all instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOtpwpEbGdrcN5Y29ycA" class="cyc_term">GeneralizedTransfer</a> in which some object plays the role of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv9UIFZwpEbGdrcN5Y29ycA" class="cyc_term">from_Generic</a>, but in which there may or may not be any object playing the role of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwAyrYZwpEbGdrcN5Y29ycA" class="cyc_term">to_Generic</a>. At the start of a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvcFjVpwpEbGdrcN5Y29ycA" class="cyc_term">TransferOut</a>, the object playing the role of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rDbKaOuVmQdeTKaYmT-4jgg" class="cyc_term">transferredThing</a> is 'located' at the object playing the role of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv9UIFZwpEbGdrcN5Y29ycA" class="cyc_term">from_Generic</a>. The collection <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvcFjVpwpEbGdrcN5Y29ycA" class="cyc_term">TransferOut</a> includes, among other things, all instances of the collections <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvtAG-JwpEbGdrcN5Y29ycA" class="cyc_term">Emission</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWQcoZwpEbGdrcN5Y29ycA" class="cyc_term">LosingUserRights</a>, and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj9a5wpEbGdrcN5Y29ycA" class="cyc_term">DistributionEvent</a>. Negative examples of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvcFjVpwpEbGdrcN5Y29ycA" class="cyc_term">TransferOut</a> include some instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjuo5wpEbGdrcN5Y29ycA" class="cyc_term">AppropriatingSomething</a> (when there is no previous owner) and some instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjcMpwpEbGdrcN5Y29ycA" class="cyc_term">Hearing</a> (when the sounds may come from various unspecified locations). transfer event with well-defined from-location

A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOtpwpEbGdrcN5Y29ycA" class="cyc_term">GeneralizedTransfer</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVifB5wpEbGdrcN5Y29ycA" class="cyc_term">InformationTransferEvent</a> is an event in which information is transferred from a source (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV5PA5wpEbGdrcN5Y29ycA" class="cyc_term">informationOrigin</a>) to one or more destinations (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVipxZwpEbGdrcN5Y29ycA" class="cyc_term">informationDestination</a>), where the source and the various destinations are either intelligent agents or <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvkNufpwpEbGdrcN5Y29ycA" class="cyc_term">InformationBearingThing</a>s (IBTs). Examples include reading a book (transfer of information from the book to the reader), saying something to someone (transfer of information from the speaker to the listener), machine translation (transfer of information from an encoded IBT in the source language to an encoded IBT in the target language), OCR scanning (transfer of information from a visual information source to another IBT in a different format), carving initials in a tree (transfer of information from an agent to an IBT), and making a speech (transfer of information from an agent to other agents). See also the specialization <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvucXhJwpEbGdrcN5Y29ycA" class="cyc_term">InformationTransferPhysicalEvent</a>. InformationTransferEvent information transfer

Emission A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvcFjVpwpEbGdrcN5Y29ycA" class="cyc_term">TransferOut</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvtAG-JwpEbGdrcN5Y29ycA" class="cyc_term">Emission</a> is an event in which something `comes out' of a source, where the source in question causally contributes to that thing's `coming out' (e.g., the source is a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjX_pwpEbGdrcN5Y29ycA" class="cyc_term">providerOfMotiveForce</a>). The source of the emission is indicated with the predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjc8ZwpEbGdrcN5Y29ycA" class="cyc_term">emitter</a>. If the thing which `comes out' is an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj27ZwpEbGdrcN5Y29ycA" class="cyc_term">PartiallyTangible</a>, then the event belongs to a more specific collection, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjmyJwpEbGdrcN5Y29ycA" class="cyc_term">EmittingAnObject</a>. If an emission is the first sub-event of an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwQCA9ZwpEbGdrcN5Y29ycA" class="cyc_term">WavePropagation</a>, then the emission belongs to the more specialized collection, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvr582pwpEbGdrcN5Y29ycA" class="cyc_term">EmittingAWave</a>. emitting

HumanActivity human activity A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViNqpwpEbGdrcN5Y29ycA" class="cyc_term">AnimalActivity</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViN65wpEbGdrcN5Y29ycA" class="cyc_term">HumanActivity</a> is a spatially-localized action each of whose "doers" (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP1HmJwpEbGdrcN5Y29ycA" class="cyc_term">doneBy</a>) is either a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rIcwFloGUQdeMlsOWYLFB2w" class="cyc_term">HomoSapiens</a> or a group of humans (i.e. a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjmoJwpEbGdrcN5Y29ycA" class="cyc_term">Group</a> all of whose members are <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rIcwFloGUQdeMlsOWYLFB2w" class="cyc_term">HomoSapiens</a> or groups of humans).

A specialization of both <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVioQZwpEbGdrcN5Y29ycA" class="cyc_term">Action</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViGFZwpEbGdrcN5Y29ycA" class="cyc_term">AtLeastPartiallyMentalEvent</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVieP5wpEbGdrcN5Y29ycA" class="cyc_term">PurposefulAction</a> is an action consciously, volitionally, and purposefully done by (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVipYpwpEbGdrcN5Y29ycA" class="cyc_term">performedBy</a>) at least one actor. intentional action PurposefulAction

A collection of collections. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWXYgJwpEbGdrcN5Y29ycA" class="cyc_term">ExistingObjectType</a> is a specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj27ZwpEbGdrcN5Y29ycA" class="cyc_term">PartiallyTangible</a> (q.v.). Moreover, each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWXYgJwpEbGdrcN5Y29ycA" class="cyc_term">ExistingObjectType</a> is a collection that is temporally stuff-like (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVitN5wpEbGdrcN5Y29ycA" class="cyc_term">TemporalStuffType</a>) but physically-spatially object-like (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVirnZwpEbGdrcN5Y29ycA" class="cyc_term">ObjectType</a>) -- i.e. object-like with respect to some physical-spatial part-whole predicate (e.g. some specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r8a2smPXcQdiEoJhcx65EiQ" class="cyc_term">properPhysicalDecompositions</a>). Consider the collection <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwJaXepwpEbGdrcN5Y29ycA" class="cyc_term">BookCopy</a>. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwJaXepwpEbGdrcN5Y29ycA" class="cyc_term">BookCopy</a> is a specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj27ZwpEbGdrcN5Y29ycA" class="cyc_term">PartiallyTangible</a>. Further, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwJaXepwpEbGdrcN5Y29ycA" class="cyc_term">BookCopy</a> is temporally stuff-like: any one of the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWn4OZwpEbGdrcN5Y29ycA" class="cyc_term">timeSlices</a> of a given copy <code>COPY</code> of (say) "Moby Dick" is still a copy of "Moby Dick". (Most collections of tangible objects are temporally stuff-like in this way.) But <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwJaXepwpEbGdrcN5Y29ycA" class="cyc_term">BookCopy</a> is spatially object-like: if we take a scalpel and slice <code>COPY</code> into ten pieces, each piece is not a copy of "Moby Dick". So <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwJaXepwpEbGdrcN5Y29ycA" class="cyc_term">BookCopy</a> is an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWXYgJwpEbGdrcN5Y29ycA" class="cyc_term">ExistingObjectType</a>. See also <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVir35wpEbGdrcN5Y29ycA" class="cyc_term">StuffType</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVny6pwpEbGdrcN5Y29ycA" class="cyc_term">ExistingStuffType</a>. ExistingObjectType type of object

thing transferred The predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWekBZwpEbGdrcN5Y29ycA" class="cyc_term">transferredObject</a> is used to identify the object whose external relationships change in some event considered generically as a "transfer". <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWekBZwpEbGdrcN5Y29ycA" class="cyc_term">transferredObject</a> TRANSFER OBJ)</code> means that <code>OBJ</code> is being moved, transferred, or exchanged in the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOtpwpEbGdrcN5Y29ycA" class="cyc_term">GeneralizedTransfer</a> event <code>TRANSFER</code>. Note that in general, and if possible, it is preferable to use a more specialized instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAKZwpEbGdrcN5Y29ycA" class="cyc_term">ActorSlot</a> than <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWekBZwpEbGdrcN5Y29ycA" class="cyc_term">transferredObject</a> (e.g., <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEjpwpEbGdrcN5Y29ycA" class="cyc_term">objectMoving</a> for physical transfer of an object, or <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj0z5wpEbGdrcN5Y29ycA" class="cyc_term">objectOfPossessionTransfer</a> for an object that changes possession but not necessarily location) in representing ground facts about transfers. transferredObject

Role A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViDzZwpEbGdrcN5Y29ycA" class="cyc_term">ObjectPredicate</a> (q.v.) whose instances relate situations to individuals that are "involved" in them in various ways. As such, each <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAA5wpEbGdrcN5Y29ycA" class="cyc_term">Role</a> has its first argument-place constrained to (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvuItPZwpEbGdrcN5Y29ycA" class="cyc_term">argIsa</a>) instances of some specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvYjIS5wpEbGdrcN5Y29ycA" class="cyc_term">Situation</a>, and its other argument-places constrained to instances of some specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjaApwpEbGdrcN5Y29ycA" class="cyc_term">Individual</a>. Note that the sort of "involvement" a given <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAA5wpEbGdrcN5Y29ycA" class="cyc_term">Role</a> attributes to an individual in a situation might be either active or passive (cf. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP1HmJwpEbGdrcN5Y29ycA" class="cyc_term">doneBy</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi65pwpEbGdrcN5Y29ycA" class="cyc_term">objectActedOn</a>), either central or peripheral (cf. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvXxi65wpEbGdrcN5Y29ycA" class="cyc_term">primaryObjectMoving</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP1do5wpEbGdrcN5Y29ycA" class="cyc_term">assistingAgent</a>), either "physical" or "conceptual" (cf. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEjpwpEbGdrcN5Y29ycA" class="cyc_term">objectMoving</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWUq7JwpEbGdrcN5Y29ycA" class="cyc_term">infoTransferred</a>). Individuals can be "involved" in situations in the relevant way without directly participating in the situations. For example, an agent may be involved in an event which it does not temporally intersect by being affected by it (thus <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwQ_BQpwpEbGdrcN5Y29ycA" class="cyc_term">affectedAgent</a> is an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAA5wpEbGdrcN5Y29ycA" class="cyc_term">Role</a>). Important specializations of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAA5wpEbGdrcN5Y29ycA" class="cyc_term">Role</a> are <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwL4_QpwpEbGdrcN5Y29ycA" class="cyc_term">BinaryRolePredicate</a> and its specialization <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAKZwpEbGdrcN5Y29ycA" class="cyc_term">ActorSlot</a>. role

Collecting gathering things together A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWMZaZwpEbGdrcN5Y29ycA" class="cyc_term">TransferIn</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjcHpwpEbGdrcN5Y29ycA" class="cyc_term">Collecting</a> is an event in which tangible or intangible objects are collected together at a single "place". The objects might come from various sources, and might be gathered via some collection network. Notable specializations of this collection include <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvpe5e5wpEbGdrcN5Y29ycA" class="cyc_term">GroupingObjects</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwBUJ2pwpEbGdrcN5Y29ycA" class="cyc_term">CollectingInformation</a>.

subEvents subevent The most general instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViCxpwpEbGdrcN5Y29ycA" class="cyc_term">SubEventPredicate</a>, this predicate relates a given event to the events that are its parts. <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViQmZwpEbGdrcN5Y29ycA" class="cyc_term">subEvents</a> WHOLE PART)</code> means that <code>PART</code> is a part, or subevent, of <code>WHOLE</code>. Events can be decomposed into subevents events temporally, spatially, and in other ways; see the specializations of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViQmZwpEbGdrcN5Y29ycA" class="cyc_term">subEvents</a> for more on this. For decomposing an event in a purely temporal way, see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwCK6fZwpEbGdrcN5Y29ycA" class="cyc_term">subProcesses</a>.

A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjaApwpEbGdrcN5Y29ycA" class="cyc_term">Individual</a>. This is the collection of all things that have temporal extent or location -- things about which one might sensibly ask "When?". <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAxJwpEbGdrcN5Y29ycA" class="cyc_term">TemporalThing</a> thus contains many kinds of things, including events, physical objects, agreements, and pure intervals of time. Major specializations of this collection are <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi255wpEbGdrcN5Y29ycA" class="cyc_term">SomethingExisting</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvYjIS5wpEbGdrcN5Y29ycA" class="cyc_term">Situation</a>, and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAw5wpEbGdrcN5Y29ycA" class="cyc_term">TimeInterval</a> (qq.v.). Things that are timeless -- such as mathematical sets, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAzJwpEbGdrcN5Y29ycA" class="cyc_term">Collection</a>s, and numbers -- are of course not instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAxJwpEbGdrcN5Y29ycA" class="cyc_term">TemporalThing</a> (cf. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rGfrGRkkIQdeI2O3iJCGV3Q" class="cyc_term">AtemporalThing</a>). thing that exists in time TemporalThing

(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWer2ZwpEbGdrcN5Y29ycA" class="cyc_term">preSituation</a> EVENT SIT) means that the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvh5TfJwpEbGdrcN5Y29ycA" class="cyc_term">StaticSituation</a> SIT holds just prior to the start of the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViADZwpEbGdrcN5Y29ycA" class="cyc_term">Event</a> EVENT, and SIT is directly related to EVENT in some salient way. The required `salience' of the two arguments to each other is difficult to formalize but usually intuitively clearcut. Commonly, SIT and EVENT share many of the same objects involved in various roles, and there is often a causal connection as well. For instance, if SIT is an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjuI5wpEbGdrcN5Y29ycA" class="cyc_term">Configuration</a> (q.v.), then SIT might be somehow `taken apart' by EVENT or might `trigger' EVENT. preSituation Pre Situation

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

The collection of things that either are wholly intangible (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjjo5wpEbGdrcN5Y29ycA" class="cyc_term">Intangible</a>) or have at least one intangible (i.e. immaterial) part (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi2BJwpEbGdrcN5Y29ycA" class="cyc_term">intangibleParts</a>). This includes intangible individuals, such as instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvxwC-ZwpEbGdrcN5Y29ycA" class="cyc_term">Number_General</a> or <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVivo5wpEbGdrcN5Y29ycA" class="cyc_term">Agreement</a>, as well as non-individuals (all of which are intangible), i.e. instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjl_ZwpEbGdrcN5Y29ycA" class="cyc_term">SetOrCollection</a>. It also includes things that have both tangible and intangible components (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj3cZwpEbGdrcN5Y29ycA" class="cyc_term">CompositeTangibleAndIntangibleObject</a>), such as a printed copy of a newspaper (as its information content is intangible) or a person (as her mental states are intangible). partially intangible thing PartiallyIntangible

origin An <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAKZwpEbGdrcN5Y29ycA" class="cyc_term">ActorSlot</a> that is a specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWDKWZwpEbGdrcN5Y29ycA" class="cyc_term">preActors</a> (q.v.). This predicate is used to indicate the starting point of a particular movement from one place to another. <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjiI5wpEbGdrcN5Y29ycA" class="cyc_term">fromLocation</a> MOVE LOC)</code> means that <code>LOC</code> is where some salient moving-object (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEjpwpEbGdrcN5Y29ycA" class="cyc_term">objectMoving</a>) in the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv4GokJwpEbGdrcN5Y29ycA" class="cyc_term">Translocation</a> <code>MOVE</code> is found at the beginning of <code>MOVE</code> and is where it begins this motion. This moving-object might or might not be <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwPusM5wpEbGdrcN5Y29ycA" class="cyc_term">Stationary</a> at <code>LOC</code> at the beginning of <code>MOVE</code>. If <code>MOVE</code> is a single-pathway translation (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVsNyJwpEbGdrcN5Y29ycA" class="cyc_term">Translation_SingleTrajectory</a>), then each of its salient moving-objects is found at <code>LOC</code> when <code>MOVE</code> starts. If <code>MOVE</code> has multiple movers and multiple pathways (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV74r5wpEbGdrcN5Y29ycA" class="cyc_term">Translation_MultiTrajectory</a>), then at least some of the moving-objects can be found at <code>LOC</code> when <code>MOVE</code> starts. If <code>MOVE</code> is a flow (such as a river flowing, a wind blowing, a tornado, a typhoon, some clouds moving, or air filling your lungs when you take a breath; see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEhJwpEbGdrcN5Y29ycA" class="cyc_term">FluidFlow_Translation</a>), then at least some portion of the fluid moving-object can be found at <code>LOC</code> when <code>MOVE</code> starts. See also <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViCe5wpEbGdrcN5Y29ycA" class="cyc_term">motionPathway_Complete</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwPKiKZwpEbGdrcN5Y29ycA" class="cyc_term">pathConnects</a>. fromLocation

A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViADZwpEbGdrcN5Y29ycA" class="cyc_term">Event</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOtpwpEbGdrcN5Y29ycA" class="cyc_term">GeneralizedTransfer</a> is an event in which something (tangible or intangible) is transferred from one 'place' to another. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOtpwpEbGdrcN5Y29ycA" class="cyc_term">GeneralizedTransfer</a> includes changes in physical location, in ownership or possession, transfer of information, and propagation of wave phenomena through space. See also the related predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rDbKaOuVmQdeTKaYmT-4jgg" class="cyc_term">transferredThing</a>, and the specializations of this collection. GeneralizedTransfer transfer

Event event An important specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvYjIS5wpEbGdrcN5Y29ycA" class="cyc_term">Situation</a> and thus also of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjj45wpEbGdrcN5Y29ycA" class="cyc_term">IntangibleIndividual</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rtM0npht0QdiUF94Dipp7Pg" class="cyc_term">TemporallyExistingThing</a> (qq.v). Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViADZwpEbGdrcN5Y29ycA" class="cyc_term">Event</a> is a dynamic situation in which the state of the world changes; each instance is something one would say "happens". Events are intangible because they are changes per se, not tangible objects that effect and undergo changes. Notable specializations of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViADZwpEbGdrcN5Y29ycA" class="cyc_term">Event</a> include <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvjJE4ZwpEbGdrcN5Y29ycA" class="cyc_term">Event_Localized</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjpjZwpEbGdrcN5Y29ycA" class="cyc_term">PhysicalEvent</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVioQZwpEbGdrcN5Y29ycA" class="cyc_term">Action</a>, and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOtpwpEbGdrcN5Y29ycA" class="cyc_term">GeneralizedTransfer</a>. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViADZwpEbGdrcN5Y29ycA" class="cyc_term">Event</a>s should not be confused with <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAw5wpEbGdrcN5Y29ycA" class="cyc_term">TimeInterval</a>s (q.v.). The temporal bounds of events are delineated by time intervals, but in contrast to many events time intervals have no spatial location or extent.

IntangibleExistingThing intangible thing existing stably in time A specialization of both <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjj45wpEbGdrcN5Y29ycA" class="cyc_term">IntangibleIndividual</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi255wpEbGdrcN5Y29ycA" class="cyc_term">SomethingExisting</a>. Instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVixI5wpEbGdrcN5Y29ycA" class="cyc_term">IntangibleExistingThing</a> exist stably in time (unlike instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViADZwpEbGdrcN5Y29ycA" class="cyc_term">Event</a>), but lack any material parts (unlike instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj27ZwpEbGdrcN5Y29ycA" class="cyc_term">PartiallyTangible</a>). Notable specializations of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVixI5wpEbGdrcN5Y29ycA" class="cyc_term">IntangibleExistingThing</a> include <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv9p3wpwpEbGdrcN5Y29ycA" class="cyc_term">DevisedPracticeOrWork</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVivo5wpEbGdrcN5Y29ycA" class="cyc_term">Agreement</a>.

A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvjJE4ZwpEbGdrcN5Y29ycA" class="cyc_term">Event_Localized</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWESd5wpEbGdrcN5Y29ycA" class="cyc_term">IntrinsicStateChangeEvent</a> is an event characterized primarily by a change in some intrinsic property of at least one main actor involved in the event. Such intrinsic changes may include changes of a thing's color, temperature, device state, or size. Events where the main change is extrinsic (such as a change in location or ownership) are not instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWESd5wpEbGdrcN5Y29ycA" class="cyc_term">IntrinsicStateChangeEvent</a>. In events which have more than one actor, the event may be an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWESd5wpEbGdrcN5Y29ycA" class="cyc_term">IntrinsicStateChangeEvent</a> for one actor but not for another. For example, in a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjwqZwpEbGdrcN5Y29ycA" class="cyc_term">FasteningSafetyBelt</a> event, the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViLD5wpEbGdrcN5Y29ycA" class="cyc_term">SafetySeatBelt</a> (the device used) goes from unconnected to connected (to itself), which is an intrinsic change; however, the agent who does the fastening does not change intrinsically, but only in his configuration to the belt, an external object. Another example: in a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViw4JwpEbGdrcN5Y29ycA" class="cyc_term">HairCuttingEvent</a>, the hair that is cut undergoes an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWESd5wpEbGdrcN5Y29ycA" class="cyc_term">IntrinsicStateChangeEvent</a> due to its role in that kind of event, but the barber undergoes no intrinsic change due to the hair cutting. Note that some events, such as an ice cube melting into a small puddle of water, could be represented either as an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWESd5wpEbGdrcN5Y29ycA" class="cyc_term">IntrinsicStateChangeEvent</a> or as a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVibApwpEbGdrcN5Y29ycA" class="cyc_term">PhysicalTransformationEvent</a>, but not (within a single micro-theory) as both. event that inherently involves a change of state IntrinsicStateChangeEvent

CreationEvent A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWdRSZwpEbGdrcN5Y29ycA" class="cyc_term">CreationOrDestructionEvent</a>. In each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjeiZwpEbGdrcN5Y29ycA" class="cyc_term">CreationEvent</a>, at least one instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi255wpEbGdrcN5Y29ycA" class="cyc_term">SomethingExisting</a> (q.v.) is brought into existence (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWStbZwpEbGdrcN5Y29ycA" class="cyc_term">outputsCreated</a>). creation event

social event A specialization of both <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVieP5wpEbGdrcN5Y29ycA" class="cyc_term">PurposefulAction</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViNJ5wpEbGdrcN5Y29ycA" class="cyc_term">CompositePhysicalAndMentalEvent</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViPO5wpEbGdrcN5Y29ycA" class="cyc_term">SocialOccurrence</a> is an action in which two or more agents take part. In many cases, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViPO5wpEbGdrcN5Y29ycA" class="cyc_term">SocialOccurrence</a>s involve communication among the participating agents. Some instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViPO5wpEbGdrcN5Y29ycA" class="cyc_term">SocialOccurrence</a> have very elaborate role structures (e.g. a typical lawsuit), while others have fairly simple role structures (e.g. greeting a colleague at work). SocialOccurrence

A specialization of both <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViPO5wpEbGdrcN5Y29ycA" class="cyc_term">SocialOccurrence</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV50MZwpEbGdrcN5Y29ycA" class="cyc_term">ChangeInUserRights</a>. In each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViQlpwpEbGdrcN5Y29ycA" class="cyc_term">ExchangeOfUserRights</a>, two instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAB5wpEbGdrcN5Y29ycA" class="cyc_term">Agent_PartiallyTangible</a> (the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV37_5wpEbGdrcN5Y29ycA" class="cyc_term">exchangers</a>) perform two distinct (though related) instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViM85wpEbGdrcN5Y29ycA" class="cyc_term">TransferringPossession</a> with each other. Two objects are exchanged. Each agent gains possession -- in the form of some <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rIh5wwHSwEdaAAACgyZzFrg" class="cyc_term">SituationTypeByUserRights</a> -- of something (an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj0z5wpEbGdrcN5Y29ycA" class="cyc_term">objectOfPossessionTransfer</a>) from the other. Each transfer is related to the other as some kind of condition, usually as a precondition or an intended result; for example, the news seller will hand over a paper if given fifty cents, and a buyer will give the news seller fifty cents so that the seller will turn over a newspaper to the buyer. The two <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViM85wpEbGdrcN5Y29ycA" class="cyc_term">TransferringPossession</a> events are <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViQmZwpEbGdrcN5Y29ycA" class="cyc_term">subEvents</a> of the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViQlpwpEbGdrcN5Y29ycA" class="cyc_term">ExchangeOfUserRights</a> event. ExchangeOfUserRights exchange

indivisible The collection of discrete entities without distinguishable parts, portions, entries, subsets, elements,... A couple examples are: the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViA2JwpEbGdrcN5Y29ycA" class="cyc_term">False</a> truth-value; any single #$MathematicalPoint. Indivisible

transfer event with well-defined to-location A collection of events. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWMZaZwpEbGdrcN5Y29ycA" class="cyc_term">TransferIn</a> is a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOtpwpEbGdrcN5Y29ycA" class="cyc_term">GeneralizedTransfer</a> (q.v.) for which there is a well-defined thing that it is a transfer "to" (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwAyrYZwpEbGdrcN5Y29ycA" class="cyc_term">to_Generic</a>), but not necessarily a well-defined thing that it is a transfer "from" (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv9UIFZwpEbGdrcN5Y29ycA" class="cyc_term">from_Generic</a>). Subcollections of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWMZaZwpEbGdrcN5Y29ycA" class="cyc_term">TransferIn</a> include <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjcHpwpEbGdrcN5Y29ycA" class="cyc_term">Collecting</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWRg15wpEbGdrcN5Y29ycA" class="cyc_term">GainingUserRights</a>, and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjWH5wpEbGdrcN5Y29ycA" class="cyc_term">AccessingAnIBT</a>. At the end of a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWMZaZwpEbGdrcN5Y29ycA" class="cyc_term">TransferIn</a>, the thing transferred (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rDbKaOuVmQdeTKaYmT-4jgg" class="cyc_term">transferredThing</a>) is in some sense "located" at the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwAyrYZwpEbGdrcN5Y29ycA" class="cyc_term">to_Generic</a>. Non- examples of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWMZaZwpEbGdrcN5Y29ycA" class="cyc_term">TransferIn</a> include instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWe33pwpEbGdrcN5Y29ycA" class="cyc_term">AbandoningSomething</a> (when there is no prospective owner) and of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvXDRVpwpEbGdrcN5Y29ycA" class="cyc_term">IBTGeneration</a> (when the information may go to various unspecified locations). TransferIn

Receiving receiving A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWMZaZwpEbGdrcN5Y29ycA" class="cyc_term">TransferIn</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rva8CdpwpEbGdrcN5Y29ycA" class="cyc_term">Receiving</a> is an event in which something `comes in' to an object. Typically, a receiving has associated with it an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv4GokJwpEbGdrcN5Y29ycA" class="cyc_term">Translocation</a> (q.v.); a particular receiving and its associated translocation(s) are related by the predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvqvCoZwpEbGdrcN5Y29ycA" class="cyc_term">transferInSubEvent</a>. If the thing which `comes in' is an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj27ZwpEbGdrcN5Y29ycA" class="cyc_term">PartiallyTangible</a> (such as a baseball, or a SCUD missile), then its reception is an instance of the specialization <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvwycppwpEbGdrcN5Y29ycA" class="cyc_term">ReceivingAnObject</a> (q.v.). If the translocation associated with the receiving is an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwQCA9ZwpEbGdrcN5Y29ycA" class="cyc_term">WavePropagation</a> (such as a radio broadcast, or heat radiation from the Sun), then the receiving is an instance of the specialization <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv8zHIpwpEbGdrcN5Y29ycA" class="cyc_term">ReceivingAWave</a> (q.v.).

static situation StaticSituation A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvYjIS5wpEbGdrcN5Y29ycA" class="cyc_term">Situation</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvh5TfJwpEbGdrcN5Y29ycA" class="cyc_term">StaticSituation</a> is a state of affairs between two or more things, persisting statically over some time interval. Instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvh5TfJwpEbGdrcN5Y29ycA" class="cyc_term">StaticSituation</a> always have a temporal extent, and they usually have a tangible and spatial extent. As an example, consider the situation of Bill Clinton sitting in his easy chair on the evening of 7/4/96. There are participant objects such as Bill and the chair, there are relationships such as the seat of the chair supporting his bottom and his weight being off his feet, etc. In any <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvh5TfJwpEbGdrcN5Y29ycA" class="cyc_term">StaticSituation</a>, for the participants in that situation, there is some significant or focal relationship between them which does not change. In the most typical cases, there is no important change whatsoever, e.g. someone sitting would be such a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvh5TfJwpEbGdrcN5Y29ycA" class="cyc_term">StaticSituation</a>. But some things represented as <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvh5TfJwpEbGdrcN5Y29ycA" class="cyc_term">StaticSituation</a>s can alternatively be represented as <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViADZwpEbGdrcN5Y29ycA" class="cyc_term">Event</a>s. For example, a situation in which geese were flying in a flock would be static (the flock-like spatial relationship between the geese would be retained) but it would also be dynamic in that the geese were moving, so either representation could be chosen depending on the context.

granuleOfTemporalStuff (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjaJJwpEbGdrcN5Y29ycA" class="cyc_term">granuleOfTemporalStuff</a> STUFFTYPE OBJTYPE) means that the stuff-like collection STUFFTYPE has as its temporal granules (or granularity level) instances of the object-like collection OBJTYPE. If some collection is temporally stuff-like, that means that the instances of that collection can be divided temporally, and the temporal slices remaining will still be instances of that collection; e.g., a time slice of some instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAkpwpEbGdrcN5Y29ycA" class="cyc_term">Person</a> is still a person, and a temporal slice of a walking process is still a walking process (cf. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVitN5wpEbGdrcN5Y29ycA" class="cyc_term">TemporalStuffType</a>). Such division cannot always go on indefinitely, however: eventually, division of something temporally stuff-like will result in the temporally object-like 'granules' out of which the stuff-like thing is composed. For instances, division of a walking process would eventually result in individual steps. At this level of division or below, the remaining temporal slices do NOT count as instances of the temporal stuff-type from which they were divided. This may seem counter-intuitive, but since the individual temporal granules of a temporal stuff typically do NOT have most of the properties that the groups made of the granules have (including the property of being temporally stuff-like), we do not count the individual granules as instances of the collection of which they are granules. See also <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjDxJwpEbGdrcN5Y29ycA" class="cyc_term">granuleOfSpatialStuff</a>. Granule Of Temporal Stuff

Translocation A subcollection of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEAZwpEbGdrcN5Y29ycA" class="cyc_term">MovementEvent</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv4GokJwpEbGdrcN5Y29ycA" class="cyc_term">Translocation</a> is a movement across a distance; thus there is both a location that it is a movement "from" (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjiI5wpEbGdrcN5Y29ycA" class="cyc_term">fromLocation</a>) and a location that it is a movement "to" (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjXepwpEbGdrcN5Y29ycA" class="cyc_term">toLocation</a>). (These two locations might or might not be distinct, considering round-trips.) Note that instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv4GokJwpEbGdrcN5Y29ycA" class="cyc_term">Translocation</a> might or might not involve a salient moving object (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEjpwpEbGdrcN5Y29ycA" class="cyc_term">objectMoving</a>); for those that do see the specialization <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOcJwpEbGdrcN5Y29ycA" class="cyc_term">Movement_TranslationEvent</a>; for some that don't see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwQCA9ZwpEbGdrcN5Y29ycA" class="cyc_term">WavePropagation</a>. translocation

A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvjJE4ZwpEbGdrcN5Y29ycA" class="cyc_term">Event_Localized</a>. During each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWdRSZwpEbGdrcN5Y29ycA" class="cyc_term">CreationOrDestructionEvent</a>, one or more instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi255wpEbGdrcN5Y29ycA" class="cyc_term">SomethingExisting</a> (q.v.) come into or go out of existence. Specializations of this collection include <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjeiZwpEbGdrcN5Y29ycA" class="cyc_term">CreationEvent</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj5IJwpEbGdrcN5Y29ycA" class="cyc_term">DestructionEvent</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjhdZwpEbGdrcN5Y29ycA" class="cyc_term">Manufacturing</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj-OJwpEbGdrcN5Y29ycA" class="cyc_term">MakingSomething</a>, and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVisLpwpEbGdrcN5Y29ycA" class="cyc_term">KillingByOrganism</a>. CreationOrDestructionEvent creation or destruction event

emitter emitter This predicate, a specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjX_pwpEbGdrcN5Y29ycA" class="cyc_term">providerOfMotiveForce</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjiI5wpEbGdrcN5Y29ycA" class="cyc_term">fromLocation</a> (qq.v.), is used to identify the source of an emission. <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjc8ZwpEbGdrcN5Y29ycA" class="cyc_term">emitter</a> EMIT OBJ)</code> means that <code>OBJ</code> provides the force involved in making the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi-wZwpEbGdrcN5Y29ycA" class="cyc_term">objectEmitted</a> move from <code>OBJ</code> to someplace outside of <code>OBJ</code>.

initial transfer-out subevent The Cyc predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvk1I1JwpEbGdrcN5Y29ycA" class="cyc_term">transferOutSubEvent</a> indicates the initial stage of a particular <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOtpwpEbGdrcN5Y29ycA" class="cyc_term">GeneralizedTransfer</a> in which the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rDbKaOuVmQdeTKaYmT-4jgg" class="cyc_term">transferredThing</a> leaves the point of origin. For example, (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvk1I1JwpEbGdrcN5Y29ycA" class="cyc_term">transferOutSubEvent</a> TRANSLOC EMISSION) means that EMISSION is the initial stage (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjWoJwpEbGdrcN5Y29ycA" class="cyc_term">firstSubEvents</a>) of the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv4GokJwpEbGdrcN5Y29ycA" class="cyc_term">Translocation</a> TRANSLOC. (The <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjc8ZwpEbGdrcN5Y29ycA" class="cyc_term">emitter</a> in EMISSION is a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjiI5wpEbGdrcN5Y29ycA" class="cyc_term">fromLocation</a> of TRANSLOC.) transferOutSubEvent

A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViGFZwpEbGdrcN5Y29ycA" class="cyc_term">AtLeastPartiallyMentalEvent</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViNJ5wpEbGdrcN5Y29ycA" class="cyc_term">CompositePhysicalAndMentalEvent</a> is an event that involves some mental event(s), as well as some interaction between physical objects. Each instance will thus have at least one <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjpjZwpEbGdrcN5Y29ycA" class="cyc_term">PhysicalEvent</a> as a sub-event. (It may or may not itself be an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjpjZwpEbGdrcN5Y29ycA" class="cyc_term">PhysicalEvent</a>, depending on whether it occurs at a specific spatial location.) Examples include a news broadcast program, a court trial, someone inheriting property, someone writing a letter, a physical examination, and a charity ball. Notable specializations of this collection include <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvrOVYpwpEbGdrcN5Y29ycA" class="cyc_term">PurposefulPhysicalAction</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjoypwpEbGdrcN5Y29ycA" class="cyc_term">SensoryEvent</a>. CompositePhysicalAndMentalEvent event with both physical and mental components

PartiallyTangible A subcollection of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4ro3lluGJHQdiVxrZReHS-jQ" class="cyc_term">EnduringThing_Localized</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAxJwpEbGdrcN5Y29ycA" class="cyc_term">TemporalThing</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj27ZwpEbGdrcN5Y29ycA" class="cyc_term">PartiallyTangible</a> has a tangible (i.e. material) part and a temporal extent (i.e. it exists in time). It might or might not also have an intangible part. For example, a particular copy of a book is made of matter, has temporal extent, and also has an intangible part: the information content of the text markings on its pages. tangible thing

(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjDxJwpEbGdrcN5Y29ycA" class="cyc_term">granuleOfSpatialStuff</a> STUFFTYPE OBJTYPE) means that the stuff-like collection STUFFTYPE has as its spatial granules (or granularity level) instances of the object-like collection OBJTYPE. If some collection is spatially stuff-like, that means that the instances of that collection can be divided spatially, and the resulting physical portions will themselves be instances of that collection; e.g., a physical portion of some instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViFf5wpEbGdrcN5Y29ycA" class="cyc_term">SandMob</a> is still sand (cf. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVny6pwpEbGdrcN5Y29ycA" class="cyc_term">ExistingStuffType</a>). Such divisibility cannot go on indefinitely, however: eventually, division of something spatially stuff-like will result in the object-like 'granules' out of which the stuff-like thing is composed. For instances, division of sand would eventually result in individual grains of sand, division of water would eventually get down to individual molecules of water, etc. _Below_ this level of division, the remaining physical portions do _not_ count as instances of the stuff-type from which they were divided. _At_ this level of division, things may go one way or another: a single molecule of water is <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjAHZwpEbGdrcN5Y29ycA" class="cyc_term">Water</a> (at least if we stick by the necessary identity of water and H2O), whereas a single grain of sand is not plausibly sand. Granule Of Spatial Stuff granuleOfSpatialStuff

SomethingExisting thing existing stably in time A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rtM0npht0QdiUF94Dipp7Pg" class="cyc_term">TemporallyExistingThing</a> whose instances are more or less static, as compared (e.g.) to the more dynamic instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViADZwpEbGdrcN5Y29ycA" class="cyc_term">Event</a>. The clearest examples of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi255wpEbGdrcN5Y29ycA" class="cyc_term">SomethingExisting</a>s are tangible things, such as people, lakes, stars, and the Earth's ionosphere. But <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi255wpEbGdrcN5Y29ycA" class="cyc_term">SomethingExisting</a> also includes certain intangible temporal things, such as <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVivo5wpEbGdrcN5Y29ycA" class="cyc_term">Agreement</a>s and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi_0JwpEbGdrcN5Y29ycA" class="cyc_term">Obligation</a>s, that remain relatively stable throughout their lifetimes. On the other hand, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi255wpEbGdrcN5Y29ycA" class="cyc_term">SomethingExisting</a> excludes "purely temporal" intangibles such as <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAw5wpEbGdrcN5Y29ycA" class="cyc_term">TimeInterval</a>s.

type of temporally stuff-like thing A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVir35wpEbGdrcN5Y29ycA" class="cyc_term">StuffType</a> (q.v.) whose instances are all and only those collections that are temporally stuff-like. A collection <code>COL</code> is temporally stuff-like just in case every purely temporal part (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWn4OZwpEbGdrcN5Y29ycA" class="cyc_term">timeSlices</a>) of an instance of <code>COL</code> is itself an instance of <code>COL</code>, unless it is a temporal part of a temporal granule of <code>COL</code> (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjaJJwpEbGdrcN5Y29ycA" class="cyc_term">granuleOfTemporalStuff</a>). More precisely, for a collection <code>COL</code> to be an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVitN5wpEbGdrcN5Y29ycA" class="cyc_term">TemporalStuffType</a> it is both a necessary and sufficient condition that for any <code>OBJ1</code> and <code>OBJ2</code> (with <code>OBJ2</code> at or above <code>COL</code>'s temporal granularity level), if <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViBBJwpEbGdrcN5Y29ycA" class="cyc_term">isa</a> OBJ1 COL)</code> and <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWn4OZwpEbGdrcN5Y29ycA" class="cyc_term">timeSlices</a> OBJ1 OBJ2)</code>, then <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViBBJwpEbGdrcN5Y29ycA" class="cyc_term">isa</a> OBJ2 COL)</code>. Consider <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi0gpwpEbGdrcN5Y29ycA" class="cyc_term">WalkingOnTwoLegs</a>. Take an arbitrary instance <code>WALK</code> of this collection (say Miss America 2000's victory walk down the runway and back); and then take an arbitrary time-slice <code>SUBWALK</code> of <code>WALK</code> that subsumes at least one instance of (the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjaJJwpEbGdrcN5Y29ycA" class="cyc_term">granuleOfTemporalStuff</a> for <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi0gpwpEbGdrcN5Y29ycA" class="cyc_term">WalkingOnTwoLegs</a>) <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViYBpwpEbGdrcN5Y29ycA" class="cyc_term">TakingAStep</a> (say her trip back from the end of the runway). <code>SUBWALK</code> is itself an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi0gpwpEbGdrcN5Y29ycA" class="cyc_term">WalkingOnTwoLegs</a>. So <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi0gpwpEbGdrcN5Y29ycA" class="cyc_term">WalkingOnTwoLegs</a> is an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVitN5wpEbGdrcN5Y29ycA" class="cyc_term">TemporalStuffType</a>. See <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViq35wpEbGdrcN5Y29ycA" class="cyc_term">TemporalObjectType</a> for the disjoint notion of being temporally object-like. TemporalStuffType

composite tangible and intangible thing CompositeTangibleAndIntangibleObject The collection of individuals that have both a tangible and an intangible component. Instances include people (who have bodies and minds), information bearing objects (which consist of intangible information encoded in a tangible object, such as the music on a CD or the text in a book), and many other things. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj3cZwpEbGdrcN5Y29ycA" class="cyc_term">CompositeTangibleAndIntangibleObject</a>, being partially tangible, exists in time (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAxJwpEbGdrcN5Y29ycA" class="cyc_term">TemporalThing</a>). Although occasionally it can be useful to reify separately the tangible and intangible components of a composite object (e.g. to state certain things about Lenin's body as opposed to his mind), in most cases it is sufficient simply to reify the composite.

PhysicalTransformationEvent A specialization of both <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv4jqZJwpEbGdrcN5Y29ycA" class="cyc_term">PhysicalDestructionEvent</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvpKVWpwpEbGdrcN5Y29ycA" class="cyc_term">PhysicalCreationEvent</a>. In each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVibApwpEbGdrcN5Y29ycA" class="cyc_term">PhysicalTransformationEvent</a> at least one thing ceases to exist and at least one thing comes into existence (and usually at least some portion of the thing(s) destroyed becomes incorporated into the thing(s) created). An important specialization of this collection is <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVibh5wpEbGdrcN5Y29ycA" class="cyc_term">PhysicalTransformationProcess</a>, the collection of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVibApwpEbGdrcN5Y29ycA" class="cyc_term">PhysicalTransformationEvent</a>s that are also instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVitN5wpEbGdrcN5Y29ycA" class="cyc_term">TemporalStuffType</a>. See also the predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVigMpwpEbGdrcN5Y29ycA" class="cyc_term">transformedInto</a>. transform

A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvjJE4ZwpEbGdrcN5Y29ycA" class="cyc_term">Event_Localized</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjpjZwpEbGdrcN5Y29ycA" class="cyc_term">PhysicalEvent</a> is a spatially localized event involving one or more physical objects or stuffs. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjpjZwpEbGdrcN5Y29ycA" class="cyc_term">PhysicalEvent</a>s typically involve interaction among <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj27ZwpEbGdrcN5Y29ycA" class="cyc_term">PartiallyTangible</a>s. But note that a physical event might consist in the creation, destruction, movement, or a change in some physical feature of a single salient physical object. (See <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvpKVWpwpEbGdrcN5Y29ycA" class="cyc_term">PhysicalCreationEvent</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv4jqZJwpEbGdrcN5Y29ycA" class="cyc_term">PhysicalDestructionEvent</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEAZwpEbGdrcN5Y29ycA" class="cyc_term">MovementEvent</a>, and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWESd5wpEbGdrcN5Y29ycA" class="cyc_term">IntrinsicStateChangeEvent</a>.) For a contrasting (though not necessarily disjoint) collection, see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvkjZ1pwpEbGdrcN5Y29ycA" class="cyc_term">StrictlyMentalEvent</a>. For events that have both physical and mental components, see the collection <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViNJ5wpEbGdrcN5Y29ycA" class="cyc_term">CompositePhysicalAndMentalEvent</a>. physical event PhysicalEvent

action The collection of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViADZwpEbGdrcN5Y29ycA" class="cyc_term">Event</a>s (q.v.) that are carried out by some "doer" (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP1HmJwpEbGdrcN5Y29ycA" class="cyc_term">doneBy</a>). Instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVioQZwpEbGdrcN5Y29ycA" class="cyc_term">Action</a> include any event in which one or more actors effect some change in the (tangible or intangible) state of the world, typically by an expenditure of effort or energy. Note that it is not required that any tangible object be moved, changed, produced, or destroyed for an action to occur; the effects of an action might be intangible (such as a change in a bank balance or the intimidation of a subordinate). Note also that the doer of an action, though typically an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAB5wpEbGdrcN5Y29ycA" class="cyc_term">Agent_PartiallyTangible</a> (q.v.), need not be (e.g. a falling rock that dents a car's roof). Depending upon the context, doers of actions might be animate or inanimate, conscious or nonconscious. For actions that are intentional, see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVieP5wpEbGdrcN5Y29ycA" class="cyc_term">PurposefulAction</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVipYpwpEbGdrcN5Y29ycA" class="cyc_term">performedBy</a>. Action

Situation situation A specialization of both <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjj45wpEbGdrcN5Y29ycA" class="cyc_term">IntangibleIndividual</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAxJwpEbGdrcN5Y29ycA" class="cyc_term">TemporalThing</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvYjIS5wpEbGdrcN5Y29ycA" class="cyc_term">Situation</a> is a state or event consisting of one or more objects having certain properties or bearing certain relations to each other. Notable specializations of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvYjIS5wpEbGdrcN5Y29ycA" class="cyc_term">Situation</a> are <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViADZwpEbGdrcN5Y29ycA" class="cyc_term">Event</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvh5TfJwpEbGdrcN5Y29ycA" class="cyc_term">StaticSituation</a>; it is disjoint with <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi255wpEbGdrcN5Y29ycA" class="cyc_term">SomethingExisting</a>.

postEvents A <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwL4_QpwpEbGdrcN5Y29ycA" class="cyc_term">BinaryRolePredicate</a> (q.v.) that relates one event to another that follows it. <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi76ZwpEbGdrcN5Y29ycA" class="cyc_term">postEvents</a> BEFORE AFTER)</code> implies two things: (1) <code>BEFORE</code> occurs strictly before <code>AFTER</code>: <code>AFTER</code> starts after <code>BEFORE</code> has ended (see the generalization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi76ZwpEbGdrcN5Y29ycA" class="cyc_term">postEvents</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjQyZwpEbGdrcN5Y29ycA" class="cyc_term">startsAfterEndingOf</a>). (2) <code>BEFORE</code> and <code>AFTER</code> are significantly relevant to each other. This required "relevance" of the two arguments to each other is difficult to formalize but often intuitively clearcut. Sometimes <code>AFTER</code> is caused by <code>BEFORE</code>. For example, we might say (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi76ZwpEbGdrcN5Y29ycA" class="cyc_term">postEvents</a> TakingAShower001 ExitingShower001), but would not say (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi76ZwpEbGdrcN5Y29ycA" class="cyc_term">postEvents</a> BolshevikRelvolution DeathOfJohnLennon) since these two events are not at all relevant to each other. Post Events

SingleDoerAction action with only one performer A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVioQZwpEbGdrcN5Y29ycA" class="cyc_term">Action</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP1IRJwpEbGdrcN5Y29ycA" class="cyc_term">SingleDoerAction</a> is an action which can have only one "doer" (see the predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP1HmJwpEbGdrcN5Y29ycA" class="cyc_term">doneBy</a>). Such actions may be intentional, but they need not be. Most bodily functions (e.g., the instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViYhJwpEbGdrcN5Y29ycA" class="cyc_term">Heartbeating</a> or <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjPypwpEbGdrcN5Y29ycA" class="cyc_term">Bleeding_TheAction</a>) belong to specializations of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP1IRJwpEbGdrcN5Y29ycA" class="cyc_term">SingleDoerAction</a>, because the only doer of a normal bodily function is the body of a single agent. In order for a type of action (i.e., a specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVioQZwpEbGdrcN5Y29ycA" class="cyc_term">Action</a>) to be a specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP1IRJwpEbGdrcN5Y29ycA" class="cyc_term">SingleDoerAction</a>, it must be inconsistent to assert, for any instance <code>ACT</code> of that type of action, both <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP1HmJwpEbGdrcN5Y29ycA" class="cyc_term">doneBy</a> ACT X)</code> and <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP1HmJwpEbGdrcN5Y29ycA" class="cyc_term">doneBy</a> ACT Y)</code>, where <code>X</code> and <code>Y</code> are different. Notable specializations of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwP1IRJwpEbGdrcN5Y29ycA" class="cyc_term">SingleDoerAction</a> include <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjSm5wpEbGdrcN5Y29ycA" class="cyc_term">Sleeping</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkJU5wpEbGdrcN5Y29ycA" class="cyc_term">Dying</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjXfZwpEbGdrcN5Y29ycA" class="cyc_term">AnimalWalkingProcess</a>, and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViMp5wpEbGdrcN5Y29ycA" class="cyc_term">WritingByHand</a>.

The predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjXepwpEbGdrcN5Y29ycA" class="cyc_term">toLocation</a> is used to indicate the ending point of a particular movement. <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjXepwpEbGdrcN5Y29ycA" class="cyc_term">toLocation</a> MOVE LOC)</code> means that <code>LOC</code> is where the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEjpwpEbGdrcN5Y29ycA" class="cyc_term">objectMoving</a> in <code>MOVE</code> (a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOcJwpEbGdrcN5Y29ycA" class="cyc_term">Movement_TranslationEvent</a>) is found when the event <code>MOVE</code> ends; the final location of the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEjpwpEbGdrcN5Y29ycA" class="cyc_term">objectMoving</a> in that event is <code>LOC</code>. The <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEjpwpEbGdrcN5Y29ycA" class="cyc_term">objectMoving</a> may or may not be <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwPusM5wpEbGdrcN5Y29ycA" class="cyc_term">Stationary</a> at <code>LOC</code>. If <code>MOVE</code> is a single-pathway translation (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVsNyJwpEbGdrcN5Y29ycA" class="cyc_term">Translation_SingleTrajectory</a>), then every <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEjpwpEbGdrcN5Y29ycA" class="cyc_term">objectMoving</a> in it is found at <code>LOC</code> when <code>MOVE</code> ends. If <code>MOVE</code> has multiple movers and multiple pathways (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV74r5wpEbGdrcN5Y29ycA" class="cyc_term">Translation_MultiTrajectory</a>), then at least some of the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEjpwpEbGdrcN5Y29ycA" class="cyc_term">objectMoving</a>(s) can be found at <code>LOC</code> at the end of <code>MOVE</code>. If <code>MOVE</code> is a fluid flow (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEhJwpEbGdrcN5Y29ycA" class="cyc_term">FluidFlow_Translation</a>), then at least some portion of the fluid <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkEjpwpEbGdrcN5Y29ycA" class="cyc_term">objectMoving</a> can be found at location <code>LOC</code> at the end of <code>MOVE</code>. See also <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViCe5wpEbGdrcN5Y29ycA" class="cyc_term">motionPathway_Complete</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwPKiKZwpEbGdrcN5Y29ycA" class="cyc_term">pathConnects</a>. destination toLocation

A collection of events and a specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWdRSZwpEbGdrcN5Y29ycA" class="cyc_term">CreationOrDestructionEvent</a>. In each instance of this collection at least one instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi255wpEbGdrcN5Y29ycA" class="cyc_term">SomethingExisting</a> (the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWWNUJwpEbGdrcN5Y29ycA" class="cyc_term">inputsDestroyed</a>) ceases to exist. Examples include deleting a computer file, chopping down a tree and breaking an agreement. For cases where the item destroyed is a material thing (i.e. an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj27ZwpEbGdrcN5Y29ycA" class="cyc_term">PartiallyTangible</a>), see the more specialized <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv4jqZJwpEbGdrcN5Y29ycA" class="cyc_term">PhysicalDestructionEvent</a>. DestructionEvent destruction event

A collection of events and a specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOtpwpEbGdrcN5Y29ycA" class="cyc_term">GeneralizedTransfer</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV50MZwpEbGdrcN5Y29ycA" class="cyc_term">ChangeInUserRights</a> is an event in which some instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAB5wpEbGdrcN5Y29ycA" class="cyc_term">Agent_PartiallyTangible</a> either gains or loses possession of something. "Possession" means having some right to use a thing that one has in hand or otherwise has access to. Different types of possession (e.g. ownership, rental, borrowings) can be specified by using the appropriate instance(s) of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rIh5wwHSwEdaAAACgyZzFrg" class="cyc_term">SituationTypeByUserRights</a> (q.v.). Changes in an agent's user rights can come about in various ways: through buying and selling, renting, borrowing or lending, giving, repossession, etc. Specializations of this collection include <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWQcoZwpEbGdrcN5Y29ycA" class="cyc_term">LosingUserRights</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWRg15wpEbGdrcN5Y29ycA" class="cyc_term">GainingUserRights</a>, and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViQlpwpEbGdrcN5Y29ycA" class="cyc_term">ExchangeOfUserRights</a>; in the latter collection, there is an alteration in the rights of two (or more) agents to use two (or more) items -- as in a purchase, when one agent gets full use rights to an object by turning over a sum of money to the object's previous owner. In addition, some changes in user rights are classified explicitly in <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjgVpwpEbGdrcN5Y29ycA" class="cyc_term">TemporaryChangeOfUserRights</a> (e.g. borrowing, renting), while others are permanent. Events that involve such changes in user rights all belong in the collection of events, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV50MZwpEbGdrcN5Y29ycA" class="cyc_term">ChangeInUserRights</a>. In any particular <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV50MZwpEbGdrcN5Y29ycA" class="cyc_term">ChangeInUserRights</a> event, the item which is changing hands is identified as the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj0z5wpEbGdrcN5Y29ycA" class="cyc_term">objectOfPossessionTransfer</a>. change in user rights ChangeInUserRights

The collection of wholly intangible individuals, a specialization of both <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjjo5wpEbGdrcN5Y29ycA" class="cyc_term">Intangible</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjaApwpEbGdrcN5Y29ycA" class="cyc_term">Individual</a>. Instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjj45wpEbGdrcN5Y29ycA" class="cyc_term">IntangibleIndividual</a> are immaterial, and thus do not have mass, color, or other tangible qualities. Examples include mathematical objects (such as numbers, functions, and relations), attributes, time intervals, space regions, and events. Excluded are sets and collections because, although intangible, they are not individuals. intangible individual object IntangibleIndividual

Transfer In Sub Event The Cyc predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvqvCoZwpEbGdrcN5Y29ycA" class="cyc_term">transferInSubEvent</a> indicates the final stage of a particular <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViOtpwpEbGdrcN5Y29ycA" class="cyc_term">GeneralizedTransfer</a> in which the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rDbKaOuVmQdeTKaYmT-4jgg" class="cyc_term">transferredThing</a> reaches the destination. For example, (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvqvCoZwpEbGdrcN5Y29ycA" class="cyc_term">transferInSubEvent</a> COMM LISTENING) means that LISTENING is the final stage (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjXppwpEbGdrcN5Y29ycA" class="cyc_term">lastSubEvents</a>) of the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVieg5wpEbGdrcN5Y29ycA" class="cyc_term">CommunicationAct_Single</a> COMM. transferInSubEvent

ExistingStuffType type of temporally and spatially stuff-like thing A collection of collections, and a specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVitN5wpEbGdrcN5Y29ycA" class="cyc_term">TemporalStuffType</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVny6pwpEbGdrcN5Y29ycA" class="cyc_term">ExistingStuffType</a> is a collection of things (including portions of things) which are both temporally and spatially stufflike. Division in time or space does not destroy the stufflike quality of the object (down to a certain granularity). <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViBBJwpEbGdrcN5Y29ycA" class="cyc_term">isa</a> STUFFTYPE <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVny6pwpEbGdrcN5Y29ycA" class="cyc_term">ExistingStuffType</a>)</code> implies both (i) for most instances <code>STUFF</code> of <code>STUFFTYPE</code>, for any proper physical part (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r8a2smPXcQdiEoJhcx65EiQ" class="cyc_term">properPhysicalDecompositions</a>) <code>PART</code> of <code>STUFF</code>, <code>PART</code> is also an instance of <code>STUFFTYPE</code> and (ii) for all instances <code>STUFF</code> of <code>STUFFTYPE</code>, for most proper physical parts <code>PART</code> of <code>STUFF</code>, <code>PART</code> is also an instance of <code>STUFFTYPE</code>. For example, every piece of wood is temporally stufflike: if W-168 is a piece of wood during 1996, then it's also a piece of wood for the one-minute time-slice 9:05am 7/7/96. It's also spatially stufflike: if we take that piece of wood W-168 and cut it in half, we have two things which are both pieces of wood. Since every piece of wood is both temporally and spatially stufflike, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVimxJwpEbGdrcN5Y29ycA" class="cyc_term">Wood</a> is an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVny6pwpEbGdrcN5Y29ycA" class="cyc_term">ExistingStuffType</a>. Other instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVny6pwpEbGdrcN5Y29ycA" class="cyc_term">ExistingStuffType</a> include the collections #$AppleJuice, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj1EpwpEbGdrcN5Y29ycA" class="cyc_term">IceCream</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvgC2UJwpEbGdrcN5Y29ycA" class="cyc_term">Diamond</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwQCaCZwpEbGdrcN5Y29ycA" class="cyc_term">WaxedPaper</a>, and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwAoze5wpEbGdrcN5Y29ycA" class="cyc_term">StriatedMuscle</a>. See the comment for <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVir35wpEbGdrcN5Y29ycA" class="cyc_term">StuffType</a> to learn more about the distinctions between, and the need for, these four collections: <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVir35wpEbGdrcN5Y29ycA" class="cyc_term">StuffType</a>, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVirnZwpEbGdrcN5Y29ycA" class="cyc_term">ObjectType</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWXYgJwpEbGdrcN5Y29ycA" class="cyc_term">ExistingObjectType</a>.

Top-Topic top-topic CycVocabularyTopic An instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvprlOZwpEbGdrcN5Y29ycA" class="cyc_term">FacetingCollectionType</a> and a specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rgQsP1F2xEdif1wACs2IMlQ" class="cyc_term">Topic</a>. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rAmoSCGJbQdiSXZJvYiNhkQ" class="cyc_term">CycVocabularyTopic</a> is a collection of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViA9JwpEbGdrcN5Y29ycA" class="cyc_term">Thing</a>s falling under a topic for which some Cyc Vocabulary exists. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rgQsP1F2xEdif1wACs2IMlQ" class="cyc_term">Topic</a> is neither a strict [<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvcZ1FpwpEbGdrcN5Y29ycA" class="cyc_term">facets_Strict</a>] nor a covering [<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv86JWpwpEbGdrcN5Y29ycA" class="cyc_term">facets_Covering</a>] faceting of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViA9JwpEbGdrcN5Y29ycA" class="cyc_term">Thing</a>: many <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViA9JwpEbGdrcN5Y29ycA" class="cyc_term">Thing</a>s may be instances of no <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rgQsP1F2xEdif1wACs2IMlQ" class="cyc_term">Topic</a>, or of multiple <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rgQsP1F2xEdif1wACs2IMlQ" class="cyc_term">Topic</a>s. cyc vocabulary topic Top-Topic top-topic cyc metaphysics topic A <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4r2SZdtGMBQdiOl-Ui2UGs_g" class="cyc_term">CycVocabularyTopLevelTopic</a> and a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rtGXkHpNaEdqAAAACs0uFOQ" class="cyc_term">KBDependentCollection</a>. CycMetaphysics-Topic A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwIE23ZwpEbGdrcN5Y29ycA" class="cyc_term">TimeDependentCollection</a> (q.v.). This is the collection of all and only those collections <code>COL</code> such that any thing's being an instance of <code>COL</code> depends on the current state of the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjqoZwpEbGdrcN5Y29ycA" class="cyc_term">CycKB</a>. Such a <code>COL</code> corresponds to a property defined (at least partly) in terms of the contents, features, or implementation of the Cyc Knowledge Base itself, as opposed to a property that "exists out there" in the KB-independent world. For example, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV281JwpEbGdrcN5Y29ycA" class="cyc_term">CycLAssertion</a> is a KB-dependent collection, membership in which requires of a given CycL sentence that it has in fact been asserted to the KB. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViAoJwpEbGdrcN5Y29ycA" class="cyc_term">CycLSentence</a> is also KB-dependent, as being a CycL sentence requires being composed (ultimately) out of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvu6KTZwpEbGdrcN5Y29ycA" class="cyc_term">CycLReifiedDenotationalTerm</a>s (and perhaps variables) -- i.e. terms that are currently reified in the KB. Conversely, <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv5ddsJwpEbGdrcN5Y29ycA" class="cyc_term">Sentence</a> is not a KB-dependent collection. See also <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvip9N5wpEbGdrcN5Y29ycA" class="cyc_term">KBDependentRelation</a>. KB dependent collection KBDependentCollection