Beginner knowledge: How to understand the Web2.0 standard?

web|web2| Standard | beginners

Web2.0 is not a specific thing, but a stage that is a term that facilitates the various technologies and related product services at this stage. So, we can't say what Web2.0 is, but it can be said that those are Web2.0.

These conditions are listed under the Web2.0 entry:

*CSS and semantic-related XHTML markup
*ajax Technology
*syndicationofdatainrss/atom
*aggregationofrss/atomdata
* Concise and meaningful URLs
* Support release for weblog
*restian (preferred) or Xmlwebserviceapis
* Some social networking elements

The elements that Web2.0 must possess are:

* The website should be able to allow users to put the data inside and outside the site system.
* Users have their own data in the website system
* Completely web-based, all features can be done through the browser.

(The above is quoted from the English version of Wikipedia)

synchronization, aggregation, and migration of XML data based on RSS/ATOM/RDF/FOAF

The data is no longer glued to the page and site, it's independent and it follows the user. This is a very important feature of Web2.0. This is why the blog is the representative of the Web2.0 reason. In the blog, often the protagonist is a mutual independent of the blog.

Independent, and then have physical manifestations. Now, we can make them active. Through the processing of XML data, these contents can be freely combined and presented and processed by various applications, whether they are web programs or desktop programs. Of course, the most important thing is behind the people.

Social factors

Content with people go, content can be the combination of user freedom, that is, users can freely use content media, create a community, the occurrence of various social (network) behavior. There are also tags and folksonomy based on the open tag system.

The third recognized factor is the open API

This is a little more technical, it takes time to study, and you can take a look at the examples: Amazon, Flickr, GoogleMap, and so on.

How do you create a Web2.0 product?

It is important to catch such a few points, one is the micro content (here is defined), one is the user individual.
In addition to these two basics, you can also consider sharing within the community and providing APIs.

Micro content: English is microcontent. Any data that the user produces is micro content, such as a blog, comment, picture, bookmark, favorite music list, what you want to do, where you want to go, new friends, and so on. These micro-content, filled with our lives, work and learning, its number, importance, as well as our dependence on it, and no less than those pious, suits the orthodox articles, papers, books.

The discovery and utilization of micro-content is a natural derivation of the equality, democracy and free atmosphere created by Internet, and it is also a result of Internet related technology to reduce the cost of information management.

We produce a lot of micro-content every day, but also consume the same amount of micro-content. For Web2.0, how to help users manage, maintain, store, share and transfer micro-content is the key.

User individual. For Web1.0 typical products/services, the user does not have a specific face, personality, it is just a vague group synonymous. But for Web2.0 products and services, the user is a real person. What Web2.0 serves is a specific person, not a ghostly concept. And the specificity of this person will be constantly enriched by the service itself.

How to serve this specific individual is the starting point of Web2.0 design.

Products/services that can be called Web2.0 will be like this:

Services to the user's micro-content collection, creation, distribution, management, sharing, cooperation, maintenance and other platforms.

What about the rest? I'm afraid I've been designing the XML representation of micro-content, the aggregation of micro-content, the migration of micro-content, the maintenance of social relations, the usability of the interface, and so on. And whether it is open source, participation, personal value, grassroots, cooperation and so on?

Web2.0 is the arrival of a new phase in which many aspects begin to evolve and implicate each other. Therefore, different people have different views. So what does Web2.0 mean for Web developers?

They say that the Web2.0 stage, the Web is a platform, or that the web is becoming programmable and can be executed by Web applications. The ambitious are assuming that its ultimate goal is webOS. Web1.0 time, the Web is just a publishing platform for people to read, the Web by a hypertext link. Now the trend has changed, the web is not just the world of HTML documents, it has become an interactive place.

Specifically, they say that the web becomes a development environment, with the help of a Web service-provided programming interface that makes a Web site a software artifact. This is the goal of WebService, the information island through these webservice dialogue, can be freely constructed into suitable for different applications of the building.

Some examples: del.icio.us, Flickr, A9, Amazon, Yahoo, Google, MSN and other programming interfaces derived from a variety of applications.

Why open APIs, this involves the commercial aspects of the market in the technical strategy. Of course, there is a deeper reason, what is that?

This interaction is not only reflected in the different Web services, but also in the browser interaction between the user and the Web. This is one reason why Web2.0 and Ajax are so relevant in the collection of delicious bookmarks. The convenience of using a desktop program on a Web page is really enjoyable. This is probably one aspect of Web programmability, and Web pages are no longer as simple as tagging and content mixing, it's a place to be programmed (is that understandable?). Some people objected that the use of Ajax is not friendly to search engines, only Web1.0 webmaster care about this matter, in Web2.0 time, the webmaster should be concerned about the convenience of user participation, the user's freedom, as for search, there are RSS/ATOM/RDF, but not to worry about, Google has not complied with this trend, so that everyone volunteered to submit it?

The third aspect of programmability is the seamless connectivity trend between Web applications and desktop applications. Like here said "from the tool, is the Internet browser to various browsers, RSS reader, and other content development" programming is an important purpose of the operation of the data, so for the site, in addition to the WebService interface, the most recent way is to rss/rdf/atom the content in the format , or meaningful XHTML format output, while implementing the separation of content and performance.

Web2.0 is a historical concept, not a technical one, it is the result of the historical dating of web development. The concept of carding, can help me better grasp the internet is happening technology and culture.