Abstract: A semantically aware relational database management system includes suitable programming to relate attributes of the relational database to semantic equivalents of such attributes. In response to receiving a query, the relational database management system performs at least one semantically aware operation on the data in the relational database in order to determine what data is to be retrieved in response to the query. Results of the query presented to a user may include data derived from performing the semantically aware operations.

Abstract: A flexible workflow is described that includes a pocket of flexibility. The pocket of flexibility may include workflow fragments that may be joined together, subject to pre-defined constraints. In implementing the flexible workflow, a user may encounter the pocket of flexibility, and select from the fragments to construct a workflow that is consistent with the user's current needs. The fragments may be incrementally presented to the user on a user interface, such that only those fragments determined to be combinable in a valid way may be selected by the user. In this way, a user who may have little experience with workflow languages or terminology may be able to use the flexible workflow, and be confident that the result is valid. Thus, difficulties in dealing with change in workflow systems may be mitigated, and this mitigation may be achieved without compromising the simplicity and generic nature of a workflow language.

Abstract: Techniques for making transformations between combined and individual workflows are described. For example, a first party, such as a first enterprise, may have a pre-determined workflow designed to implement a plurality of tasks. Similarly, a second party may have its own pre-determined workflow designed to implement a separate plurality of tasks. All of the tasks associated with the first workflow and the second workflow may be combined into a combined workflow having a task order that, when executed, provides a desired result of a business collaboration between the first party and the second party. Ordering tasks operable to implement the order of the combined workflow also may be added to achieve the desired result.

Abstract: A semantically aware relational database management system includes suitable programming to relate attributes of the relational database to semantic equivalents of such attributes. In response to receiving a query, the relational database management system performs at least one semantically aware operation on the data in the relational database in order to determine what data is to be retrieved in response to the query. Results of the query presented to a user may include data derived from performing the semantically aware operations.

Abstract: A semantically aware relational database management system includes suitable programming to relate attributes of the relational database to semantic equivalents of such attributes. In response to receiving a query, the relational database management system performs at least one semantically aware operation on the data in the relational database in order to determine what data is to be retrieved in response to the query. Results of the query presented to a user may include data derived from performing the semantically aware operations.

Abstract: A workflow model is described. In one example of the workflow model, a first workflow is associated with a first party, and a first workflow view is used to represent an abstraction of the first workflow. Similarly, a second workflow is associated with a second party, and a second workflow view is used to represent an abstraction of the second workflow. Then, a coalition workflow view referencing the first workflow view and the second workflow view provides a collaborative workflow that specifies tasks that the first party and the second party are required to perform. In this way, multiple parties may easily partner with one another to accomplish a business objective, while maintaining a level of confidentiality of their workflow processes.

Abstract: A semantically aware relational database management system includes suitable programming to relate attributes of the relational database to semantic equivalents of such attributes. In response to receiving a query, the relational database management system performs at least one semantically aware operation on the data in the relational database in order to determine what data is to be retrieved in response to the query. Results of the query presented to a user may include data derived from performing the semantically aware operations.

Abstract: Techniques for modifying an abstraction level of a workflow are described. For example, a workflow may be analyzed to determine a first plurality of tasks, and the first plurality of tasks may then be combined into a first virtual task within an abstracted workflow. Then, the first virtual task may be linked to the first plurality of tasks, such that a virtual execution of the abstracted workflow corresponds to an actual execution of the workflow. In this way, the abstracted workflow may be shared with other parties, while a level of confidentiality associated with the workflow is preserved.

Abstract: A flexible workflow is described that includes a pocket of flexibility. The pocket of flexibility may include workflow fragments that may be joined together, subject to pre-defined constraints. In implementing the flexible workflow, a user may encounter the pocket of flexibility, and select from the fragments to construct a workflow that is consistent with the user's current needs. The fragments may be incrementally presented to the user on a user interface, such that only those fragments determined to be combinable in a valid way may be selected by the user. In this way, a user who may have little experience with workflow languages or terminology may be able to use the flexible workflow, and be confident that the result is valid. Thus, difficulties in dealing with change in workflow systems may be mitigated, and this mitigation may be achieved without compromising the simplicity and generic nature of a workflow language.

Abstract: A workflow model is described. In one example of the workflow model, a first workflow is associated with a first party, and a first workflow view is used to represent an abstraction of the first workflow. Similarly, a second workflow is associated with a second party, and a second workflow view is used to represent an abstraction of the second workflow. Then, a coalition workflow view referencing the first workflow view and the second workflow view provides a collaborative workflow that specifies tasks that the first party and the second party are required to perform. In this way, multiple parties may easily partner with one another to accomplish a business objective, while maintaining a level of confidentiality of their workflow processes.

Abstract: Techniques for modifying an abstraction level of a workflow are described. For example, a workflow may be analyzed to determine a first plurality of tasks, and the first plurality of tasks may then be combined into a first virtual task within an abstracted workflow. Then, the first virtual task may be linked to the first plurality of tasks, such that a virtual execution of the abstracted workflow corresponds to an actual execution of the workflow. In this way, the abstracted workflow may be shared with other parties, while a level of confidentiality associated with the workflow is preserved.