Specifications for RIA Com-ponent Interoperability
RFI Draft
March, 2010 TC Meeting in Jacksonville, FL
Sangchual CHA / [email protected]. Sungwoon CHOI / [email protected]
1
Agenda
• RFI Overview
• Prototype of Interoperable RIA
Components
• RFI Questionnaire Detail
2
RFI Overview
3
RIA WG Scope of Effort• Provide RIA platform architecture which
supports the next generation web application ex-ecution platform providing interactive, rich and responsive user experience, and high implemen-tation productivity.
• Provide RIA component model with public interface definition, component architecture, packaging, and deployment, which guarantees interoperability.
• Provide RIA description language speci-fication of RIA with the abstract syntax and the semantic property.
4
RFI Overview
• “Specifications for RIA Component Interop-erability” Request for Information
• To promote industry consensus on technical specifications for interoperable RIA compo-nents.
• To collect information from stakeholders about– Requirements for interoperable RIA components.
– Technical perspective enabling the interoperability.
5
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
Stakeholders
RIA Application Developers
RIA Component Vendors
RIA Platform Vendors
Technical Perspec-tive
Requirement
Environment
7
From RIA Application De-velopers
• Industry they are involved, and Sys-tem they are building.
• Sort of RIA Platform they are work-ing on.
• Benefits of RIA platform for client application.
• Requirement for the interoperable RIA components.
8
From RIA Component Ven-dors
• Target RIA platform.• Sort of RIA Component (Chart, Grid,
etc).• Component Definition.• Requirements for the interoperable
RIA components.• Technical issues and mission fea-
tures.
9
From RIA Platform Vendors
• Technical mechanism for interoper-able RIA component.
• Technology for component packag-ing and deployment.
10
Prototype
11
Prototype of Interoperable RIA Component
• Proof of concept.• Find out missing features.• Ajax, Flex, Silverlight, XPLATFORM
12
Cited RIA Application
13
Composed RIA Component
AJAX : Browser as Platform
Flex : Flash Platform
Silverlight : Silverlight Platform
XPLATFORM : Container RIA Platform
Ajax Grid Component
Flex Grid, Edit Component
Silverlight Edit Component
RIA Application - Container
14
Features
RIA Platform A RIA Platform B
Get an attribute in B
Call a method() in B
Dispatch an event as calling the event handler in A
Add a event handler in A into B
15
RFI Questionnaire
16
RIA Application Developers (1/4)
■ What sort of industry and system do you work in ?- Industry. (e.g. Finance, Telecommunication, Education, Gov-
ernment)_______________________________________- System (e.g. CRM, ERP, SCM)_______________________________________
17
RIA Application Developers (2/4)
■ Which technologies have been adapted as client appli-cation platform ? Please mark all adapted RIA plat-forms, 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 Sil-
verlight.□ Others ( )
18
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
RIA Application Developers (4/4)
■ Do you have any need for supporting interoper-ability among heterogeneous RIA platform.? If so, What are the missing features, problems and/or issues with implementation? Please describe in more detail.
20
RIA Component Vendors (1/4)
■ What is your target RIA platform ? Please mark all target RIA platforms, and describe in case of Oth-ers
□ MS Silverlight / WPF□ Adobe Flex □ Ajax Framework □ Others ( )
21
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
RIA Component Vendors (3/4)
■ How do you define interfaces of RIA compo-nent ? 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
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, prob-lems and/or missing features making them col-laborate?
24
RIA Platform Vendors (1/2)
■ What is technical mechanism for enabling RIA component to be interoperable? Please describe in more detail.
25
RIA Platform Vendors (2/2)
• What kind of technology do you provide for com-ponent packaging and deployment?
26
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
Screen shots of demo
28
XPLATFORM from/to Ajax
Call the method of Ajax Grid Compo-
nent
Get the data of Ajax Grid Compo-
nent
29
XPLATFORM from/to Ajax
window.TOBEENV.form.but-ton.click()
Document.[Input Element].value
window.TOBEENV.form.in-put.value
Document.[Button Object].Click()
30
XPLATFORM from/to Flex
Call the method of Flex Grid Compo-
nentCall the Event handler
31
XPLATFORM from/to Flex
Fscommand event
CallFunction Method
Flex on Flash Platform
32
XPLATFORM from/to Sil-verlight
Call the method of Silverlight Compo-
nent
Get the data of Sil-verlight Compo-
nent
33
XPLATFORM from/to Sil-verlight
hidden Element].set()
Document.[hidden Element].value
Document.[hidden Element].set()
<input type=“hidde
n”
[hidden Element].value
34
Top Related