You do not have permission to edit this page, for the following reasons:

This IP address has been blocked from editing Wikipedia.
This does not affect your ability to read Wikipedia pages.
Most people who see this message have done nothing wrong. Some kinds of blocks restrict editing from specific service providers or telecom companies in response to recent abuse or vandalism, and can sometimes affect other users who are unrelated to that abuse. Review the information below for assistance if you do not believe that you have done anything wrong.

The IP address or range 54.92.0.0/16 has been blocked by ‪Blablubbs‬ for the following reason(s):

The IP address that you are currently using has been blocked because it is believed to be a web host provider or colocation provider. To prevent abuse, web hosts and colocation providers may be blocked from editing Wikipedia.
You will not be able to edit Wikipedia using a web host or colocation provider because it hides your IP address, much like a proxy or VPN.
We recommend that you attempt to use another connection to edit. For example, if you use a proxy or VPN to connect to the internet, turn it off when editing Wikipedia. If you edit using a mobile connection, try using a Wi-Fi connection, and vice versa. If you are using a corporate internet connection, switch to a different Wi-Fi network. If you have a Wikipedia account, please log in.
If you do not have any other way to edit Wikipedia, you will need to request an IP block exemption.

How to appeal if you are confident that your connection does not use a colocation provider's IP address:
If you are confident that you are not using a web host, you may appeal this block by adding the following text on your talk page: ((unblock|reason=Caught by a colocation web host block but this host or IP is not a web host. My IP address is _______. Place any further information here. ~~~~)). You must fill in the blank with your IP address for this block to be investigated. Your IP address can be determined here. Alternatively, if you wish to keep your IP address private you can use the unblock ticket request system. There are several reasons you might be editing using the IP address of a web host or colocation provider (such as if you are using VPN software or a business network); please use this method of appeal only if you think your IP address is in fact not a web host or colocation provider.

Administrators: The IP block exemption user right should only be applied to allow users to edit using web host in exceptional circumstances, and requests should usually be directed to the functionaries team via email. If you intend to give the IPBE user right, a CheckUser needs to take a look at the account. This can be requested most easily at SPI Quick Checkuser Requests. Unblocking an IP or IP range with this template is highly discouraged without at least contacting the blocking administrator.

This block will expire on 10:02, 6 June 2025. Your current IP address is 54.92.174.87.

Even when blocked, you will usually still be able to edit your user talk page, as well as email administrators and other editors.

For information on how to proceed, please read the FAQ for blocked users and the guideline on block appeals. The guide to appealing blocks may also be helpful.

Other useful links: Blocking policy · Help:I have been blocked
This IP address range has been globally blocked.
This does not affect your ability to read Wikipedia pages.
Most people who see this message have done nothing wrong. Some kinds of blocks restrict editing from specific service providers or telecom companies in response to recent abuse or vandalism, and can sometimes affect other users who are unrelated to that abuse. Review the information below for assistance if you do not believe that you have done anything wrong.

This block affects editing on all Wikimedia wikis.
The IP address or range 54.92.0.0/16 has been globally blocked by ‪Jon Kolbert‬ for the following reason(s):

Open proxy/Webhost: See the help page if you are affected

This block will expire on 18:27, 12 November 2028. Your current IP address is 54.92.174.87.

Even while globally blocked, you will usually still be able to edit pages on Meta-Wiki.

If you believe you were blocked by mistake, you can find additional information and instructions in the No open proxies global policy. Otherwise, to discuss the block please post a request for review on Meta-Wiki. You could also send an email to the stewards VRT queue at stewards@wikimedia.org including all above details.

Other useful links: Global blocks · Help:I have been blocked

You can view and copy the source of this page:

