AINA2010

377 views
334 views

Published on

Published in: Technology, Design
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
377
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

AINA2010

  1. 1. Mashup Patterns from Service Component Taxonomy Michele Stecca, CIPI – University of Padova and Genova (Italy) April 23rd, 2010 Perth Yes, from Europe! Yes, from Europe! Yes, from Europe! Yes, from Europe! Yes, from Europe! Yes, from Europe!
  2. 2. Outline <ul><li>Introduction </li></ul><ul><li>The Mashup Reference Model </li></ul><ul><li>Taxonomy of Service Components </li></ul><ul><li>Mashup Patterns </li></ul><ul><li>Conclusions </li></ul>
  3. 3. Introduction <ul><li>Scenario </li></ul><ul><li>High availability of contents and services through technologies typical of the Web 2.0 philosophy such as RSS Feed, Atom, REST-WS, SOAP-WS, etc. </li></ul><ul><li>Availability of tools for the rapid development of convergent Mashups (a.k.a. Composite Services) that combine different resources such as Yahoo Pipes!, JackBe Presto, etc. </li></ul><ul><li>Some APIs and Mashups repositories (e.g., programmableweb.com) exist but… </li></ul><ul><ul><li> It is still missing a classification of the both! </li></ul></ul>
  4. 4. The Reference Model <ul><li>A model for Event Driven Mashup creation and execution </li></ul><ul><li>Remarks </li></ul><ul><ul><li>Server Side execution model (long running Mashups) </li></ul></ul><ul><ul><li>Event driven model to cope with telco services (calls, SMS, etc.) </li></ul></ul><ul><li>The Service Creation Platform has been developed within the OPUCE FP 6 project (www.opuce.eu) </li></ul>
  5. 5. Taxonomy of Service Components (1/9) <ul><li>A. Monitor Service Component </li></ul><ul><li>It monitors a specific resource looking for new items that match a set of filters specified through the SC input properties. </li></ul><ul><li>Keyword in item title </li></ul><ul><li>Author name </li></ul><ul><li>… </li></ul>Item publication RSS Feed <ul><li>Keyword in e-mail subject </li></ul><ul><li>Keyword in e-mail content </li></ul><ul><li>… </li></ul>E-mail Inbox Gmail Monitor Examples of filters Monitored resource Service
  6. 6. Taxonomy of Service Components (2/9) <ul><li>A.1 Information Provider Monitoring </li></ul><ul><li>Monitoring the evolution of the contents provided over the network by a variety of sources. For example: </li></ul><ul><ul><li>The USA Government Web Site provides RSS feeds in the areas of Business & Economics (e.g., Federal Reserve news), Health (e.g., Pandemic Flu news), Public Safety and Laws (e.g., FBI news), Defense (e.g. Army news), etc. </li></ul></ul><ul><ul><li>The California State Web Site provides RSS feeds concerned with the Department of Justice, with the California Seismic Safety Commission, etc. </li></ul></ul>“ Title contains…” “ Author is…” RSS Feed Item RSS Feed Monitor RSS Feed Filters Example Item Resource Svc
  7. 7. Taxonomy of Service Components (3/9) <ul><li>A.2 Message Monitoring </li></ul><ul><li>Monitoring the incoming messages of a generic inbox. Different messaging technologies can be supported (e.g., SMS, MMS, e-mail, etc.). </li></ul>“ Sender number equals…” “ Content contains…” SMS message SMS Inbox Monitor SMS “ Object field contains…” “ Body field does not contain…” E-Mail Gmail Inbox Monitor Gmail Filters Example Item Resource Svc
  8. 8. Taxonomy of Service Components (4/9) <ul><li>A.3 Scheduled Event Monitoring </li></ul><ul><li>Monitoring events like deadlines, appointments, anniversaries, etc. The technologies through which these SCs are provided may be different (e.g., Google Calendar, internal companies/public institutes systems, etc.) depending on the specific application. </li></ul>“ Deadline date equals…” Database Entry Government Database Monitor Tax Payments Deadline “ Event date equals…” “ Event name contains…” Calendar Event Calendar Monitor Google Calendar Filters Example Item Resource Svc
  9. 9. Taxonomy of Service Components (5/9) <ul><li>A.4 Presence Monitoring </li></ul><ul><li>Monitoring the Presence status of a user. The technologies through which these SCs are provided may be different depending on the specific application. </li></ul>“ Presence equals…” “ Presence contains…” Presence User Presence GTalk Presence System Filters Example Item Resource Svc
  10. 10. Taxonomy of Service Components (6/9) <ul><li>A.5 Localization Monitoring </li></ul><ul><li>Monitoring the geographic coordinates of a user. They typically rely on the GPS system installed on many smartphones or available through some Internet services such as Yahoo Fire Eagle or on Telecom Operator Services (see for example Vodafone 360). </li></ul>“ User is close to…” User Localization User Localization Yahoo Fire Eagle Filters Example Item Resource Svc
  11. 11. Taxonomy of Service Components (7/9) <ul><li>B. Notification Component </li></ul><ul><li>It allows users to send contents to other people by means of different technologies </li></ul><ul><li>Personal Communication Notification SC (e.g., “Send SMS”, “Send Instant Message”, “Send Mail”, “Send MMS”, “Make phone call”, “Text to Speech Call”); </li></ul><ul><li>Social Network Notification SCs (e.g., Facebook, Twitter); </li></ul><ul><li>Calendar Event Notification SCs (e.g., Google Calendar); </li></ul><ul><li>Presence Notification SCs (e.g., GTalk); </li></ul><ul><li>… </li></ul>
  12. 12. Taxonomy of Service Components (8/9) <ul><li>C. Data Connector Component </li></ul><ul><li>It is a wrapper that accesses a content source, extracts a content, converts it appropriately and fills out the Svc output properties. </li></ul><ul><li>Database Data Connector SCs (e.g., MySQL Connector, MS Access Connector); </li></ul><ul><li>SpreadSheet Data Connector SCs (e.g., MS Excel Connector, Open Office SpreadSheet Connector); </li></ul><ul><li>XML Data Connector SCs; </li></ul><ul><li>… </li></ul>
  13. 13. Taxonomy of Service Components (9/9) <ul><li>D. General purpose Component </li></ul><ul><li>General Functionalities like filtering, merging, etc. </li></ul><ul><li>E. Map Component* </li></ul><ul><li>It takes the longitude and the latitude of a set of points as an input and displays them on a Map through a marker. Google Map is most famous example of such Service Component. </li></ul>
  14. 14. Mashups application environments <ul><li>Here is a list of fields where Mashups can be successfully used: </li></ul><ul><li>e-Government </li></ul><ul><li>e-Health </li></ul><ul><li>Finance </li></ul><ul><li>Enterprise (Situational Mashups) </li></ul><ul><li>Social Networks </li></ul><ul><li>Entertainment </li></ul><ul><li>… </li></ul>
  15. 15. Mashup patterns and examples (1/4) <ul><ul><li>1. Resource Monitoring and Notification </li></ul></ul><ul><ul><ul><li>1.1 Reminder Mashup (Book Lending Deadline reminder, Appointment reminder, etc.) </li></ul></ul></ul><ul><ul><ul><li>1.2 Alert Mashup (Public Transportation Delay Alert , Traffic Jam Alert, etc. ) </li></ul></ul></ul><ul><ul><ul><li>1.3 “Automatic notification of interesting events” Mashup (U2 Concert publication by Facebook Friend , etc. ) </li></ul></ul></ul>
  16. 16. <ul><li>2. Resource Monitoring, Processing and Notification </li></ul><ul><ul><li>2.1 Time dependent notification </li></ul></ul><ul><ul><li>2.2 Localization dependent notification </li></ul></ul><ul><ul><li>2.3 Presence dependent notification </li></ul></ul><ul><ul><li>2.4 Time + Localization dependent notification (e.g. Non-repudiation Mashup) </li></ul></ul>Mashup patterns and examples (2/4)
  17. 17. <ul><li>3. Resource Monitoring, Processing and Map Visualization </li></ul><ul><li>E.g. Whenever a new traffic situation appears near the user, the Mashup visualizes the position of the traffic jam (Monitor Yahoo Traffic Svc + Location Svc + Conditional Svc + Google Maps Svc) on Google Map; </li></ul>Mashup patterns and examples (3/4)
  18. 18. <ul><li>4. Data Aggregator </li></ul><ul><li>5. Typical Web Mashup synchronous execution </li></ul>Mashup patterns and examples (4/4)
  19. 19. Conclusions <ul><li>We proposed a model for the definition and execution of Mashups </li></ul><ul><li>The main contribution of this paper is twofold: </li></ul><ul><ul><li>Definition of a taxonomy of the “mashable” services </li></ul></ul><ul><ul><li>Identification and Description of Mashup Patterns </li></ul></ul><ul><li>Next Step  Improvement of the classification taking into account community’s feedbacks </li></ul>
  20. 20. <ul><li>Thank you for your attention… </li></ul><ul><li>Q & A?? </li></ul>

×