1 Activities about CPPA in Asia Region Yukinori Saito Electronic Commerce Promotion Council of Japan (ECOM, 4 th OASIS ebXML CPPA TC Reston Meeting June 3rd, PAA 2.INNODIGITAL 3.NII 4.Consideration

2 PAA’s Activities about CPPA Why adopted CPPA? PAA thinks that the function of Party Id and Certificate are very important. PAA adopted CPPA specification as an infrastructure of these functions. PAA designed this system according to ebXML Vision. -Register CPPs of Service Providers and Trading partners to R&& -Discover targeted CPP -Create CPA and make agreement How adopted CPPA? Current Status (Version of CPPA) -PAA developed CPPA management system based on CPPA V1.0. -Now, studying CPPA V2.0. (Project Status) -Testing phase between Trade-Van (Taiwan) and Tradelink (Hong Kong) Example of CPP & CPA -CPP of Trade-Van -CPA between Trade-Van and Tradelink -Contents of examples of CPP and CPA are testing data but relatively close to the real data.

3 INNODIGITAL's Activities about CPPA (1/2) Position of INNODIGITA L -KIEC (Korea Institute for Electronic Commerce) manages ebXML POC in Korea. -INNODIGITAL Co., Ltd. developed POC system. And also INNODIGITA developed and are providing some software products supporting CPPA, MS, and R&R. How adopting CPPA INNODIGITAL designed this system according to ebXML Vision. -Register CPPs to R&R -Discover targeted CPP -Create CPA and make agreement Current Status (Version of CPPA) -INNODIGITAL developed CPPA management software product named ‘Vega CPPA Composer for ebXML’ based on CPPA V1.0. -Now, upgrading to CPPA V2.0. Will deliver the next version within a few months. Example of CPP & CPA -CPP of Buyer -CPP for Seller -CPA between Buyer and Seller -These examples are created by using the tool ‘Vega CPPA Composer for ebXML’ - Contents of examples of CPP and CPA are relatively same to the examples of Appendix of CPPA V1.0.

4 Issues about CPPA -Role specification is not clear. -Others Consideration and Next Step (Transport Protocol) -INNODIGITAL now supports HTTP only. In the near future INNODIGITAL will support SMTP. Two or three protocols are sufficient in real business. (Automated Negotiation) -INNODIGITAL expects Negotiation specification. In future INNODIGITAL will support Automated Negotiation. Thoughts of Compatibility -The next version of CPPA (V3.0) should keep downward compatibility to V2.0. Some companies that will adopt V3.0, want to exchange CPP/CPA data between previous system based on V2.0. INNODIGITAL's Activities about CPPA (2/2)

5 NII’s Activities about CPPA Position of NII -TCA (Taipei Computer Association) manages ebXML POC in Taiwan. -NII (National Information Infrastructure Enterprise Promotion Association) developed POC system. DevelopmentNII developed CPPA editing tool. By this editing tool, NII created some CPP and CPA. Current Status (Version of CPPA) -NII developed CPPA editing tool based on CPPA V1.0. -Now, there is no plan to upgrade to V2.0. Example of CPP & CPA - Contents of examples of CPP and CPA are relatively same to the examples of Appendix of CPPA V1.0. Questions -In defining the DeliveryChannel element, a Characteristics element is required to specify the security requirements of this delivery channel. While the DocExchange element referred by the DeliveryChannel also specifies the security requirements. It is difficult to understand relations between these characteristics data and how to define these data. -Regarding the transportId and docExchangedId, are they named arbitrarily? Or they are defined based on some other “core components”? For example, transportId “N05” may represent “Sending Protocol = HTTP 1.1 and Receiving Protocol = HTTP 1.1”? If “N05” is not a pre-defined “core component”, will there be any problems for two parties to come to an agreement in choosing the appropriate IDs since they may use different names to refer to the same thing?

6 Consideration to CPPA specification by these three projects 1. Full fledged examples (like Appendix A and B) are very important. These examples are some kinds of templates of CPP/CPA. Implementers or users see these examples, and develop software products or XML files of CPP/CPA. 2. Users and Implementers look that CPPA specification is important. They adopted or will adopt CPPA specification besides MS specification. 3. Some parts of CPPA specification are difficult for users to understand. Some suitable comments (in V3.0), or some implementation guide book will be appreciated for users. For example, -How to specify MessagingCharacteristics under DeliveryChannel and ReliableMessaging element under DocExchange element -How to specify ID number (e.g. transportId, docExchangedId) and how to arrange associated elements to CPA -How to design plural CanSend and CanReceive elements under ServiceBinding element. 4. Some guideline or rule or thoughts of compatibility between versions is necessary. -INNODIGITAL and XML/EDI standardization committee of ECOM says CPPA V3.0 should keep downwards compatibility to V2.0.