Table of Contents
Before you set out to build your own mashups, you’ll study some specific examples in this chapter. Mashups combine content from more than one source into a new integrated whole. You can understand a specific mashup by answering a number of basic questions:
What is being combined?
Why are these elements being combined?
Where is the remixing or recombination happening?
How are various elements being combined (that is, first in the interface but also behind the scenes in the technical machinery)?
How can the mashup be extended?
This chapter will explore three major examples:
Housingmaps.com
The Google Maps in Flickr Greasemonkey script
Jon Udell’s LibraryLookup bookmarklet
In this chapter, I will analyze these three examples using the previous questions loosely as a framework. A close study of each of these mashups will be amply rewarded when you start creating your own mashups.
One pattern you will see repeated among mashups that link two web sites is the combination of three actions:
Data is extracted from a source web site.
This data is translated into a form meaningful to the destination web site.
The repackaged data is sent to the destination site.
Of course, the details differ among the mashups, but this general pattern holds true, as you will see in the three mashups presented in detail in this chapter. Where the remixing actually happens differs in the three mashups you’ll see in this chapter: in a separate application as in Housingmaps.com, in Flickr for the Google Maps in Flickr script, and in the browser without a change of interface as in the LibraryLookup bookmarklet.
Although you’ll see this pattern of data extraction, translation, and redirection in the mashups covered in this chapter, you’ll find other patterns in mashups as well. Chapter 9 will explore those other patterns in detail.