Presented at RIA WG TC meeting days in OMG to initiate RIA Component Interoperability RFI

1. Specifications for RIA Component Interoperability RFI Draft March, 2010 TC Meeting in Jacksonville, FL Sangchual CHA / chasc@tobesoft.com Prof. Sungwoon CHOI / choisw@mju.ac.kr 1

2. Agenda RFI Overview Prototype of Interoperable RIA Components RFI Questionnaire Detail 2

3. RFI Overview 3

4. RIA WG Scope of Effort Provide RIA platform architecture which supports the next generation web application execution platform providing interactive, rich and responsive user experience, and high implementation productivity. Provide RIA component model with publicinterface definition, component architecture, packaging, and deployment, which guarantees interoperability. Provide RIA description language specification of RIA with the abstract syntax and the semantic property. 4

5. RFI Overview “Specifications for RIA Component Interoperability” Request for Information To promote industry consensus on technical specifications for interoperable RIA components. To collect information from stakeholders about Requirements for interoperable RIA components. Technical perspective enabling the interoperability. 5

6. Stakeholder RIA Application Developer To build RIA Application through composition of RIA Components. RIA Component Vendor To define RIA components. (Interfaces, Behaviors, etc) To implement and publish RIA components. RIA Platform Vendor To provide RIA components running platform. To manage RIA component deployment processes. 6

7. Stakeholders RIA Application Developers Environment Requirement Technical Perspective RIA Component Vendors RIA Platform Vendors 7

8. From RIA Application Developers Industry they are involved, and System they are building. Sort of RIA Platform they are working on. Benefits of RIA platform for client application. Requirement for the interoperable RIA components. 8

9. From RIA Component Vendors Target RIA platform. Sort of RIA Component (Chart, Grid, etc). Component Definition. Requirements for the interoperable RIA components. Technical issues and mission features. 9

10. From RIA Platform Vendors Technical mechanism for interoperable RIA component. Technology for component packaging and deployment. 10

11. Prototype 11

12. Prototype of Interoperable RIA Component Proof of concept. Find out missing features. Ajax, Flex, Silverlight, XPLATFORM 12

13. Cited RIA Application 13

14. Composed RIA Component RIA Application - Container XPLATFORM : Container RIA Platform Ajax Grid Component AJAX : Browser as Platform Flex Grid, Edit Component Flex : Flash Platform Silverlight Edit Component Silverlight : Silverlight Platform 14

15. Features Call a method() in B RIA PlatformA RIA PlatformB Get an attribute in B Add a event handler in A into B Dispatch an event as calling the event handler in A 15

16. RFI Questionnaire 16

17. RIA Application Developers (1/4) ■What sort of industry and system do you work in ? - Industry. (e.g. Finance, Telecommunication, Education, Government) _______________________________________ - System (e.g. CRM, ERP, SCM) _______________________________________ 17

18. RIA Application Developers (2/4) ■Which technologies have been adapted as client application platform ? Please mark all adapted RIA platforms, and describe in case of Others. □ Pure Web, e.g. Ajax technology. □ Web with Plug-in, e.g. ActiveX, Java Applet □ Virtual Machine or Sand-box, e.g. Adobe Flex, MS Silverlight. □ Others ( ) 18

19. RIA Application Developers (3/4) ■ What are the main benefits of RIA platform? Please mark all benefits to you, and describe in case of Others □ Graphic effects and Look & Feel □ High performance with low system usage. □ Interactive data visualization. □ Local device utilization □ Stateful network session □ Direct(Socket) connection to legacy system □ Others ( ) 19

20. RIA Application Developers (4/4) ■Do you have any need for supporting interoperability among heterogeneous RIA platform.? If so, What are the missing features, problems and/or issues with implementation? Please describe in more detail. 20

21. RIA Component Vendors (1/4) ■What is your target RIA platform ? Please mark all target RIA platforms, and describe in case of Others □ MS Silverlight / WPF □ Adobe Flex □ Ajax Framework □ Others ( ) 21

22. RIA Component Vendors (2/4) ■ What sort of RIA component do you provide? Please mark all and describe if you mark Others. □ Interactive data visualization components □ Grid, □ Chart , □ Others □ Local Device Interface □ Network □ Others ( ) 22

23. RIA Component Vendors (3/4) ■How do you define interfaces of RIA component ? Do you use any global standard for defining interfaces? Do you find insufficient features from the standards? If then, Please explain in more detail. 23

24. RIA Component Vendors (4/4) ■ Do you need to integrate your components with RIA applications and/or components running on different platforms? If so, what are the issues, problems and/or missing features making them collaborate? 24

25. RIA Platform Vendors (1/2) ■ Whatis technical mechanism for enabling RIA component to be interoperable? Please describe in more detail. 25

26. RIA Platform Vendors (2/2) What kind of technology do you provide for component packaging and deployment? 26

27. Response Due Date 31 May 2010 Language English, Japanese, Korean Who would be supposed to response ? Samsung Electronics, Hyundai Capital, etc (In Korea) Hitachi System (In Japan) And so forth… 27

28. Screen shots of demo 28

29. XPLATFORM from/to Ajax Call the method of Ajax Grid Component Get the data of Ajax Grid Component 29

30. XPLATFORM from/to Ajax window.TOBEENV.form.button.click() Document.[Button Object].Click() Document.[Input Element].value window.TOBEENV.form.input.value 30

31. XPLATFORM from/to Flex Call the method of Flex Grid Component Call the Event handler 31

32. XPLATFORM from/to Flex CallFunction Method Flex on Flash Platform Fscommand event 32

33. XPLATFORM from/to Silverlight Get the data of Silverlight Component Call the method of Silverlight Component 33

34. XPLATFORM from/to Silverlight Document.[hidden Element].set() hidden Element].set() <input type=“hidden” Document.[hidden Element].value [hidden Element].value 34