It seems to me that lately it's all too often that some turnip with a keyboard and a news story quota starts talking about "Web 2.0 Technologies" without clarifying what that means. Probably because the turnip has no idea what it means, but some stats came across the newswire from an analylst firm and hey, a quick writeup means one less article to write for the day.

Perhaps it's because as an industry we haven't yet set the ground rules for what the difference between applications and technologies are in the Web 2.0 world. It's time we did that, don't you think? That way the turnips don't have to think about it, and when we read what they write we grok what they're trying to say, even if they don't.

Language and terminology have always been barriers for emerging technologies. One of the hurdles to SOA adoption was finding a common language between IT and the business, and now we're seeing the same obstacles with understanding Web 2.0. We need a common set of definitions so that when we're talking about applications or technologies, we don't have to spend the first hour debating what those terms mean.

There is a difference between "technologies" and "applications". Applications are what users see and use, technologies are what developers use to build applications. This isn't breaking news, or shouldn't be, and yet for some reason the whole Web 2.0 concept is completely messing with definitions and basic concepts that have enabled us all to understand each other when discussing these same concept since the inception of the Web.

 

 

So here's your Web 2.0 stack. Web 2.0 is primarily about building community that is enabled through the deployment of applications that were composed and developed using technologies.

COMMUNITY

 

 

APPLICATIONS (USER LAYER)

 

 

 

 

TECHNOLOGIES (DEVELOPER LAYER)

 

 

 

Imbibing: Coffee

Technorati tags: , , , , , ,