Proceedings of the 13th International Conference on Information Integration and Web-Based Applications and Services 2011
DOI: 10.1145/2095536.2095591
|View full text |Cite
|
Sign up to set email alerts
|

The mashup component description language

Abstract: Mashups can be seen as the result of software composition applied to the Web. One of the characteristics of mashup development is the heterogeneity of its building components in terms of logical layering (e.g., user interface, application logic, and data), access method (e.g., REST, SOAP), and composition technique (e.g., scraping vs. clipping, synchronous vs. asynchronous interaction, discrete vs. streaming). This poses a challenge towards the design of mashup tools aiming at lowering the barriers of mashup d… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
4
0

Year Published

2012
2012
2015
2015

Publication Types

Select...
3
2
1

Relationship

2
4

Authors

Journals

citations
Cited by 6 publications
(4 citation statements)
references
References 15 publications
0
4
0
Order By: Relevance
“…Therefore, the focus on data mashups only is too narrow and the language has already grown very complex (without concrete vendor adoption). Aghaee and Pautasso [2011], on the other hand, focus on the design of a generic mashup component description language and do not elaborate on their composition into mashups. Their model contains technology aspects (e.g., component wrappers), that we think are instead a runtime aspect that should not affect the component description.…”
Section: Related Workmentioning
confidence: 99%
“…Therefore, the focus on data mashups only is too narrow and the language has already grown very complex (without concrete vendor adoption). Aghaee and Pautasso [2011], on the other hand, focus on the design of a generic mashup component description language and do not elaborate on their composition into mashups. Their model contains technology aspects (e.g., component wrappers), that we think are instead a runtime aspect that should not affect the component description.…”
Section: Related Workmentioning
confidence: 99%
“…Mashups can be seen as the result of applying software composition techniques to the development of web applications [1]. Much effort is being spent nowadays to propose models enabling rich integration of the different component functionalities.…”
Section: Related Workmentioning
confidence: 99%
“…For example, Listing 1 conforms to the NaturalMash CNL and describes an enhanced music video search mashup that employs Last.fm (http://www.last.fm/api) to first search for a song and then uses the results to accurately search for the corresponding music videos of the song in YouTube (https://developers.google.com/youtube/). The underlying implementation of the CNL accommodates an abstract component model [22] that: (i) gives a unified technology-neutral description of Web APIs, and (ii) models them in an abstract textual form (natural language description). The abstract component model distinguishes two types of functionality provided by Web APIs, namely, Task -a passive atomic operation, and Event -an active source of control.…”
Section: Naturalmash Controlled Natural Languagementioning
confidence: 99%