Planconditions Pattern¶

Source: ODP portal · Published by: ontologydesignpatterns.org · Category: behavioral · Domain: general

What has to be true before a given plan can be carried out, and what is that plan meant to make true afterwards?; Which plans require a particular state of affairs before they can start, and which plans are meant to bring that state of affairs about?; For one particular run of a plan, which conditions did it start from and which conditions did it leave behind?

What it answers¶

What has to be true before a given plan can be carried out, and what is that plan meant to make true afterwards?
Which plans require a particular state of affairs before they can start, and which plans are meant to bring that state of affairs about?
For one particular run of a plan, which conditions did it start from and which conditions did it leave behind?

The pattern¶

The graph is the axioms the pattern asserts; nothing here is inferred. Drag to rearrange, scroll to zoom, and use the graph's own search box to find a term inside it.

Opens at level of detail 3: classes, individuals, properties and restrictions, without the literals. Raise it with the LOD control in the graph's own toolbar to see annotation values and anything a reasoner adds.

Download the pattern

Should you use this one?¶


Size	3 classes, 10 properties, 56 axioms
Brings in	2 imported ontologies, so adopting it adopts those too
Reasoning	HermiT finds this pattern consistent, with no unsatisfiable class, and its worked example consistent with the pattern.

Check it yourself: the published pattern · an archived copy · the ontology itself.

If a link does not open

ontologydesignpatterns.org, which publishes most of this library, does not currently answer over HTTPS, and its wiki redirects submission pages to its front page. The archived copy is there for exactly that reason. The ontology files themselves are still served over plain HTTP.

Terms it declares¶

The 78 classes and properties this pattern models, as the recommender scores them. Annotation properties and built-ins are excluded, because an annotation property is not modelling.

