Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Seminar Report 20071127


Published on

Published in: Technology, Education
  • Be the first to comment

Seminar Report 20071127

  1. 1. Reporter: Shih-Feng Yang 2007/11/26 Seminar Report
  2. 2. <ul><li>Andres Thor, David Aumueller, Erhard Rahm. “ Data Integration Support for Mashups .” AAAI 2007 </li></ul><ul><li>Jin Yu, Boualem Benatallah, Regis Saint-Paul, Fabio Casati, Florian Daniel, Maristella Matera. “ A Framework for Rapid Integration of Presentation Components .” WWW 2007 </li></ul>
  3. 3. Outline <ul><li>Introduction </li></ul><ul><li>A Framework Architecture for Mashups </li></ul><ul><li>Online Citation Service </li></ul><ul><li>Conclusion </li></ul>
  4. 4. Introduction <ul><li>Mashup is a new type of interactive web application, combining content from multiple services or sources into a new service. </li></ul><ul><li>In this paper, they propose a framework for the development of dynamic data integration mashups. </li></ul>
  5. 5. Introduction Information From DBLP Information From Google Scholar Online Citation Service (OCS)
  6. 6. A Framework Architecture for Mashups
  7. 7. A Framework Architecture for Mashups <ul><li>They plan to implement their framework based on iFuice </li></ul><ul><ul><li>“ Information Fusion utilizing instance correspondences and peer mappings” </li></ul></ul><ul><ul><li>Focus on instance data of different sources and mappings between then rather than utilize schema mapping. </li></ul></ul><ul><li>Transformers </li></ul><ul><ul><li>Query </li></ul></ul><ul><ul><li>Fuse </li></ul></ul><ul><ul><li>Aggregate </li></ul></ul><ul><ul><li>Union </li></ul></ul>
  8. 8. A Framework Architecture for Mashups <ul><li>Example of transformers </li></ul>
  9. 9. Online Citation Service <ul><li>It allows the generation of citation counts for publication lists of authors and venues. </li></ul><ul><li>It obtains the publication list from the DBLP bibliography, and obtains the citation counts from Google Scholar. </li></ul>
  10. 10. Online Citation Service <ul><li>Query Strategy </li></ul><ul><ul><li>Query directly by the name of publication authors and venue. </li></ul></ul><ul><ul><li>Find the title pattern. First, find the important terms by TF/IDF value, then replace the irrelevant term by ‘*’. Ex. “A survey of approaches to automatic schema matching”-> “survey * approaches * * schema matching”. </li></ul></ul><ul><ul><li>If publications don’t have matching counterparts, then use keyword strategy by the publication title. </li></ul></ul>
  11. 11. Online Citation Service <ul><li>Query Strategy </li></ul>
  12. 12. Conclusion <ul><li>They proposed a framework architecture supporting the development of mashups incorporating dynamic data integration. </li></ul><ul><li>The framework provides a script-based definition of mashups and the use of multiple query strategies for accessing external data sources. </li></ul>
  13. 13. <ul><li>Andres Thor, David Aumueller, Erhard Rahm. “ Data Integration Support for Mashups .” AAAI 2007 </li></ul><ul><li>Jin Yu, Boualem Benatallah, Regis Saint-Paul, Fabio Casati, Florian Daniel, Maristella Matera. “ A Framework for Rapid Integration of Presentation Components .” WWW 2007 </li></ul>
  14. 14. Outline <ul><li>Introduction </li></ul><ul><li>Guiding Principles </li></ul><ul><li>Presentation Integration Framework </li></ul><ul><li>Implementation </li></ul><ul><li>Conclusion </li></ul>
  15. 15. Introduction <ul><li>Creating composite applications from reusable components is important in software engineering and data management. </li></ul><ul><li>EAI (Enterprise Application Integration) </li></ul><ul><li>This research focus on presentation level integration rather than data or application level integration. </li></ul>
  16. 16. Introduction <ul><li>Web mashups perform integrations both at the application level and the presentation level. </li></ul><ul><li>But there is very little support in terms of model and tools for presentation level. </li></ul><ul><li>The goal is to build composite applications that leverage the components’ individual UIs to produce composite applications possibly with rich and highly interactive user interfaces. </li></ul>
  17. 17. Introduction <ul><li>Example: The national park guide </li></ul> Flickr.Net Google Map
  18. 18. Guiding Principles <ul><li>Lessons Learned from EAI </li></ul><ul><ul><li>Simple, formal, human readable, modular </li></ul></ul><ul><li>Differences between Presentation and Application Integration </li></ul><ul><ul><li>Event-driven vs. Methods </li></ul></ul><ul><ul><li>UI configuration </li></ul></ul><ul><ul><li>Security and Reliability are not so important in PI </li></ul></ul>
  19. 19. Presentation Integration Framework Component Model Composition Model Runtime Middleware
  20. 20. Presentation Integration Framework <ul><li>Component Model </li></ul><ul><ul><li>Events </li></ul></ul><ul><ul><li>Operations </li></ul></ul><ul><ul><li>Properties </li></ul></ul><ul><ul><li>Presentation modes </li></ul></ul>
  21. 21. Presentation Integration Framework <ul><li>Composition Model </li></ul><ul><ul><li>Event subscriptions </li></ul></ul><ul><ul><li>Data mappings </li></ul></ul><ul><ul><li>Additional integration logic </li></ul></ul><ul><ul><li>Layout information </li></ul></ul>
  22. 22. Presentation Integration Framework <ul><li>Language Representation </li></ul><ul><ul><li>They propose XPIL (Extensible Presentation Integration Language) </li></ul></ul><ul><ul><li>XPIL is a language which contains two sets of XML elements (component model and composition model). </li></ul></ul>
  23. 23. Presentation Integration Framework <ul><li>Runtime Middleware </li></ul><ul><ul><li>Event automation </li></ul></ul><ul><ul><ul><li>Capturing event from the publishing component. </li></ul></ul></ul><ul><ul><ul><li>Automatically invoking operations of the subscribing components. </li></ul></ul></ul><ul><ul><li>Component adapters and wrappers </li></ul></ul><ul><ul><ul><li>Component location and instantiation </li></ul></ul></ul><ul><ul><ul><li>Component inspection </li></ul></ul></ul><ul><ul><ul><li>Data type mapping </li></ul></ul></ul><ul><ul><ul><li>Component invocation </li></ul></ul></ul>
  24. 24. Presentation Integration Framework <ul><li>Runtime Middleware </li></ul><ul><ul><li>Component Adapter </li></ul></ul>
  25. 25. Presentation Integration Framework <ul><li>Example </li></ul>National park guide
  26. 26. Presentation Integration Framework <ul><li>Example </li></ul>Component Model Descriptors
  27. 27. Presentation Integration Framework <ul><li>Example </li></ul>Composition Model Description
  28. 28. Presentation Integration Framework <ul><li>Example </li></ul>Middleware- Event automation
  29. 29. Implementation <ul><li>Middleware and Deployment </li></ul><ul><ul><li>Implemented by ASP.NET </li></ul></ul><ul><ul><li>Input: one or more XPIL documents Output: a complete HTML page </li></ul></ul><ul><li>Component Adapter </li></ul><ul><ul><li>They have implemented </li></ul></ul><ul><ul><ul><li>.NET adapter for Flickr.NET </li></ul></ul></ul><ul><ul><ul><li>SACK adapter for AJAX components built with the SACK toolkit. </li></ul></ul></ul><ul><ul><ul><li>A wrapper for Google Maps </li></ul></ul></ul><ul><ul><ul><ul><li>Reason1: Google Map is popular, and to expose many of its services should justify the investment. </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Reason2: Google Maps API doesn’t support point of interest or address directly. </li></ul></ul></ul></ul>
  30. 30. Conclusion <ul><li>They proposed a presentation integration framework to facilitate the creation of composite applications through a simple declarative composition language, XPIL. </li></ul><ul><li>The future works: </li></ul><ul><ul><li>Layout mechanism </li></ul></ul><ul><ul><li>To build more component adapters for AJAX-based toolkits, such as Yahoo UI and Dojo. </li></ul></ul><ul><ul><li>To create a visual authoring tool that allows the composition model to be specified in a drag-n-drop fashion with the final output generated in XPIL. </li></ul></ul>