Submissions:BasicPlan

From Odp

(Difference between revisions)
Jump to: navigation, search
(Imported from OWL file.)
m (Text replace - 'Include Image' to 'Graphical representation')
Line 1: Line 1:
{{Content_OP_Proposal_toolbar}}
{{Content_OP_Proposal_toolbar}}
-
{{Include Image
+
{{Graphical representation
|ImageName=
|ImageName=
}}
}}

Revision as of 12:33, 1 March 2010


This pattern has been certified.

Related submission, with evaluation history, can be found here

If you are a member of quality committee please visit the

evaluation section

If you are author of this proposal or you want to contribute to this pattern's review, you can:

In general, it could be useful to visit the evaluation section to have information about the evaluation process of this proposal

Current revision ID: 8065

Diagram (this article has no graphical representation)

General description

Name: BasicPlan
Submitted by: AldoGangemi
Also Known As:
Intent:
Domains:
Competency Questions:
Solution description:
Reusable OWL Building Block: http://www.ontologydesignpatterns.org/cp/owl/basicplan.owl (923)
Consequences:
Scenarios:
Known Uses:
Web References:
Other References:
Examples (OWL files):
Extracted From:
Reengineered From:
Has Components:
Specialization Of:
Related CPs:


Elements

The BasicPlan Content OP locally defines the following ontology elements:

ObjectProperty conceptualizes (owl:ObjectProperty) A relation stating that an Agent is internally representing a SocialObject . E.g., 'John believes in the conspiracy theory'; 'Niels Bohr created the solar-system metaphor for the atomic theory'; 'Jacques assumes all swans are white'; 'the task force members share the attack plan'.
conceptualizes page
ObjectProperty executesTask (owl:ObjectProperty) A relation between an action and a task, e.g. 'putting some water in a pot and putting the pot on a fire until the water starts bubbling' executes the task 'boiling'.
executesTask page
ObjectProperty isConceptualizedBy (owl:ObjectProperty) A relation stating that an Agent is internally representing a Description . E.g., 'John believes in the conspiracy theory'; 'Niels Bohr created a solar-system metaphor for his atomic theory'; 'Jacques assumes all swans are white'; 'the task force shares the attack plan'.
isConceptualizedBy page
ObjectProperty isExecutedIn (owl:ObjectProperty) A relation between an action and a task, e.g. 'putting some water in a pot and putting the pot on a fire until the water starts bubbling' executes the task 'boiling'.
isExecutedIn page
ObjectProperty isParametrizedBy (owl:ObjectProperty) The relation between a Parameter, e.g. 'MajorAge', and a Region, e.g. '>17 year'.
isParametrizedBy page
ObjectProperty isSatisfiedBy (owl:ObjectProperty) A relation between a Situation and a Description, e.g. the execution of a Plan satisfies that plan.
isSatisfiedBy page
ObjectProperty parametrizes (owl:ObjectProperty) The relation between a Parameter, e.g. 'MajorAgeLimit', and a Region, e.g. '18_year'.

For a more data-oriented relation, see hasDataValue

parametrizes page
ObjectProperty satisfies (owl:ObjectProperty) A relation between a Situation and a Description, e.g. the execution of a Plan satisfies that plan.
satisfies page
Class GoalSituation (owl:Class) A goal situation is a situation that satisfies a goal.Opposite to the case of subplan executions, a goal situation is not part of a plan execution.In other words, it is not true in general that any situation satisfying a part of a description, is also part of the situation that satisfies the whole description. This helps to account for the following cases: a) Execution of plans containing abort or suspension conditions (the plan would be satisfied even if the goal has not been reached, see below), b) Incidental satisfaction, like when a situation satisfies a goal without being intentionally planned (but anyway desired).
GoalSituation page


Scenarios

Scenarios about BasicPlan

No scenario is added to this Content OP.

Reviews

Reviews about BasicPlan

There is no review about this proposal. This revision (revision ID 8065) takes in account the reviews: none

Other info at evaluation tab

The basic plans. This content ontology design patterns represents plans descriptions and their executions. It is defined by combining and expanding other CPs: basic plans description, basic plans execution, and object role. Expansion involves the partial clone of ontology elements from DOLCE Ultra Lite and Plans Lite ontologies.

Personal tools
Quality Committee
Content OP publishers