http://www.ontologydesignpatterns.org/cp/owl/agentrole.owl#Agent
http://www.ontologydesignpatterns.org/cp/owl/basicplan.owl#GoalSituation
http://www.ontologydesignpatterns.org/cp/owl/basicplan.owl#conceptualizes
http://www.ontologydesignpatterns.org/cp/owl/basicplan.owl#executesTask
http://www.ontologydesignpatterns.org/cp/owl/basicplan.owl#isConceptualizedBy
http://www.ontologydesignpatterns.org/cp/owl/basicplan.owl#isExecutedIn
http://www.ontologydesignpatterns.org/cp/owl/basicplan.owl#isParametrizedBy
http://www.ontologydesignpatterns.org/cp/owl/basicplan.owl#isSatisfiedBy
http://www.ontologydesignpatterns.org/cp/owl/basicplan.owl#parametrizes
http://www.ontologydesignpatterns.org/cp/owl/basicplan.owl#satisfies
http://www.ontologydesignpatterns.org/cp/owl/basicplandescription.owl#Goal
http://www.ontologydesignpatterns.org/cp/owl/basicplandescription.owl#Plan
http://www.ontologydesignpatterns.org/cp/owl/basicplandescription.owl#definesRole
http://www.ontologydesignpatterns.org/cp/owl/basicplandescription.owl#definesTask
http://www.ontologydesignpatterns.org/cp/owl/basicplandescription.owl#hasMainGoal
http://www.ontologydesignpatterns.org/cp/owl/basicplandescription.owl#isMainGoalIn
http://www.ontologydesignpatterns.org/cp/owl/basicplandescription.owl#isRoleDefinedIn
http://www.ontologydesignpatterns.org/cp/owl/basicplandescription.owl#isTaskDefinedIn
http://www.ontologydesignpatterns.org/cp/owl/basicplanexecution.owl#Action
http://www.ontologydesignpatterns.org/cp/owl/basicplanexecution.owl#Agent
http://www.ontologydesignpatterns.org/cp/owl/basicplanexecution.owl#PlanExecution
http://www.ontologydesignpatterns.org/cp/owl/basicplanexecution.owl#actionHasParticipant
http://www.ontologydesignpatterns.org/cp/owl/basicplanexecution.owl#includesAction
http://www.ontologydesignpatterns.org/cp/owl/basicplanexecution.owl#includesAgent
http://www.ontologydesignpatterns.org/cp/owl/basicplanexecution.owl#includesObject
http://www.ontologydesignpatterns.org/cp/owl/basicplanexecution.owl#includesRegion
http://www.ontologydesignpatterns.org/cp/owl/basicplanexecution.owl#isActionIncludedIn
http://www.ontologydesignpatterns.org/cp/owl/basicplanexecution.owl#isAgentIncludedIn
http://www.ontologydesignpatterns.org/cp/owl/basicplanexecution.owl#isObjectIncludedIn
http://www.ontologydesignpatterns.org/cp/owl/basicplanexecution.owl#isParticipantInAction
http://www.ontologydesignpatterns.org/cp/owl/basicplanexecution.owl#isRegionIncludedIn
http://www.ontologydesignpatterns.org/cp/owl/classification.owl#Concept
http://www.ontologydesignpatterns.org/cp/owl/classification.owl#classifies
http://www.ontologydesignpatterns.org/cp/owl/classification.owl#isClassifiedBy
http://www.ontologydesignpatterns.org/cp/owl/description.owl#Concept
http://www.ontologydesignpatterns.org/cp/owl/description.owl#Description
http://www.ontologydesignpatterns.org/cp/owl/description.owl#defines
http://www.ontologydesignpatterns.org/cp/owl/description.owl#isConceptUsedIn
http://www.ontologydesignpatterns.org/cp/owl/description.owl#isDefinedIn
http://www.ontologydesignpatterns.org/cp/owl/description.owl#usesConcept
http://www.ontologydesignpatterns.org/cp/owl/objectrole.owl#Object
http://www.ontologydesignpatterns.org/cp/owl/objectrole.owl#Role
http://www.ontologydesignpatterns.org/cp/owl/objectrole.owl#hasRole
http://www.ontologydesignpatterns.org/cp/owl/objectrole.owl#isRoleOf
http://www.ontologydesignpatterns.org/cp/owl/parameter.owl#Concept
http://www.ontologydesignpatterns.org/cp/owl/parameter.owl#Parameter
http://www.ontologydesignpatterns.org/cp/owl/parameter.owl#hasParameter
http://www.ontologydesignpatterns.org/cp/owl/parameter.owl#hasParameterDataValue
http://www.ontologydesignpatterns.org/cp/owl/parameter.owl#isParameterFor
http://www.ontologydesignpatterns.org/cp/owl/participation.owl#Event
http://www.ontologydesignpatterns.org/cp/owl/participation.owl#Object
http://www.ontologydesignpatterns.org/cp/owl/participation.owl#hasParticipant
http://www.ontologydesignpatterns.org/cp/owl/participation.owl#isParticipantIn
http://www.ontologydesignpatterns.org/cp/owl/partof.owl#hasPart
http://www.ontologydesignpatterns.org/cp/owl/partof.owl#isPartOf
http://www.ontologydesignpatterns.org/cp/owl/planconditions.owl#followsPrecondition
http://www.ontologydesignpatterns.org/cp/owl/planconditions.owl#hasPostcondition
http://www.ontologydesignpatterns.org/cp/owl/planconditions.owl#hasPrecondition
http://www.ontologydesignpatterns.org/cp/owl/planconditions.owl#isPostconditionOf
http://www.ontologydesignpatterns.org/cp/owl/planconditions.owl#isPostconditionPrecededBy
http://www.ontologydesignpatterns.org/cp/owl/planconditions.owl#isPreconditionFollowedBy
http://www.ontologydesignpatterns.org/cp/owl/planconditions.owl#isPreconditionOf
http://www.ontologydesignpatterns.org/cp/owl/planconditions.owl#precedesPostcondition
http://www.ontologydesignpatterns.org/cp/owl/region.owl#Region
http://www.ontologydesignpatterns.org/cp/owl/region.owl#hasRegion
http://www.ontologydesignpatterns.org/cp/owl/region.owl#hasRegionDataValue
http://www.ontologydesignpatterns.org/cp/owl/region.owl#isRegionFor
http://www.ontologydesignpatterns.org/cp/owl/sequence.owl#directlyFollows
http://www.ontologydesignpatterns.org/cp/owl/sequence.owl#directlyPrecedes
http://www.ontologydesignpatterns.org/cp/owl/sequence.owl#follows
http://www.ontologydesignpatterns.org/cp/owl/sequence.owl#precedes
http://www.ontologydesignpatterns.org/cp/owl/situation.owl#Situation
http://www.ontologydesignpatterns.org/cp/owl/situation.owl#hasSetting
http://www.ontologydesignpatterns.org/cp/owl/situation.owl#isSettingFor
http://www.ontologydesignpatterns.org/cp/owl/taskrole.owl#Role
http://www.ontologydesignpatterns.org/cp/owl/taskrole.owl#Task
http://www.ontologydesignpatterns.org/cp/owl/taskrole.owl#hasTask
http://www.ontologydesignpatterns.org/cp/owl/taskrole.owl#isTaskOf

An example of it in use¶

The pattern says what may be asserted; this says it. The graph below is a small set of individuals that instantiate the classes above and are connected by its properties, so the shape the pattern describes is visible as data rather than as a schema.

Download the example

Import this pattern into your own ontology from inside Protégé: OntoBoard → Reuse → Pattern library…, which hands it to Import terms… and writes the term list, the module, the import and the catalog entry the way ODK expects. See Working with ODK.

Something wrong with this pattern, its example or this page? Report a problem with this pattern - the form opens with the pattern filled in, and a title and a sentence are all it needs.