((Short description|Web application that combines content from more than one source in a single graphical interface))
((Other uses|Mashup (disambiguation)))
((more citations needed|date=January 2013))
A '''mashup''' (computer industry [[jargon]]), in [[web development]], is a [[web page]] or [[web application]] that uses content from more than one source to create a single new service displayed in a single graphical interface. For example, a user could combine the addresses and photographs of their library branches with a [[Google map]] to create a map mashup.<ref>((cite book|last=Fichter |first=Darlene |title=What Is a Mashup? |url=http://books.infotoday.com/books/Engard/Engard-Sample-Chapter.pdf |accessdate=12 August 2013))</ref> The term implies easy, fast integration, frequently using open application programming interfaces ([[open API]]) and data sources to produce enriched results that were not necessarily the original reason for producing the raw source data.
The term mashup originally comes from creating something by combining elements from two or more sources.<ref>((cite web |title=mash-up |url=https://www.merriam-webster.com/dictionary/mash-up#h1 |website=merriam-webster.com |date=31 May 2024 |ref=mwmashup))</ref>

The main characteristics of a mashup are combination, visualization, and aggregation. It is important to make existing data more useful, for personal and professional use. To be able to permanently access the data of other services, mashups are generally [[Client (computing)|client applications]] or hosted online.

In the past years((when|date=December 2018)), more and more Web applications have published APIs that enable software developers to easily integrate data and functions the [[Service-oriented architecture|SOA]] way, instead of building them by themselves. Mashups can be considered to have an active role in the evolution of [[social software]] and [[Web 2.0]]. Mashup composition tools are usually simple enough to be used by end-users. They generally do not require programming skills and rather support visual wiring of [[GUI widget]]s, services and components together. Therefore, these tools contribute to a new vision of the [[World Wide Web|Web]], where users are able to contribute.((clarify|reason=User contributions were part of the original vision of the WWW, right?|date=January 2014))

The term "mashup" is not formally defined by any standard-setting body.<ref>((cite web
| access-date = 2010-03-03
| title = Enterprise Mashups: The New Face of Your SOA
| publisher = SOA WORLD MAGAZINE
| url = http://soa.sys-con.com/node/719917
| quote = The term mashup isn't subject to formal definition by any standards-setting body.
| archive-date = 2009-06-05
| archive-url = https://web.archive.org/web/20090605144831/http://soa.sys-con.com/node/719917
| url-status = dead
))</ref>

==History==
The broader context of the history of the Web provides a background for the development of mashups. Under the [[Web 1.0]] model, organizations stored consumer data on [[Web portal|portals]] and updated them regularly. They controlled all the consumer data, and the consumer had to use their products and services to get the information.((citation needed|date=January 2018))

The advent of [[Web 2.0]] introduced Web standards that were commonly and widely adopted across traditional competitors and which unlocked the consumer data. At the same time, mashups emerged, allowing mixing and matching competitors' APIs to develop new services.

The first mashups used mapping services or photo services to combine these services with data of any kind and therefore to produce visualizations of data.<ref name="holmes">
((cite web | url= http://msdn.microsoft.com/en-us/architecture/bb906060.aspx| last1= Clarkin | first1= Larry | last2= Holmes | first2= Josh | title= Enterprise Mashups | work= MSDN Architecture Journal | date= 14 January 2009 | publisher= MSDN Architecture Center))
</ref>((failed verification|date=January 2018))
In the beginning, most mashups were consumer-based, but recently((when|date=January 2018)) the mashup is to be seen((by whom|date=January 2018)) as an interesting concept useful also to enterprises. Business mashups can combine existing internal data with external services to generate new views on the data.
There was also the free [[Yahoo! Pipes]] to build mashups for free using the [[Yahoo! Query Language]].

==Types of mashup==
There are many types of mashup, such as business mashups, consumer mashups, and data mashups.<ref>((cite web | url = http://www.mphasis.com/pdfs/Mashups_and_the_Enterprise.pdf | author = Sunilkumar Peenikal | year = 2009 | title = Mashups and the enterprise | publisher = MphasiS - HP | access-date = 2010-02-27 | archive-url = https://web.archive.org/web/20130602215542/http://www.mphasis.com/pdfs/Mashups_and_the_Enterprise.pdf | archive-date = 2013-06-02 | url-status = dead ))</ref> The most common type of mashup is the consumer mashup, aimed at the general public.
* ''Business'' (or ''enterprise'') ''mashups'' define applications that combine their own resources, application and data, with other external [[Web service]]s.<ref name="holmes" /> They focus data into a single presentation and allow for collaborative action among businesses and developers. This works well for an [[Agile software development|agile development]] project, which requires collaboration between the developers and customer (or customer proxy, typically a product manager) for defining and implementing the business requirements. Enterprise mashups are secure, visually rich Web applications that expose actionable information from diverse internal and external information sources.
* ''Consumer mashups'' combine data from multiple public sources in the browser and organize it through a simple browser user interface.<ref>((cite web
| access-date = 2010-03-03
| title = Enterprise Mashups: The New Face of Your SOA
| publisher = SOA WORLD MAGAZINE
| url = http://soa.sys-con.com/node/719917
| quote = A consumer mashup is an application that combines data from multiple public sources in the browser and organizes it through a simple browser user interface.
| archive-date = 2009-06-05
| archive-url = https://web.archive.org/web/20090605144831/http://soa.sys-con.com/node/719917
| url-status = dead
))</ref> ''(e.g.: [[Wikipediavision]] combines Google Map and a Wikipedia API)''
* ''Data mashups'', opposite to the consumer mashups, combine similar types of media and information from multiple sources into a single representation. The combination of all these resources create a new and distinct [[Web API|Web service]] that was not originally provided by either source.

===By API type===
Mashups can also be categorized by the basic API type they use but any of these can be combined with each other or embedded into other applications.
<!-- Please re-order this section, one of it's purposes is to avoid direct examples that could be considered as spam-->

====Data types====
* [[Index (search engine)|Indexed data]] (documents, weblogs, images, videos, shopping articles, jobs ...) used by [[metasearch engines]]
* Cartographic and geographic data:  [[geolocation software]], [[geovisualization]]
* Feeds, podcasts: [[news aggregator]]s

====Functions====
* Data converters: [[Translation|language translators]], [[speech processing]], [[URL shortening|URL shorteners]]...
* Communication: [[email]], [[instant messaging]], [[notification system|notification]]...
* Visual data rendering: [[Information visualization#Applications|information visualization]], diagrams
* Security related: [[Electronic money|electronic payment systems]], [[Digital identity|ID identification]]...
* [[Editing|Editors]]

== Mashup enabler ==
In technology, a '''mashup enabler''' is a tool for transforming incompatible IT resources into a form that allows them to be easily combined, in order to create a mashup. Mashup enablers allow powerful techniques and tools (such as mashup platforms) for combining data and services to be applied to new kinds of resources. An example of a mashup enabler is a tool for creating an [[RSS]] feed from a spreadsheet (which cannot easily be used to create a mashup). Many mashup editors include mashup enablers, for example, Presto Mashup Connectors, Convertigo Web Integrator or [[Caspio#Caspio Bridge|Caspio Bridge]].

Mashup enablers have also been described as "the service and tool providers, [sic] that make mashups possible".((citation needed|date=November 2013))

=== History ===
Early mashups were developed manually by enthusiastic programmers. However, as mashups became more popular, companies began creating platforms for building mashups, which allow designers to visually construct mashups by connecting together mashup components.

Mashup editors have greatly simplified the creation of mashups, significantly increasing the productivity of mashup developers and even opening mashup development to end-users and non-IT experts. Standard components and connectors enable designers to combine mashup resources in all sorts of complex ways with ease. Mashup platforms, however, have done little to broaden the scope of resources accessible by mashups and have not freed mashups from their reliance on well-structured data and open libraries ([[RSS]] feeds and public [[API]]s).

Mashup enablers evolved to address this problem, providing the ability to convert other kinds of data and services into mashable resources.

=== Web resources ===
Of course, not all valuable data is located within organizations. In fact, the most valuable information for business intelligence and decision support is often external to the organization. With the emergence of [[rich web applications]] and online Web portals, a wide range of business-critical processes (such as ordering) are becoming available online. Unfortunately, very few of these data sources syndicate content in RSS format and very few of these services provide publicly accessible APIs. Mashup editors therefore solve this problem by providing enablers or connectors.

==Mashups versus portals==
Mashups and [[Web portal|portals]] are both [[Aggregate data|content aggregation]] technologies. Portals are an older technology designed as an extension to traditional [[Dynamic Web page|dynamic Web application]]s, in which the process of converting data content into marked-up Web pages is split into two phases: generation of markup "fragments" and aggregation of the fragments into pages. Each markup fragment is generated by a "[[portlet]]", and the portal combines them into a single Web page. Portlets may be hosted locally on the portal server or remotely on a separate server.

Portal technology defines a complete event model covering reads and updates. A request for an aggregate page on a portal is translated into individual read operations on all the portlets that form the page ("<code>render</code>" operations on local, [[JSR 168]] portlets or "<code>getMarkup</code>" operations on remote, [[Web Services for Remote Portlets|WSRP]] portlets). If a submit button is pressed on any portlet on a portal page, it is translated into an update operation on that portlet alone (<code>processAction</code> on a local portlet or <code>performBlockingInteraction</code> on a remote, WSRP portlet). The update is then immediately followed by a read on ''all'' portlets on the page.

Portal technology is about server-side, [[Multitier architecture|presentation-tier]] aggregation. It cannot be used to drive more robust forms of application integration such as [[Two-phase commit protocol|two-phase commit]].

Mashups differ from portals in the following respects:

{| class="wikitable"
|-
! !!Portal!!Mashup
|-
!Classification
|Older technology, extension of traditional Web server model using well-defined approach
|Uses newer, loosely defined "Web 2.0" techniques
|-
!Philosophy/approach
|Approaches aggregation by splitting role of Web server into two phases: markup generation and aggregation of markup fragments
|Uses APIs provided by different content sites to aggregate and reuse the content in another way
|-
!Content dependencies
|Aggregates presentation-oriented markup fragments (HTML, WML, VoiceXML, etc.)
|Can operate on pure XML content and also on presentation-oriented content (e.g., HTML)
|-
!Location dependencies
|Traditionally, content aggregation takes place on the server
|Content aggregation can take place either on the server or on the client
|-
!Aggregation style
|"[[Salad bar]]" style: Aggregated content is presented 'side-by-side' without overlaps
|"[[Melting pot]]" style - Individual content may be combined in any manner, resulting in arbitrarily structured hybrid content
|-
!Event model
|Read and update event models are defined through a specific portlet API
|[[Create, read, update and delete|CRUD]] operations are based on [[Representational State Transfer|REST]] architectural principles, but no formal API exists
|-
!Relevant standards
|Portlet behavior is governed by standards [[JSR 168]], [[JSR 286]] and [[Web Services for Remote Portlets|WSRP]], although portal page layout and portal functionality are undefined and vendor-specific
|Base standards are XML interchanged as [[REST]] or Web Services. [[RSS]] and [[Atom (standard)|Atom]] are commonly used. More specific mashup standards such as [[EMML]] are emerging.
|}

The portal model has been around longer and has had greater investment and product research. Portal technology is therefore more standardized and mature. Over time, increasing maturity and standardization of mashup technology will likely make it more popular than portal technology because it is more closely associated with Web 2.0 and lately [[service-oriented architecture|Service-oriented Architectures]] (SOA).<ref>((cite web | last=Digna | first=Larry | year=2007 | url=http://blogs.zdnet.com/BTL/?p=4912 | title=Gartner: The future of portals is mashups, SOA, more aggregation | publisher=ZDNET | access-date=2009-12-26 | archive-date=2012-04-13 | archive-url=https://web.archive.org/web/20120413031348/http://www.zdnet.com/blog/btl/gartner-the-future-of-portals-is-mashups-soa-more-aggregation/4912 | url-status=dead ))</ref>  New versions of portal products are expected to eventually add mashup support while still supporting legacy portlet applications. Mashup technologies, in contrast, are not expected to provide support for portal standards.

==Business mashups==
Mashup uses are expanding in the business environment. Business mashups are useful for integrating business and data services, as business mashups technologies provide the ability to develop new integrated services quickly, to combine internal services with external or personalized information, and to make these services tangible to the business user through user-friendly Web browser interfaces.<ref>((cite web | url = http://www.ibm.com/developerworks/lotus/library/mashups-patterns-pt1/ | last=Holt | first=Adams | year=2009 | title = Executive IT Architect, Mashup business scenarios and patterns  | publisher=IBM DeveloperWorks))</ref>

Business mashups differ from consumer mashups in the level of integration with business computing environments, security and access control features, governance, and the sophistication of the programming tools (mashup editors) used.  Another difference between business mashups and consumer mashups is a growing trend of using business mashups in commercial [[software as a service]] (SaaS) offering.

Many of the providers of business mashups technologies have added [[service-oriented architecture|SOA]] features.

==Architectural aspects of mashups==
The architecture of a mashup is divided into three layers:
* Presentation / [[user interaction]]: this is the [[user interface]] of mashups. The technologies used are [[HTML]]/[[XHTML]], [[CSS]], [[JavaScript]], [[Ajax (programming)|Asynchronous JavaScript and Xml (Ajax)]].
* Web Services: the product's functionality can be accessed using API services. The technologies used are [[XMLHTTPRequest]], [[XML-RPC]], [[JSON-RPC]], [[SOAP]], [[REST]].
* Data: handling the data like sending, storing and receiving. The technologies used are [[XML]], [[JSON]], [[KML]].

Architecturally, there are two styles of mashups: Web-based and server-based. Whereas Web-based mashups typically use the user's [[web browser]] to combine and reformat the data, server-based mashups analyze and reformat the data on a remote [[server (computing)|server]] and transmit the data to the user's browser in its final form.<ref>((cite web| last=Bolim | first=Michael | year=2005 | pages=22–23 | url=http://bolinfest.com/Michael_Bolin_Thesis_Chickenfoot.pdf | title=End-User Programming for the Web, MIT MS thesis, 2.91 MB PDF ))</ref>

Mashups appear to be a variation of a [[façade pattern]].<ref>Design Patterns: Elements of Reusable Object-Oriented Software (((ISBN|0-201-63361-2))) by Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides</ref>  That is: a software engineering design pattern that provides a simplified interface to a larger body of code (in this case the code to aggregate the different feeds with different [[API]]s).

Mashups can be used with software provided as a service ([[software as a service|SaaS]]).

After several years of standards development, mainstream businesses are starting to adopt [[service-oriented architecture]]s (SOA) to integrate disparate data by making them available as discrete Web services.  Web services provide open, standardized [[protocol (computing)|protocol]]s to provide a unified means of accessing information from a diverse set of platforms ([[operating system]]s, [[programming language]]s, [[application software|applications]]). These Web services can be reused to provide completely new services and applications within and across organizations, providing business flexibility.

==See also==
* [[Mashup (culture)]]
* [[Mashup (music)]]
* [[Open Mashup Alliance]]
* [[Open API]]
* [[Yahoo! Pipes]]
* [[Webhook]]
* [[Web portal]]
* [[Web scraping]]

==References==
((Reflist))

==Further reading==
* Ahmet Soylu, Felix Mödritscher, Fridolin Wild, Patrick De Causmaecker, Piet Desmet. 2012 . [http://www.ahmetsoylu.com/wp-content/uploads/2013/10/soylu_Program2012.pdf “Mashups by Orchestration and Widget-based Personal Environments: Key Challenges, Solution Strategies, and an Application.”] Program: Electronic Library and Information Systems 46 (4): 383–428.
* Endres-Niggemeyer, Brigitte ed. 2013. Semantic Mashups. Intelligent Reuse of Web Resources. Springer. ((ISBN|978-3-642-36402-0)) (Print)

((Web syndication))
((Web interfaces))
((Intellectual_property_activism))
((Authority control))

((DEFAULTSORT:Mashup (Web Application Hybrid)))
[[Category:Mashup (web application hybrid)| ]]
[[Category:Software architecture]]
[[Category:Web 2.0]]
[[Category:Web 2.0 neologisms]]
[[Category:Web development]]

Pages transcluded onto the current version of this page (help):

Mashup (web application hybrid) (edit)
Template:Ambox (view source) (template editor protected)
Template:Authority control (view source) (template editor protected)
Template:By whom (view source) (template editor protected)
Template:Catalog lookup link (view source) (template editor protected)
Template:Category handler (view source) (protected)
Template:Citation needed (view source) (protected)
Template:Cite book (view source) (protected)
Template:Cite web (view source) (protected)
Template:Clarify (view source) (template editor protected)
Template:Delink (view source) (protected)
Template:Failed verification (view source) (template editor protected)
Template:Find sources mainspace (view source) (template editor protected)
Template:Fix (view source) (protected)
Template:Fix-span (view source) (template editor protected)
Template:Fix/category (view source) (protected)
Template:Hlist/styles.css (view source) (protected)
Template:ISBN (view source) (template editor protected)
Template:Intellectual property activism (edit)
Template:Main other (view source) (protected)
Template:More citations needed (view source) (template editor protected)
Template:Navbox (view source) (template editor protected)
Template:Other uses (view source) (template editor protected)
Template:Pagetype (view source) (protected)
Template:Reflist (view source) (protected)
Template:Reflist/styles.css (view source) (protected)
Template:SDcat (view source) (protected)
Template:Short description (view source) (protected)
Template:Short description/lowercasecheck (view source) (protected)
Template:Web interfaces (edit)
Template:Web syndication (edit)
Template:When (view source) (template editor protected)
Template:Yesno (view source) (protected)
Template:Yesno-no (view source) (template editor protected)
Template:Yesno-yes (view source) (template editor protected)
Module:Arguments (view source) (protected)
Module:Authority control (view source) (template editor protected)
Module:Authority control/config (view source) (template editor protected)
Module:Catalog lookup link (view source) (template editor protected)
Module:Category handler (view source) (protected)
Module:Category handler/blacklist (view source) (protected)
Module:Category handler/config (view source) (protected)
Module:Category handler/data (view source) (protected)
Module:Category handler/shared (view source) (protected)
Module:Check for unknown parameters (view source) (protected)
Module:Check isxn (view source) (template editor protected)
Module:Citation/CS1 (view source) (protected)
Module:Citation/CS1/COinS (view source) (protected)
Module:Citation/CS1/Configuration (view source) (protected)
Module:Citation/CS1/Date validation (view source) (protected)
Module:Citation/CS1/Identifiers (view source) (protected)
Module:Citation/CS1/Utilities (view source) (protected)
Module:Citation/CS1/Whitelist (view source) (protected)
Module:Citation/CS1/styles.css (view source) (protected)
Module:DecodeEncode (view source) (template editor protected)
Module:Delink (view source) (protected)
Module:Disambiguation/templates (view source) (protected)
Module:EditAtWikidata (view source) (protected)
Module:Find sources (view source) (template editor protected)
Module:Find sources/config (view source) (template editor protected)
Module:Find sources/links (view source) (template editor protected)
Module:Find sources/templates/Find sources mainspace (view source) (template editor protected)
Module:Format link (view source) (template editor protected)
Module:Hatnote (view source) (template editor protected)
Module:Hatnote/styles.css (view source) (template editor protected)
Module:Hatnote list (view source) (template editor protected)
Module:Message box (view source) (protected)
Module:Message box/ambox.css (view source) (protected)
Module:Message box/configuration (view source) (protected)
Module:Namespace detect/config (view source) (protected)
Module:Namespace detect/data (view source) (protected)
Module:Navbar (view source) (protected)
Module:Navbar/configuration (view source) (protected)
Module:Navbar/styles.css (view source) (protected)
Module:Navbox (view source) (template editor protected)
Module:Navbox/configuration (view source) (template editor protected)
Module:Navbox/styles.css (view source) (template editor protected)
Module:Other uses (view source) (template editor protected)
Module:Pagetype (view source) (protected)
Module:Pagetype/config (view source) (protected)
Module:Pagetype/disambiguation (view source) (protected)
Module:Pagetype/rfd (view source) (template editor protected)
Module:Pagetype/setindex (view source) (protected)
Module:Pagetype/softredirect (view source) (protected)
Module:SDcat (view source) (protected)
Module:String (view source) (protected)
Module:TableTools (view source) (protected)
Module:Unsubst (view source) (protected)
Module:Wikitext Parsing (view source) (protected)
Module:Yesno (view source) (protected)

Return to Mashup (web application hybrid).

Retrieved from "https://en.wikipedia.org/wiki/Mashup_(web_application_hybrid)"