1. A Declarative Approach to Electronic Business Ching-Long Yeh Department of Computer Science and Engineering Tatung University Taipei 104 Taiwan chingyeh@cse.ttu.edu.tw http://www.cse.ttu.edu.tw/chingyeh

2. A Declarative to EB2 Abstract EB standards provide the neutral basis of interoperability between trading partner Moving from procedural approach to declarative approach Representation of EB standards using the ontology technique Declarative approach to EB implementation

3. Electronic Commerce Evolution of electronic commerce –B2C, human-to-machine, online catalogue service –B2B, AP-to-AP, EB standards –RosettaNet 、 ebXML 、 BizTalk 。 Transport, routing, packaging Business processes, business documents Company ACompany B Transport, routing, packaging Business processes, business documents Backend AP

4. A Declarative to EB4 General EB Architecture EB standard architecture is divided into –Upper level: Standard business processes and document –Lower level: Services for message transport, routing and packaging Popular standards –Horizontal integration: ebXML –Vertical integration: RosettaNet (Information Technology, Electronic Component and Semiconductor Manufacturing) –Messaging service: BizTalk Framework Transport, routing, packaging Business processes, business documents

5. A Declarative to EB5 ebXML Technical Architecture

6. A Declarative to EB6 ebXML Infrastructure EB infrastructure consists of 1.Trading partner’s information Collaboration Protocol Profile (CPP) and Collaboration Protocol Agreement (CPA ） 2.Business process and information meta model Business Process Schema Specification 3.Core component and core library functionality 4.Registry functionality 5.Messaging service functionality Common BP and vocabulary

7. A Declarative to EB7 CPP Structure <CollaborationProtocolProfile xmlns="http://www.ebxml.org/namespaces/tradePartner" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.1">......... text

8. A Declarative to EB8 CPA Structure <CollaborationProtocolAgreement xmlns="http://www.ebxml.org/namespaces/tradePartner" xmlns:bpm="http://www.ebxml.org/namespaces/businessProcess" xmlns:ds = "http://www.w3.org/2000/09/xmldsig#" xmlns:xlink = "http://www.w3.org/1999/xlink" cpaid="YoursAndMyCPA" version="1.2"> 1988-04-07T18:39:09 1990-04-07T18:40:00 <ConversationConstraints invocationLimit = "100" concurrentConversations = "4"/> … … any combination of text and elements any text

9. 1.Any Party may register its CPPs to an ebXML Registry. 2.Party B discovers trading partner A (Seller) by searching in the Registry and downloads CPP(A) to Party B’s server. 3.Party B creates CPA(A,B) and sends CPA(A,B) to Party A. 4.Parties A and B negotiate and store identical copies of the completed CPA as a document in both servers. This process is done manually or automatically. 5.Parties A and B configure their run-time systems with the information in the CPA. 6.Parties A and B do business under the new CPA. CPP(A) CPP(B) CPP(X) CPP(Y) CPP(Z) 1. CPA(A,B) (Document)(Exec. codet) CPA(A,B) (Document)(Exec. codet) 2. 3.4. 5. 6. Party A (Seller, Server) Party B (Buyer, Server) Registry Working Architecture of CPP/CPA

10. A Declarative to EB10 Business Process Schema Concept

11. A Declarative to EB11 Business Process Schema in XML

12. A Declarative to EB12 Procedural Approach to EB Specifications –Not machine-readable –Need human interpretation Lack of partner discovery mechanism (registry, CPP, CPA) Example: RosettaNet

13. A Declarative to EB13 Declarative Approach to EB Specifications –Machine-readable (Business Process, Document, and Vocabulary in either UML or XML) –Enabling automatic code generation Partner discovery mechanism (registry, CPP, CPA) Example: ebXML

14. A Declarative to EB14 Forming CPA by Automatic Negotiation Packaging Transport Rol e Packaging Transport Rol e matches Basic tasks of forming CPA

15. Rule-based Formation of CPA Ontology (BPS, BD, CC) BPS: Business Process Schema BD: Business Document CC: Core Components Inference Engine Rule Base RDF triples store Prolog rules Web Server Input: CPP 1,CPP 2 Result: CPA or difference

16. A Declarative to EB16 Two-Layer Agent-Mediated EB Architecture We propose a two-layer agent-mediated EB architecture, where –The Upper Layer consists of agents that play the role of Business Collaboration and Choreography in ebXML, –The Lower Layer consists of agents each of which accomplishes a basic Business Transaction in ebXML.

18. Interactions between BT Agents

19. Interactions between BC Agents

20. Generation of Execution Code from CPA Inference Engine Rule Base CPA BC Agent Code BT Agent Code

21. A Declarative to EB21 Implementation

22. A Declarative to EB22 Conclusions EB standards are moving towards declarative approach. We propose a declarative approach to EB implementation –Ontology –Rule-based –Generation of execution codes from specification documents