The gap between data providers and the mashup makers who love them
JohnFeller 110000RUW6 Tags:  kapow mashups situationalapps qedwiki wiki web2.0 strikeiron mashupcamp 1,538 Visits
I attended a Mashup Camp session this morning on mashup development tools. Itstarted just as you might expect. The moderator asked us to list offtools that we were familiar with, which solicited a long collection ofprogramming languages, libraries, IDEs, etc. QEDWiki was listed as one ofthem. But the next issue was how those tools get access to anduse/display data. This gave rise to the traditional Model ViewController discussion and about the apparent disparity in how access tovarious data sources was achieved. After all, if you're a hard-coreprogrammer, writing code to interact with Joe's Web service is easy. But if you're not, unless it's a simple feed, you're stuck. What'sneeded of course is a widget standard that allows the data provider toallow his data to be used in a variety of mashup platforms. Someoneprotested that the various framework providers would be unlikely to support such a standard, but Iasserted that it was the content providers who had a vested interest inpursuing such a standard. The group seemed to agree. The group alsoseemed to understand the need for a standard interface between thewidgets and the frameworks that support them. Sounds good, right?
Well,maybe not. This morning I proposed leading a discussion on whatstandards might be needed to facilitate the lifecycle of and interactionsbetween widgets. The person passing the microphone around basically took the microphone from me while I wastalking and said to me "You're talking about standards? It will be amiracle if anyone shows up for that!" Also, I've spoken to a couple other folks who have said much thesame thing. This group may not yet be interested in talking standards,even if it is in their interest. A few folks get it. The StrikeIronguys do. So do the Kapow guys. But of course they are both contentproviders. The AOL guys seem to get it too based on their microformatwork. I'll be participating in a session with them on microformatstomorrow morning. And in fact, microformats are of course a form ofstandard. Maybe it's best to just stay away from the term "standard". I need to think about how I might better state things for thisaudience. Anyway, it will be interesting to see who shows up to mysession this afternoon. I'll let you know.
Thanks for reading,