Web 2.0 Conference Preview: Tools that make the collaborative web work for you

Outside the 650 area code, you might be able to go out for dinner without overhearing three Web 2.0 conversations, but new web technologies and business methods can still help your business. In our coverage of the upcoming Web 2.0 conference, we'll look at what the social networking, web services, open collaboration, and powerful browser features.

The Web's business and technology elite will convene for O'Reilly and Associates' third annual Web 2.0 Conference Nov. 7-9 in San Francisco's Palace Hotel. Started in 2004, the meeting lends its name to what some call a movement and others an ignorable wave of marketing hype.

What is Web 2.0? The concept is notoriously fluid, and easy to apply to whatever topic, site or idea that the speaker wants to show off. Tim O'Reilly's own definition includes a three-color diagram with 20-odd boxes and lines. The easiest definition, however, is simply the group of new Web sites that have grown after the dot-com crash at the turn of the millennium. The most interesting and important of these show four key properties: an emphasis on social software, exposing useful web services, a culture of openness, and a rich browser interface.

Is Web 2.0 relevant for open source developers, users, and IT managers? Although it may seem like just so much marketing fluff, Web 2.0 does have meaning for open source creators and users as well as IT decision-makers.


Web 2.0 sites exhibit, to steal a trick from Steven Colbert, "Opensourciness". Some of the most successful sites, like del.icio.us and digg.com, are an outgrowth of open source culture. Most sites began as personal projects to "scratch an itch" for developers and friends, or as small start-ups run on a tight budget. This has engendered a close interaction between developer and audience, and a consequent release early, release often responsiveness in the development of new features.

The start-up culture of Web 2.0, with more restricted post-crash budgets, has led to an even more pronounced dependence on open source software -- either a Linux Apache MySQL PHP/Perl/Python (LAMP) stack or increasingly popular alternatives including Lighttpd and Ruby -- than in the pre-crash Web. More importantly, as Web 2.0 sites have grown up into serious businesses, few have migrated away from the rapid-development high-level languages to "serious" development platforms.

Web 2.0 sites like the photo-sharing service Flickr encourage hacking of third-party tools, providing APIs and open-format data for plugins, extensions, and other experimentation by users. Some companies are even encouraging a purely API-based system, such as Amazon's interesting pay-to-play Web services. Some sites, such as WordPad, LiveJournal, and Wikipedia, release their software under a free license, encouraging the kind of improvements that feed back into their core sites.

One of the most notable features of many Web 2.0 sites, is the emergence of Asynchronous JavaScript and XML (AJAX) interfaces -- JavaScript-based dynamic sites that modify HTML and use micro-requests to the server. Most Web 2.0 sites incorporate some AJAX interactivity; some, such as meebo.com, make it the core of their interface. While JavaScript interfaces were once anathema, their re-emergence is directly attributable to the rise of Mozilla and Firefox, and to a lesser extent Konqueror and Safari, and the consequent viability of standards-based Web development. Thanks to these open source browsers, Web developers have been able to depend on richer interaction in their browser interfaces.

Most importantly, many Web 2.0 sites extend open source values into non-programmatic objects: images, video, text. Many, but by no means all, Web 2.0 sites support an open management culture, such as the one defined by Jonathan Nolen's Open Company Test. The Creative Commons suite of licenses, released in 2001, have been used extensively in blogging services such as Blogger and photo-sharing services such as Flickr. Although many sites support a "spectrum" of licenses -- from the most restrictive to the most liberal, and everything in between -- large content wikis such as Wikipedia make all their text and images available under free licenses. Together these services are making a huge corpus of work available for free use.

Awareness in the free and open community

Why should open source users and developers keep an eye on Web 2.0? Most directly, Web 2.0 cranks up the demands on open source software. Development challenges on the LAMP stack are higher than ever before, as Web 2.0 sites require flexibility for payloads ranging from frequent and tiny AJAX requests to multi-megabyte video and audio streams. Lean, efficient and powerful server tools, including Lighttpd and Ruby on Rails are drawing away developers from the LAMP stack.

On the client side, free desktops that incorporate Web services and Web API clients will have a growing importance for users. And Web 2.0 sites push free browsers to handle more than HTML and a handful of image formats and fulfill their promise as desktop platform in their own right.

There are also lessons to be learned from the rise of Web 2.0. The scaling of Web communities to thousands or even hundreds of thousands of users suggests that there is more that open source development teams can do to reach out to their users. Many Free and Open Source Software (FLOSS) teams are increasingly using Web 2.0 tools -- blogs, wikis, social software, even video sharing and podcasting -- to close the gap between developer and user.

Technically, Web 2.0 sites have proven the viability of the browser as a platform for rich, non-trivial user interface. The AJAX techniques used by the most visible Web 2.0 sites are slowly finding a place in open source applications, sometimes based on JavaScript libraries such as Dojo and Mochikit; we can expect more in the year to come. On the server end, Web 2.0 has also given a push to HTTP-based remote APIs like Simple Object Access Protocol, XML-RPC, and techniques like REST.

Web 2.0 sites are also providing alternative business models for commercial open source development. Web services based on providing a Web interface to open source software, such as WordPad and Wikia, have been able to contribute to the FLOSS commons but continue to compete on the strength of their content, community, and "hard" resources, including hardware and bandwidth.

IT managers and other open source deployment specialists will need to think hard about Web 2.0's increased requirements for their networks. Richer media types may require expanded bandwidth capacity, as well as browser upgrades or changes on the desktop. Employees used to social software technologies (blogs, wikis, social networking) at home may come to expect their availability inside the firewall. That culture of openness may extend beyond organizational boundaries to customers, partners and even competitors. On the development front, internal applications may increasingly be built around HTTP-based API architectures, with AJAX as a user interface platform replacing custom desktop tools.

But the future of Web 2.0 is not uniformly rosy; there are still some important outstanding questions that make open source users uneasy. Many Web 2.0 sites depend heavily on closed data formats such as Macromedia Flash; some sites, such as Flickr, degrade gracefully to AJAX, and others, including MySpace And YouTube, don't, and are essentially inaccessible to free software users.

The Web services architecture is also a source of concern. Though building software around public APIs may be convenient, it introduces a single point of failure that may be unacceptable. Open APIs, however useful, simply cannot provide the dependability of open source that you can run, modify and distribute yourself.

The question of software freedom also raises concerns. Open source advocates have, for years, expressed concern over the so-called "ASP loophole" and its potential to undercut the copyleft social contract. Web services that provide an interface to users, but no downloadable software, are exempt from most copyleft licenses' requirements to share the source code for their changes. The upcoming GPLv3, as well as the little used Open Software License and Affero General Public license, try to push Web service providers to share their modifications, but the model remains untried and raises its own problems for Web developers and users.

Of the top three Web sites, Google and Yahoo have been actively acquiring Web 2.0 companies, and both as well as Microsoft have incorporated Web 2.0 technical features into their core sites. As the third year of Web 2.0 begins, its once-fringe features are becoming the establishment. The open source community can benefit from a continued engagement with the Web 2.0 movement to further its own needs.

Learn more about this topic

Web 2.0 Conference

The O'Reilly defintion of Web 2.0

Bob Stumpel's canonical list of Web 2.0 sites

Open Company Test

This story, "Web 2.0 Conference Preview: Tools that make the collaborative web work for you" was originally published by LinuxWorld-(US).

Join the Network World communities on Facebook and LinkedIn to comment on topics that are top of mind.

Copyright © 2006 IDG Communications, Inc.

SD-WAN buyers guide: Key questions to ask vendors (and yourself)