Building Mashups by example

Abstract

Creating a Mashup, a web application that integrates data from multiple web sources to provide a unique service, involves solving multiple problems, such as extracting data from multiple web sources, cleaning it, and combining it together. Existing work relies on a widget paradigm where users address those problems during a Mashup building process by selecting, customizing, and connecting widgets together. While these systems claim that their users do not have to write a single line of code, merely abstracting programming methods into widgets has several disadvantages. First, as the number of widgets increases to support more operations, locating the right widget for the task can be confusing and time consuming. Second, customizing and connecting these widgets usually requires users to understand programming concepts. In this paper, we present a Mashup building approach that (a) combines most problem areas in Mashup building into a unified interactive framework that requires no widgets, and (b) allows users with no programming background to easily create Mashups by example.

Assistive Tools towards Personal Learning Environment in Higher Education

“…Based on that combination, few mashup approaches have been identified and discussed to facilitate mashup development. This includes widget-based [9], spreadsheet-like [11], wired-based [5], programming by example and demonstration [12], [13] and block-based development [14]. These approaches play an important role as a user interface component at the presentation level.…”

Mixer: Mixed-Initiative Data Retrieval and Integration by Example

“…Vegemite [22] asks the user to create a set of "VegeTables," each of which corresponds to a script for combining two websites. Karma [36], Dontcheva et al [11] and Mashroom [38] build separate tables for each extracted website; additionally, Mashroom explicitly uses nested tables (specifically with an eye towards comprehensibility by end users). Each of these systems asks the user to explicitly "merge" extractions from different websites into a coherent table.…”

Automatic Mash Up of Composite Applications

“…With this annotation, we are describing the message in terms of an OWL class in an existing ontological model. This message is set as an output of the "pubCityState" operation in a portType (lines [18][19][20][21][22] and included in a portlet type binding (lines [23][24][25][26][27][28][29][30][31][32][33][34][35]. The "pubCityState" operation corresponds to broadcasting the city and state information to PropertyBroker.…”

“…As a number of research works suggest [32], [28], [33], [34], most tools provide limited search and discovery for mashup components. Users still need to know how to write code (e.g., JavaScript or XML/HTML) and link the components using technical concepts derived from programming.…”

“…Karma [33] and UQBE [40] take a mashup as a schema matching or data integration problem. In this environment, disparate data sources are "joined" by common attributes as if joining relational tables.…”