Participatory Web 2.0 for development in short Web2forDev is a way of employing web services, in order to improve information sharing and collaborative production of content in the context of development work. In this context actors in development can easily relate to other stakeholders, have selective access to information, produce and publish their own content and redistribute pieces of content released by others. They can integrate, combine, aggregate, generate, moderate and mediate content. In a typical Web2forDev scenario data and/or functionalities from a number of free/low cost online applications are combined and served as mashups thus ensuring a wide range of online services at low cost.

Usage

Web 2.0 applications are used in the development sector for a number of purposes and by different actors. Examples are …

• Internet/SMS gateways are being used to distribute development-related information to people with access to mobile phones but without access to internet. Similarly, these gateways enable mobile phone users to make their presence on the internet by posting to blogs and online databases via sms, etc.
• Tagging systems and content aggregation enable users with access to only low-bandwidth to find quickly the information they are searching for, without having to navigate through many bandwidth-demanding websites.
• Users with old computers can take advantage of some online applications which can process their computing tasks the way their computers never could (eg. online version of Adobe Photoshop)
• Users who don’t own their own PCs are using online services to store all their data, such as emails, documents, photos, etc, thus having access to them from any computer connected to internet. That way, online storage spaces and related services substitute physical hard drive spaces (PCs) which in many regions are shared by many users.

Web 2.0 can be described in 3 parts, which are as follows:

Rich Internet application (RIA) — defines the experience brought from desktop to browser whether it is from a graphical point of view or usability point of view. Some buzzwords related to RIA are Ajax and Flash.

Web-oriented architecture (WOA) — is a key piece in Web 2.0, which defines how Web 2.0 applications expose their functionality so that other applications can leverage and integrate the functionality providing a set of much richer applications (Examples are: Feeds, RSS, Web Services, Mash-ups)

Social Web — defines how Web 2.0 tends to interact much more with the end user and make the end-user an integral part.
As such, Web 2.0 draws together the capabilities of client- and server-side software, content syndication and the use of network protocols. Standards-oriented web browsers may use plug-ins and software extensions to handle the content and the user interactions. Web 2.0 sites provide users with information storage, creation, and dissemination capabilities that were not possible in the environment now known as “Web 1.0″.

Web 2.0 websites include the following features and techniques: Andrew McAfee used the acronym SLATES to refer to them:[23]
Search
Finding information through keyword search.
Links
Connects information together into a meaningful information ecosystem using the model of the Web, and provides low-barrier social tools.
Authoring
The ability to create and update content leads to the collaborative work of many rather than just a few web authors. In wikis, users may extend, undo and redo each other’s work. In blogs, posts and the comments of individuals build up over time.
Tags
Categorization of content by users adding “tags”—short, usually one-word descriptions—to facilitate searching, without dependence on pre-made categories. Collections of tags created by many users within a single system may be referred to as “folksonomies” (i.e., folk taxonomies).
Extensions
Software that makes the Web an application platform as well as a document server. These include software like Adobe Reader, Adobe Flash player, Microsoft Silverlight, ActiveX, Oracle Java, Quicktime, Windows Media, etc.
Signals
The use of syndication technology such as RSS to notify users of content changes.
While SLATES forms the basic framework of Enterprise 2.0, it does not contradict all of the higher level Web 2.0 design patterns and business models. In this way, a new Web 2.0 report from O’Reilly is quite effective and diligent in interweaving the story of Web 2.0 with the specific aspects of Enterprise 2.0. It includes discussions of self-service IT, the long tail of enterprise IT demand, and many other consequences of the Web 2.0 era in the enterprise. The report also makes many sensible recommendations around starting small with pilot projects and measuring results, among a fairly long list.

The term Web 2.0 is associated with web applications that facilitate participatory information sharing, interoperability, user-centered design, and collaboration on the World Wide Web. A Web 2.0 site allows users to interact and collaborate with each other in a social media dialogue as creators (prosumers) of user-generated content in a virtual community, in contrast to websites where users (consumers) are limited to the passive viewing of content that was created for them. Examples of Web 2.0 include social networking sites, blogs, wikis, video sharing sites, hosted services, web applications, mashups and folksonomies.
The term is closely associated with Tim O’Reilly because of the O’Reilly Media Web 2.0 conference in late 2004. Although the term suggests a new version of the World Wide Web, it does not refer to an update to any technical specification, but rather to cumulative changes in the ways software developers and end-users use the Web. Whether Web 2.0 is qualitatively different from prior web technologies has been challenged by World Wide Web inventor Tim Berners-Lee, who called the term a “piece of jargon”, precisely because he intended the Web in his vision as “a collaborative medium, a place where we [could] all meet and read and write”. He called it the “Read/Write Web”.