|
Written by Webmaster
|
|
Saturday, 20 January 2007 |
|
I had the opportunity today to review Dion Hinchcliffe's data driven mashup demo using QEDWiki. Dion does a nice job covering in less than 13mins the concepts of assemble, wire and share. While his commentary about the QEDWiki mashup maker is spot on with respect to the assembly experience still being too complex for your average executive admin or knowledge worker, it was interesting to see how Dion himself was able to seamlessly create a new mashup application from scratch in minutes. If you have not yet read Dion's commentary on IBM's Mashup Maker, please do so and then check out his demo. It is a great way to see many of the concepts outline here on Mashboards.net in action. |
|
Last Updated ( Saturday, 20 January 2007 )
|
|
|
Perfect Storm for Mashups |
|
|
|
|
Written by Webmaster
|
|
Friday, 08 December 2006 |
|
Over the last third of the year I have gained a deep appreciation for the impact weather can have on enterprise mashups. Consider the decision making power an energy trader has if he has access to both historic and forecast data for wave heights and winds speeds in the Atlantic Ocean. With this power of information he can analyze the transportation times and inventory changes of oil based on weather delays. If his access to data was limited to only current and forecast wind and wave information, his ability to speculate on market prices would not be as great as if he additionally had access to historic trends. |
|
Last Updated ( Friday, 08 December 2006 )
|
|
Read more...
|
|
|
Written by Webmaster
|
|
Wednesday, 16 August 2006 |
|
I really like Dion Hinchcliffe's Mashup Anatomy article. Aside from putting a stake in the gound and attempting to categorize the various types of mashups, I found his Web Mashup diagram a perfect visual aid for helping to explain the mashup ecosystem. |
|
Last Updated ( Wednesday, 16 August 2006 )
|
|
Read more...
|
|
|
Exploring the Monetary Aspects of Mashups |
|
|
|
|
Written by Webmaster
|
|
Thursday, 03 August 2006 |
Directions Media recently published an article containing an interview, with Seisan President Curt Tomlinson, focused on the business of mashups. Seisan developed the Mapzierge and CaddyMap mashups that use the MapQuest API.
Tomlinson commented that "the major factor facing companies that have the data and assets to distribute via Service APIs is the ability to monetize what they are providing". Essentially he believes that technology is not the inhibitor for the adoption of Enterprise Mashups but instead the evolution and adoption of new business models associated with the mashup ecosystem. Unlike the web traffic energized advertisement revenue that fuels the availability of free APIs from companies like Google, we will eventually need to see transaction based revenue correlated to the selling of content and data service subscriptions. This is the same fee-based transaction obstacle that faced the adoption of Web Services five years ago.
|
|
Last Updated ( Thursday, 03 August 2006 )
|
|
Read more...
|
|
|
Written by Webmaster
|
|
Wednesday, 19 July 2006 |
Christine Herron provides a good summation of the twenty or more mashup entries that competed head-to-head in the speed geeking contest at Mashup Camp 2 (MC2). As a campster myself, I was happy to see my favorite mashup take first place honors based on the most Wooden Nickel votes. WeatherBonk won the speed geeking contest yet the spectrum of votes on the various entries raised a major issue about this new technology domain being referred to as "mashups".
Specifically, what is considered a mashup? While we seem to all agree with the Wikipedia definition, it becomes difficult to articulate why one mashup is better than another if we do not have a common understanding of the characteristics of a mashup. Furthermore, it becomes even more difficult to describe to a customer the scope of this new technology domain and why it is so unique if our examples tend to be instances of a very broad interpretation of the definition.
|
|
Last Updated ( Wednesday, 19 July 2006 )
|
|
Read more...
|
|
|
Commentary 