]> 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. To secure is to gain possession of a position or terrain feature with or without force and try to prevent its destruction or loss by enemy action. A unit does not have to physically occupy a geographical location to secure it if the unit can prevent the enemy from occupying or firing at that location by other means. The subordinate tasks associated with secure are to prevent enemy direct and observed indirect fire from impacting on the secured area and to prevent any enemy forces from occupying or using the secured area. securing an objective SecuringAnObjective http://en.wikipedia.org/wiki/Security secured secured an objective have secured will secure an objective secure an objective will have secured has secured an objective will have secured an objective securing secures an objective secures have secured an objective has secured secure will secure had secured an objective had secured To secure is to gain possession of a position or terrain feature with or without force and try to prevent its destruction or loss by enemy action. A unit does not have to physically occupy a geographical location to secure it if the unit can prevent the enemy from occupying or firing at that location by other means. The subordinate tasks associated with secure are to prevent enemy direct and observed indirect fire from impacting on the secured area and to prevent any enemy forces from occupying or using the secured area. securing an objective SecuringAnObjective To secure is to gain possession of a position or terrain feature with or without force and try to prevent its destruction or loss by enemy action. A unit does not have to physically occupy a geographical location to secure it if the unit can prevent the enemy from occupying or firing at that location by other means. The subordinate tasks associated with secure are to prevent enemy direct and observed indirect fire from impacting on the secured area and to prevent any enemy forces from occupying or using the secured area. securing an objective SecuringAnObjective MilitaryTaskedActionType type of military task The collection of all types of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVieP5wpEbGdrcN5Y29ycA" class="cyc_term">PurposefulAction</a> that can be assigned as tasks (cf. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvpz69JwpEbGdrcN5Y29ycA" class="cyc_term">unitAssignedToTask</a>) to a military unit (cf. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwQWn3pwpEbGdrcN5Y29ycA" class="cyc_term">ModernMilitaryUnit_Deployable</a>). Examples of instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rBvMr-qWFEdaAAAABAxv6tg" class="cyc_term">MilitaryTaskedActionType</a> are <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvbfzAZwpEbGdrcN5Y29ycA" class="cyc_term">AttackOnObject</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv4jqZJwpEbGdrcN5Y29ycA" class="cyc_term">PhysicalDestructionEvent</a>. It is not assumed that any spec whatsoever of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwCCSNZwpEbGdrcN5Y29ycA" class="cyc_term">MilitaryAction</a> is an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rBvMr-qWFEdaAAAABAxv6tg" class="cyc_term">MilitaryTaskedActionType</a> : e.g., the collection of tasks to be performed by UNIT003 by 3 pm on July 31 might well be a spec of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwCCSNZwpEbGdrcN5Y29ycA" class="cyc_term">MilitaryAction</a>, but it shouldn't be a military task _type_ in its own right. (In other words: this collection does not include the powerset of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwCCSNZwpEbGdrcN5Y29ycA" class="cyc_term">MilitaryAction</a>.) AccomplishmentType type of accomplishment A collection of collections. Each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv48ocpwpEbGdrcN5Y29ycA" class="cyc_term">AccomplishmentType</a> is a type of events that include, by their nature, a 'culmination' or completion point, conceptually distinct from their mere temporal ending. Moreover, each instance of an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv48ocpwpEbGdrcN5Y29ycA" class="cyc_term">AccomplishmentType</a> is 'quantized' in the following sense: if <code>EVENT-1</code> and <code>EVENT-2</code> are instances of the same instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv48ocpwpEbGdrcN5Y29ycA" class="cyc_term">AccomplishmentType</a>, then <code>EVENT-2</code> cannot be a proper sub-event of <code>EVENT-1</code>, nor can <code>EVENT-1</code> be a proper sub-event of <code>EVENT-2</code>. DurativeEventType A collection of collections. If TYPE is an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwNyXxJwpEbGdrcN5Y29ycA" class="cyc_term">DurativeEventType</a>, each instance of TYPE is a "durative event" extended through time, i.e., it endures continuously between its starting and ending points, and such points are not simultaneous. As an example, writing a letter is a durative event type, since an event of this type will (except in "degenerate" cases) have a distinct starting point, a period of time in the middle during which writing occurs, and an end point at which the letter is written. By contrast, winning a prize is an instantaneous change: up to the moment the event takes place, you don't have the prize, after that you do. Granted, the awarding of the prize might in fact have a physical duration, but from a conceptual or logical point of view it might as well have none. If one thinks of events as the occurrence of "changes", one may regard durative events as changes that intrinsically occupy a continuous, non-zero chunk of time, and non-durative events (for which see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv4unQpwpEbGdrcN5Y29ycA" class="cyc_term">PunctualEventType</a>) as instantaneous changes. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv9vChJwpEbGdrcN5Y29ycA" class="cyc_term">CumulativeEventType</a> is a proper specialization of this collection, because the cumulativity property (see the salient assertion for <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv9vChJwpEbGdrcN5Y29ycA" class="cyc_term">CumulativeEventType</a>) implies that all process types can have temporal extension. Naturally, many <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwNyXxJwpEbGdrcN5Y29ycA" class="cyc_term">DurativeEventType</a>s are not cumulative, but rather <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv48ocpwpEbGdrcN5Y29ycA" class="cyc_term">AccomplishmentType</a>s. type of durative event To secure is to gain possession of a position or terrain feature with or without force and try to prevent its destruction or loss by enemy action. A unit does not have to physically occupy a geographical location to secure it if the unit can prevent the enemy from occupying or firing at that location by other means. The subordinate tasks associated with secure are to prevent enemy direct and observed indirect fire from impacting on the secured area and to prevent any enemy forces from occupying or using the secured area. securing an objective SecuringAnObjective offensive military task The collection comprised of the closed class of forms of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwCCSNZwpEbGdrcN5Y29ycA" class="cyc_term">MilitaryAction</a> which may be performed as part of either offensive or defensive actions. MilitaryTask-MayBeOffensiveOrDefensive Pretty String (<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwLSVCpwpEbGdrcN5Y29ycA" class="cyc_term">prettyString</a> TERM STRING) means that STRING is the English word or expression (sequence of words) commonly used to refer to TERM. The predicate <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwLSVCpwpEbGdrcN5Y29ycA" class="cyc_term">prettyString</a> is used by the code which generates CycL to English paraphrases, but its applicability is not restricted to this use. prettyString appropriating A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjGlpwpEbGdrcN5Y29ycA" class="cyc_term">TakingSomething</a>. In each instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjuo5wpEbGdrcN5Y29ycA" class="cyc_term">AppropriatingSomething</a>, an agent takes something that no one else has user rights over, such as air for breathing, or some object which at that time belongs to no one (for example, a dime lying in the street). AppropriatingSomething