Your SlideShare is downloading. ×
Elucidating the Mashup Hype: Definition, Challenges, Methodical Guide and Tools for Mashups
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Elucidating the Mashup Hype: Definition, Challenges, Methodical Guide and Tools for Mashups


Published on

Paper presented at 2nd Workshop on Mashups, Enterprise Mashups and Lightweight Composition on the Web (MEM 2009 @ WWW 2009; …

Paper presented at 2nd Workshop on Mashups, Enterprise Mashups and Lightweight Composition on the Web (MEM 2009 @ WWW 2009;

Mashups are a current hype that is attracting high interest by academia and industry now and in the next years. The idea behind a mashup is to create new content by reusing and combining existing content from heterogeneous sources. Advantages of mashups are that even people with no knowledge of programming languages can easily build new Web applications and create new forms of visualizations. To support the mashup construction process several tools have been proposed with easy-to-use functionalities. However, from the research perspective it is dissatisfying that neither a clear definition and classification model for mashups nor a separation between mashups and other forms of application integrations exist. The aim of this paper is to elucidate the mashup hype by providing a definition and classification model for mashups and to sketch a methodical engineering guide for mashups. Additionally, an overview of tools and languages supporting the mashup creation is presented.

Published in: Technology
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. Elucidating the Mashup Hype: Definition, Challenges, Methodical Guide and Tools for Mashups Agnes Koschmider, Victoria Torres and Vicente Pelechano
  • 2.
    • Introduction
    • Definition for Mashups
    • Links and Differences
    • Classification of Mashups
    • Challenges for the Mashup Construction
    • Guide for a Methodical Construction of Mashups
    • Tools
    • Conclusions
  • 3.
    • The Mashup term
      • roots in the musical domain
      • generalized and brought to other domains
    • Focusing on the Web domain
      • No clear distinction between SOA vs. Mashup
      • No clear classification model
      • Which challenges introduce
      • Methodology for Mashup construction
  • 4. Introduction
  • 5. Definition for Mashups Web page integration combination reuse Data sources APIs Third party data Web 2.0 Data processing
  • 6. Definition for Mashups Web-based application that is created by combining and processing on-line third party resources, resources that contribute with data, presentation or functionality
  • 7.
    • SOA principles
      • Autonomy
      • Composability
      • Contract
      • Discoverability
      • Encapsulation
      • Loose coupling
      • Reusability
      • Statelessness
    Links and Differences
  • 8.
    • Differences
      • No formal definition of the combined resources is required
      • Integration is performed at UI level not at logic level
      • Targeted to non-expert users
      • Resources not always provided to be exploited by third-parties
      • There is no a communication protocol
    Links and Differences
  • 9.
    • WHAT to mash up?
    • WHERE to mash up?
    • HOW to mash up?
    • F or WHOM to mash up?
    Classification of Mashups
  • 10.
    • WHAT to mash up?
      • Presentation
        • Retrieves layout information from different data sources
      • Data
        • Merges data from different sources
      • Application functionality
        • Builds a new resource based on the composition of functionality
      • Other classifications based on the content
        • Mapping, Photo/Video, Search/Shopping, News, etc.
    Classification of Mashups
  • 11.
    • WHERE to mash up?
      • Server
        • Logic hosted in the Server
        • Languages: Python, CGI, PHP, etc.
        • Content is generated similarly to traditional Web apps
        • Allows transforming returned data into a different formats
      • Client
        • Logic hosted in the Client
        • Languages: Javascript, AJAX, Java applet
        • Data directly retrieved from provider
        • Better user experience
    Classification of Mashups
  • 12.
    • H OW to mash up?
      • Extraction
        • Collect + Merge
      • Flow
        • Collect + Transform/Process + Merge
    Classification of Mashups
  • 13.
    • For WHOM to mash up?
      • Consumer mashups
        • Intended for individual use
        • Combine public + private sources
        • By means of a simple browser-based UI
      • Enterprise/Business mashups
        • Intended for organization members use
        • Considers: Security + Governance/Enterprise policies
        • Intended for domain experts
    Classification of Mashups
  • 14.
    • Cataloguing
      • Available directories
        • Tool directories (Yahoo! Pipes, google Mashups, etc.)
      • It is necessary:
        • Establish a standardized catalogue facilitating efficient searches
    Challenges for the Mashup Construction
  • 15.
    • Data integrity
      • In Web 2.0 users are Contributors and Creators
        • Inconsistency
        • Incorrectness
        • Intentionally misleading data entry
      • Control mechanisms against end-user changes
    Challenges for the Mashup Construction
  • 16.
    • Making data Web-enabled
      • Improve screen scraping techniques
        • No contract between content provider and consumer
        • Highly dependent on the source presentation
      • Evaluate the impact of hosting the logic in the client
        • Browsers with JavaScript disabled
        • Web robots, spiders or Webcrawlers
      • Avoid Denial of Service (DoS) Attacks
    Challenges for the Mashup Construction
  • 17.
    • Security and Identity
      • Protection of data in transit
        • i.e. MashSSL (SSL protocol)
      • Control access
      • Client-side
        • Allows avoiding Same-Origin Policy
      • Server-side
        • Application ID is not passed to each client’s browser
    Challenges for the Mashup Construction
  • 18.
    • Sharing and reusing
      • Mechanisms for sharing mashups
        • What to share: public vs. Private data
        • How to share:
          • Access policies
          • Mechanisms to set the context of use (permision)
        • Who to share with: groups, individuals, etc.
    Challenges for the Mashup Construction
  • 19.
    • Trust certificates
      • Mainly for Enterprise/Business Mashups
      • Can I trust the source?
        • Threats due to the mashup dynamic and multidomain nature
        • Protect end-users
      • Someone should issue a license certifying the mashup
    Challenges for the Mashup Construction
  • 20.
    • Version control mechanisms
      • Mashups rely on third-party resources
      • Is the partner getting the proper data?
      • Content providers should notify about changes
    Challenges for the Mashup Construction
  • 21.
    • Things to consider
      • Resources exist before the Mashup application
      • Resources are given in a specific technology
      • End-users get involved in the Mashup life-cycle
      • Model Driven Development (MDD)
        • H as proven satisfactory in Software Development
        • Follows a Top-down strategy
        • Can help to define “generic” mashups
    Guide for a Methodological Construction of Mashups
  • 22.
    • State the problem domain
      • Business objective and success factors
    • Identify the IT environment
      • A vailable resources in the domain
    • Identify the technical requirements
      • Catalogue interfaces, define new services, processes, …
    • Identify the technology set
      • Select technology to deploy, test and evaluate
    • Mashup Maintenance
      • Version control, data integrity
    Guide for a Methodological Construction of Mashups
  • 23.
    • Building, storing and publishing functionalities
    • Conceived as Web 2.0 applications
    • Targeted to both experts and non-expert users
    • Open source to highly-cost licence tools
  • 24.
    • Dapper = Data + mapper
      • Presentation, extraction and consumer Mashup tool
    • DERI pipes
      • Data, flow and consumer Mashup tool
      • Inspired by Yahoo! Pipes
      • It allows handling RDF documents  semantics
      • Does not require programming language skills
  • 25.
    • Serena Mashup Composer
      • Data, functionality, flow and enterprise Mashup tool
      • Information + Business processes + Data
      • Syntax for Mashup creation similar to BPEL
        • But allows consuming any kind of resource (feeds, plain HTML, services)
    • Microsoft Popfly
      • Presentation, data, flow and consumer Mashup tool
      • Does not require language programming skills
  • 26.
    • Mashup technology allows end-users define applications based on their own needs
    • It is necessary to provide methods for the construction of Mashups
    • Before enterprise adoption
      • Is required more research in
        • Control Mechanisms
        • Mashup Certification
        • Mashup Quality
        • Data Intergrity