In the previous post I described the simple differences between Web 2.0 and Web 1.0 and identified seven principles outlined by Tim O'Reilly [1]. O'Reilly's seven principles offer a logical jump-off point for exploring the Web 2.0 phenomenon. In this entry I will discuss his first principle, The Web as Platform [1].
According to O'Reilly, "You can visualize Web 2.0 as a set of principles and practices that tie together a veritable solar system of sites that demonstrate some or all of those principles, at a varying distance from that core" [1]. See the below "meme map" for a graphical description. The map offers an outstanding visual -- a picture is worth a thousand words -- for how Web 2.0 is developing the web as platform. Most importantly, the web (the platform) is constantly changing to meet the needs of the Internet community -- giving the user a stake in the development and modification of content accessible to any user with a browser and web access.
One of the key ideas of The Web as Platform is that client side applications, such as the Microsoft Office Suite, and their development, release, and distribution cycles will become obsolete. O'Reilly sums this philosophy up nicely [1]:
"There will be no scheduled software releases, just continuous improvement. No licensing or sale, just usage. No porting to different platforms so that customers can run the software on their own equipment, just a massively scalable collection of commodity PCs running open source operting systems plus homegrown applications and utilities that no one outside the company ever gets to see."
The Web as Platform is a key principle to understanding the Web 2.0 phenomenon. The ability to harness collective intelligence to create and edit data collectively within the web community is what makes the web a powerful, scalable platform. The Web as Platform principle allows users to run software applications entirely through a browser. Instead of just viewing a site, Web 2.0 sites often offer rich, user-friendly interfaces that encourage users to add value to applications as they use them.
In the next blog entry I'll discuss the second principle: Harnessing Collective Intelligence.
References:
1. Tim O'Reilly (2005-09-30). What is Web 2.0: Design Patterns and Business Models for the Next Generation of Software
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment