]> This is a "meta-property" to specify which properties makeup a complexObject (an object consisting of a main object and several part objects). This property is used by the copyComplex build-in that can be used to model operator effects. copyComplex copies not only the specified individual, but all individuals that can be reache via subproperties of this property. The Goals this task or method contribute to reach. A Method is "implemented" by decomposition into a strict sequence of Tasks and Operators. This is modeled by the step-subproperties of this Property step1, step2, ..., stepn. Operators may have further parameters beside the used IOObjects, e.g. some parts of the DomainModel without IOObjects to operate on. Which optional SubGoals are compatible with which MainGoals is modeled with this property. All the IOObjects produced by Operator applications. A Task can be solved by several Methods, specified by this property. The user is queried for all start objects of Goals modeled with that relation. Goals and startObjects together build the planning problem instance to be solved by he planner. All the IOObjects used by Operator applications. The DomainModel elements the Task or Method works on, i.e. uses and produced by the operators it is finaly decomposed to. Abtract grouping of operators, useful esp. for inheritance of pararameter restrictions, conditions & effects. The operators, that can be executed via a Service-Call The modeling of the Planning Domain goes here. future extension, this represent "control-structure" services, a typical example is cross-validation, which dominates a "ModelingEvaluation"-task. The modeling of goals go here. Goals startObjects to be applied on. The eProPlan-Goal Plugin can be used to ask the user to specify Goals and start Object description. The objects used and produced by the Operators in our Planning Domain future extension future extension There is one main goal theuser is asked for. Depending on the main goal she can specify different SubGoals, which ones are allowed is specified using the possibleSubGoal Property Any further informations we need to describe IOObjects in detail for operator conditions. The Operators in the Planning Domain. The ePropPlan-Operator Plugin can be used on sub concepts of this concept to model Operator conditions and effects. Operators uses and produces IOObjects, further parameters can be specified using the parameter Objectproperty to MetaData or the simpleParameter DataProperty. Operators should not have Equivalent Classes, as the TBox reasoner dos not know their full semantic, which includes the conditions and effects, BUT the eProPlan-I assumes that Operators are campletely described by a) superclasses b) conditions, and c) effects. So if for any 2 operators eProPlan-I find that their superclass-restriktions subsume each other and conditions & effects do subsume each other as well then eProPlan-I infers subsumption between the Operators. This type marks if an operator is executable via a service (BasicOperator or DominatingOperator) or is "execute" by the planer via unfolding ( LoopOperator or MacroOperator) or just an abstract grouping of Operators (AbstractOperator) The Tasks, their possible Methods, and the decomposition of Methods into (Sub-) Tasks and Operators, i.e. the HTN as used by some planning methods.