At the root of what a mashup is the the question of what’s being "mashed" together into something new.  Is it data?  Is it visual presentation? Is it the underlying functionality (code)? The answer of course is that a mashup could be all of these things, or just one of them.  In the end, mashups are intentionally loosely defined because of their very nature as ad hoc aggregations of whatever needs to be aggregated. Whether that is visuals, information, or working software is immaterial to the term’s application.  ^{link »}

An increasing number of companies such as Bridgewerx , Kapow , Worcsnet , and others are trying to solve (or partially solve) the problem of requiring programming skills to create mashups.  This means mashups will become much more end-user directed in the near future as facilitation techniques become more sophisticated.  They will be created by almost anyone for just-in-time situations and projects, and even thrown away when their usefulness ends.  ^{link »}

Mashups connote a mindset of informal techniques that just work by virtual of the concept of "small pieces, loosely joined".  ^{link »}

The 5 styles of mashups ^{link »}

Presentation Mashup ^{link »}

Client-Side Data Mashup ^{link »}

Client-Side Software Mashup ^{link »}

Server-Side Software Mashup ^{link »}

Server-Side Data Mashup ^{link »}

tags: mar 09, blogs.zdnet.com

blogs.zdnet.com/Hinchcliffe/?p=49 · Original page