1. Inferring, Validating, and Coordinating the Commitments in a Workflow Jiangbo Dang and Michael N. Huhns Dept. of Computer Science & Engineering University of South Carolina ICWS 2006 Presented by: Jingshan Huang Computer Science & Engineering Dept. University of South Carolina

2. The Relationships among an OWL-S, a CPN, and Commitments for Agents A commitment has the form C(a;b;q), where a is its creditor, b is its debtor, and q is the condition the debtor will bring about. C(a;b;p->q) is a conditional commitment, where p is the condition Commitment can be viewed in IOPR form

3. Motivating Scenario Service agents negotiate with each other to reach beneficial contracts to execute a workflow and establish commitments for managing, monitoring, and coordinating its execution Product Requestor A Driller E Parts Maker D Analyzer C Product Maker B

4. Research Issues: Motivating Scenario Service agents negotiate with each other to reach beneficial contracts to execute a workflow and establish commitments for managing, monitoring, and coordinating its execution

5. A Composed Service in OWL-S

6. IOPRs

7. A Workflow as a Colored Petri Net

8. Example Outputs ProductMaker B owns three atomic processes: CheckProdDesignStatus, DesignProduct, GeneratePartRequirement [CheckProdDesignStatus] Preconditions: Completed(SendProdRequirement) Result: Set Approved true or false Input: ProductRequirements ^ AnalysisReport Output: ProductRequirements ^ AnalysisReport [DesignProduct] Preconditions: Completed(CheckProdDesignStatus) ^ not approved Result: Input: ProductRequirements Output: ProductDesign [GeneratePartRequirement] Preconditions: Completed(CheckProdDesignStatus) ^ approved Result: Input: ProductDesign Output: PartsRequirements

9. The Relationships among an OWL-S, a CPN, and Commitments for Agents

10. Questions?