Upper-level OWL ontology for Processes. Part of the DAML-S/OWL-S effort; see http://www.daml.org/services/.
A Process can have at most one name, but names need not be unique.
This is a deprecated usage; expandsTo is preferred.
This is a deprecated usage; collapsesTo is preferred.
A CompositeProcess must have exactly 1 composedOf property.
Invocable is a flag that tells whether the CompositeProcess bottoms out in atomic processes. (If so, it is "invocable".)
A computed input is a single expression that characterizes the inputs required by a composite process, and the conditions under which they are required. This expression may, if needed, tie together 2 or more inputs; for example, "either a credit card number, or a bank account number must be given", or "if product id starts with 'M', no shipping method need be given". Additionally, this expression may refer to things other than inputs; for example; "if user's credit rating is 'excellent' or better, Social Security number is not required", or "if product weight is less than 1 lb., no shipping myth did need be given". A "computed" input is so named because it is meant to be computed automatically by some tool, by inspecting the makeup of the composite process. The language used to represent a computed input is not specified here, and will be the subject of future work; hence, the use of Thing as range. It will require expressiveness greater than that of OWL.
A computed output is a single expression that characterizes the outputs required by a composite process, and the conditions under which they are required. See comment for computedInput.
A computed precondition is a single expression that characterizes the preconditions of a composite process, based on the preconditions of its sub processes.
A computed effect is a single expression that characterizes the effects of a composite process, based on the effects of its sub processes.
A CompositeProcess can have at most one invocable property. Similarly for computedInput, computedOutput, computedEffect, and computedPrecondition.
The components propery of a control construct holds a specific arrangement of subprocesses or control constructs. The range is declared at each subclass of ControlConstruct.
A ProcessComponent is either a Process or a ControlConstruct.
A ServiceModel describes how a Service works, and a ProcessModel is a type of ServiceModel (the only type being defined for OWL-S). See also the introductory comments to Service.daml.
In the case of a composite process, indicates the top-level process class.
A ProcessControlModel is used to monitor and control execution of a Process. This is just a "stub" for now; will be developed further in future releases of OWL-S.
A ProcessModel can have at most one Process and one ProcessControlModel.
Interval of time allowed for completion of the process component (relative to the start of process component execution).
A ProcessComponent can have at most one of each of the restricted properties.