I Would like to know about how the book is organized. Is it more example oriented or more theoretical ? First chapter has used some HTML code and explained things nicely. What are the other kinds of examples used in the book (i.e: any other types of code and samples) ?
The mashups are broken down into 5 major categories: Harvest, Manage, Enhance, Assemble, and Test. A complete description of the patterns is available at the book's companion website.
It is definitely example-oriented, as each of the 34 patterns covered has an average of 3 examples included. However, these examples are not code-based (see some of my other posts this week) owing to the current maturity level of the technology. The goal here is to get readers to break out of a traditional development mindset that makes them dismiss certain solutions as technologically impossible. All of the examples in the book can be created with current mashup tooling. The book gives ascribes a set of Core Activities to each of the patterns which will help you choose the right product to help implement the examples.