Charter For RIA WG in OMG

647 views

Published on

Chartered RIA WG in OMG to show goal, missions, scope of effort.

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
647
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Good afternoon . Thank you so much for joining this presentation. My name is Sangchual CHA and working for TOBESOFT TOBESOFT is a RIA platform provider and has about 60% of market share in Korea. More than 5 RIA solution providers in Korea gathered and organized RIA Enterprise SIG last year, 2008. Through this activities we found that interoperability must be a key factor to the future of RIA technology. This is why we suggest this working group today.
  • Through this presentation, I will show what this working group is aiming . Secondary, I will tell brief history of client side application and current status of RIA. And next, I will explain the scope of effort and expected deliveries. This presentation will take about 20 minutes, after then we will have time to discuss about this issues.
  • What I want to say in this presentation is about RIA. So Have a look of the definition of RIA. Lots of definition could be shown and I choose it from Wikipedia. RIA is a Web application with desktop application characteristics . And it runs in Web browser and out of Web browser, sandbox or virtual machine.
  • Web can find easily RIA around us. Adobe, Air For example, we can download eBay desktop from eBay and it runs out of browser. eBay / Auction Service Bidding Information Data Update with Push Service It makes us to access eBay service with interactive and graphical user interface .
  • Microsoft announced Silverlight 3 this year. Silverlight is one of best tools for Rich Media Player . Silverlight Ready to Enterprise Application This screen shot is Silverlight control showcase. We can build easily enterprise application with Silverlight3.
  • This is a screen shot of RIA from TOBESOFT that I am working for. TOBESOFT RIA Platform is specialized in enterprise component and data model .
  • Goals of RIA Working Group. Primarily we have two goals. The first one is to build Industry Consensus on Interoperability . We need to raise up the consensus on interoperable RIA components and compatible Rich Internet Applications. The second one is about RIA technical specification. We need to focus on three parts. RIA Platform Architecture, RIA Component Model, RIA Application Description Language. From now, I’m going to show brief history of client application and current status of RIA
  • I’ve got two view points on client side application, functionality and availability. At the beginning of this history, we know, there was only dummy terminal at the client side. Dummy terminal haven’t got a any computing power so it just display data from Mainframe and users can access the mainframe system in specific place. It’s low functionality and low availability. The second generation is Client/Server Desktop Application. There were big changes. Client side systems have really powerful computing ability. They provide rich and interactive user interface and enable to run business logic in client side. The functionality of client application had improved dramatically in this era. But it had still low availability. we have to install the desktop program. Sometimes it was really hard because of different client side environment. And next, World Wide Web has been introduced in 1990 by Tim Berners-Lee for the purpose of sharing the result of study and research via internet. Practically, Web technology is based on standard specification. W3C, IEFT and ECMA International are web standard leading organization. HTML, Cascading Style Sheet, ECMAScript, HTTP, etc are well known Web standard technology. This global standards make Web interoperable and compatible. Almost Web browsers keep this guidelines. After then Web technology had improved as a client application platform. Lots of Client/Server based system moved to Web oriented environment because of its availability. But we lost some functionality because HTML and JavaScript provide limited functionality. And finally, we are at the stage of Rich Internet Application. RIA has matured with functionality and availability. Alright, let’s have a look of Web and RIA in depth.
  • Shift of Web After rapid spread of Web technologies, The paradigm has been shifted. After IT staffs and users recognized merits of Web, they have moved view point. IT guys have tried to apply Web technology to traditional client application area. Web technology evolved as a IT backbone in Companies. Basically view point has shifted from showing document to working environment. Web has been recognized as a working platform in companies. Browsers are not only documents viewing tool but also application running platform. Browsers execute web applications written with HTML, JavaScript, CSS. At beginning of this trial, There were just simple functions, like Visitor records, BBS and so forth. Now, we can manage our schedule, write a financial statement, share photos, view maps via Web. And we can find easily CRM, ERP applications run on Web browser with interactive and rich user interface.
  • RIA Characteristics. As I mentioned, there are shifts in Web and RIA is satisfying the requirement. There are four major characteristics as like you know. Client-Centric Application means that RIAs combine diverse IT systems together in client side. For example, enterprise users should access different types of application at same time. They input and view data with Groupware, ERP, CRM, etc. To do this, application should support single sign on, data sharing scheme between applications, process control and so forth. RIAs satisfy this requirement. RIA provide Rich, Interactive, Responsive User Interface. Graphical user interfaces and visual effects are really important factors in IT system because they improve productivity and performance. Interactive user interfaces are a visual data display panel as well as a communication channel in IT system. Client Systems consists of types of H/W and S/W resource. There are common I/O devices as like Mouse, Keyboard, monitor, etc. Web standards and web browsers support these general and common devices. But sometimes we have to use not-common devices. IC Card, Web Cam, Scanner and so on. For example in bank branch, the teller put their IC card into IC Card reader that is attached in PC for the secured authorization. And web cam is a one of essential device in communication. To utilize local resource is really important feature in enterprise IT system. And RIA make them possible. Stateful connection Basically web browser can’t keep the session context. Every web page should be fully reloaded So it is really bad for business performance and productivity. So RIA provide partial update and refresh data in certain area.
  • 70% of RIA project succeeded and 30% of users has got more than they expected. It show that RIA is being adapting successfully and will be adapted in the enterprise market.
  • RIA Platform vendors. We know well big vendors and solution providers have launched RIA platform, Adobe is the marker leader, Adobe have announced Flex and Air year ago. Microsoft also launched Silverlight, Silverlight 3 has announced this year. Actually Silverlight is based on Windows Presentation Foundation and .NET Platform Google, The solutions from Google is based on Ajax Technologies runs on Web browsers. And We can see lots of other RIA vendors. JavaFX from Sun, Eclipse Rich Client Platform from IBM. Laszlo is open-source oriented RIA platform. TEBESOFT has begun RIA business since 2002, and has about 60% market share in Korea.
  • RIA issues about interoperability and Compatibility. We have seen, lots of vendors announced and launched diverse RIA platform. Practically they, RIA platform has their own platform architecture, component model and description language. And more, all of them are hardly compatible. RIA has been evolved based on Web technology. So they have similar component model and language specification. Even 90% is same, other 10% make them incompatible. So we need to make them compatible in ways. In addition, We know RIA platform is based on Web Technology. It means that RIA inherits lots of merits from Web. So we need to focus on not losing benefits derivers from Web.
  • Scope of effort -> We suggest mainly three technical specification about RIA. -> RIA Platform Architecture / RIA Component Model / RIA Description Language -> RIA Platform Architecture, RPA : It provides RIA execution platform : It could be said runtime environment, VM. : RPA supports Interactive, Rich, Responsive User Interface : RPA provides Just – in – deployment and RIA component repository mechanism.
  • Scope of effort -> We suggest mainly three technical specification about RIA. -> RIA Platform Architecture / RIA Component Model / RIA Description Language -> RIA Platform Architecture, RPA : It provides RIA execution platform : It could be said runtime environment, VM. : RPA supports Interactive, Rich, Responsive User Interface : RPA provides Just – in – deployment and RIA component repository mechanism.
  • Scope of effort -> RIA Component model, RCM -> RCM aims the interoperability of RIA components. -> In RCM, we try to outline primitive component hierarchy and way to define component interface. -> RCM will define event flow and how to handle event and design deployment flow.
  • Scope of effort -> RIA Description Language (RDL) -> RDL consists of structural part with and behavior part with ECMAScript. In structural part, we will describe abstract syntax for application structure. And in behavior part, we will show semantic property for object, functions, event handling and orchestration. - Objects consist of File System, Math Expression, Expression Format, - Functions include user defined functions and Business logic - Data Model and Presentational Component orchestration would be important part in RDL.
  • Expected Delivers RFI / RFP / Specification Recommendation Issue RFI in this year Issue RFP next year, 2009 Close recommendation process in 2010
  • Charter For RIA WG in OMG

    1. 1. Rich Internet Application (RIA) Working Group Charter Presented by Sangchual CHA TOBESOFT [email_address]
    2. 2. Agenda <ul><li>Goal </li></ul><ul><li>Brief History </li></ul><ul><li>RIA </li></ul><ul><li>Scope of Effort </li></ul><ul><li>Expected Deliveries </li></ul>
    3. 3. RIA Definition <ul><li>Rich Internet applications (RIAs) are web applications that have most of the characteristics of desktop applications, typically delivered by way of standards based web browser plug-ins or independently via sandboxes or virtual machines. (Wikipedia) </li></ul>
    4. 4. RIA Example
    5. 5. RIA Example
    6. 6. RIA Example Gauges
    7. 7. Goal <ul><li>Industry Consensus </li></ul><ul><ul><li>RIA Component Interoperability </li></ul></ul><ul><ul><li>RIA Platform Interworking </li></ul></ul><ul><li>Recommendation of Specification </li></ul><ul><ul><li>RIA Platform Architecture </li></ul></ul><ul><ul><li>RIA Component Model </li></ul></ul><ul><ul><li>RIA Application Description Language </li></ul></ul>
    8. 8. Brief History Mainframe Computing Dummy Terminal Client / Server Desktop Application Rich Internet Application Web Client Application Availability Functionality
    9. 9. Shift of Web <ul><li>From Showing Document to Working Environment. </li></ul><ul><li>From Interlinked Document to Interactive Application. </li></ul><ul><li>From Stateless Connection to Stateful Session Context. </li></ul><ul><li>From Restricted Client Access to Utilize Local Computing Resource. </li></ul>
    10. 10. RIA Characteristics <ul><li>Client-Centric Application </li></ul><ul><li>Rich and Responsive User Experience </li></ul><ul><li>Client Computing Resource Utilization </li></ul><ul><li>Stateful Connection </li></ul>
    11. 11. RIA User Acceptance <ul><li>The Early Adaptor Phase (2004 – 2008) </li></ul><ul><li>The Early Majority Phase (2009 – 2012) </li></ul><ul><li>By Gartner Dec. 2008, MarketScope for Ajax Technology and RIA Platform </li></ul>
    12. 12. RIA Platform Vendors <ul><li>Diverse Vendor Oriented RIA Platform </li></ul><ul><ul><li>[Adobe] Flex , Air </li></ul></ul><ul><ul><li>[Microsoft] Silverlight, WPF, .NET </li></ul></ul><ul><ul><li>[Google] Google Web Toolkit (GWT) </li></ul></ul><ul><ul><li>[IBM] Eclipse Rich Client Platform (RCP) </li></ul></ul><ul><ul><li>[Sun] JavaFX, Java Virtual Machine </li></ul></ul><ul><ul><li>[Curl] Curl RIA Platform </li></ul></ul><ul><ul><li>[NexaWeb] Universal Client Platform </li></ul></ul><ul><ul><li>[Laszlo Systems] Laszlo Webtop, OpenLaszlo </li></ul></ul><ul><ul><li>[TOBESOFT] XPLATFORM </li></ul></ul>
    13. 13. RIA Issues <ul><li>Diverse RIA Platform </li></ul><ul><li>Components Interoperability based on standardized technical specification </li></ul><ul><li>Preserve Benefits delivered from Web </li></ul>
    14. 14. Scope of Effort OS RIA App. RIA App. RIA App. Component IDL Component IDL Web Browser HTML RIA Runtime Component Component Component Component RIA Description Language (RDL) RIA Component Model (RCM) RIA Platform Architecture (RPA)
    15. 15. Scope of Effort cont’d <ul><li>RIA Platform Architecture (RPA) </li></ul><ul><ul><li>Next generation web application execution platform </li></ul></ul><ul><ul><li>Interactive User Interface </li></ul></ul><ul><ul><li>Just-in-time Deployment </li></ul></ul>
    16. 16. Scope of Effort cont’d <ul><li>RIA Component Model (RCM) </li></ul><ul><ul><li>Interoperable Heterogeneous Component </li></ul></ul><ul><ul><li>Basic Component Types </li></ul></ul><ul><ul><li>Interface Description </li></ul></ul><ul><ul><li>Event Flow and Handling </li></ul></ul><ul><ul><li>Repository and Deployment </li></ul></ul>
    17. 17. Scope of Effort cont’d <ul><li>RIA Description Language (RDL) </li></ul><ul><ul><li>Language Specification of RIA </li></ul></ul><ul><ul><li>Abstract Syntax of Structural Part </li></ul></ul><ul><ul><ul><li>XML </li></ul></ul></ul><ul><ul><ul><li>Structure of Application </li></ul></ul></ul><ul><ul><li>Semantic Property of Behavior Part </li></ul></ul><ul><ul><ul><li>ECMAScript </li></ul></ul></ul><ul><ul><ul><li>Objects, Functions, Events Handling, Orchestration </li></ul></ul></ul>
    18. 18. Expected Deliveries <ul><li>RFI Draft </li></ul><ul><ul><li>TC Meeting at Dec. 2009 </li></ul></ul>

    ×