Web 1.0
The first iteration of the web represents the web 1.0, which, according to Berners-Lee, is the “read-only web.”
In other words, the early web allowed us to search for information and read it. There was very little in the way
of user interaction or content generation.
The first iteration of the web represents the web 1.0, which, according to Berners-Lee, is the “read-only web.”
This was what most website owners wanted. They needed a website to make their information available to anyone at
any time. I call this “brick-and-mortar thinking applied to the web.” The web as a whole hasn’t moved much
beyond this stage.
Shopping cart applications, which most ecommerce sites use in some form, fall under the category of web 1.0. The
overall goal is to present products to potential customers — much as a catalog or a brochure does — to anyone in
the world. The web provides the exposure. It removes the geographical restrictions associated with
brick-and-mortar businesses.
Web 2.0
We are now seeing the infancy of web 2.0, or the “read-write” web as Berners-Lee described it. It’s the ability
to contribute content and interact with other web users. It has dramatically changed the landscape of the web in
a short time. It has much potential. As examples, look at YouTube and MySpace, which rely on user submissions.
Web 2.0 is a welcome response to web users, who want to participate in the information.
There are many definitions of a “web 2.0 application.” For example, there’s the perception that just because a
website is built using a certain technology (such as Ruby on Rails) or because it employs Ajax in its interface,
it represents web 2.0. But that is not necessarily the case. Web 2.0, for lay people, simply requires that users
can interact or contribute content.
Web 3.0
This leads us web 3.0 (extending the vague nomenclature). By extrapolating Tim Berners-Lee’s explanations, web
3.0 is “read-write-execute.” This is difficult to envision in its abstract form. To illustrate, consider
semantic markup and web services.
Semantic markup refers to the communication gap between humans and computerized applications. One of the biggest
challenges of presenting information on the web is that applications cannot provide context to data, and,
therefore, can’t understand what is relevant. Through the use of some sort of semantic markup (or data
interchange formats), data could be put in a form not only accessible to humans via natural language, but able
to be understood and interpreted by software applications as well.
While it is still evolving, this notion — formatting data to be understood by software agents — leads to the
“execute” portion of the web 3.0 definition.
A web service is a software that supports computer-to-computer interaction over the internet. Web services are
not new and usually take the form of an application programming interface. The popular photography-sharing
website Flickr provides a web service whereby developers can programmatically interface to search for images.
There are thousands of web services. Combining semantic markup and web services can produce a web 3.0 experience
— applications that can speak to each other directly and interpret information for humans.
main diffrences between web versions:
1.page state-wed 1 static
web 2 users add content to web sites
wed 3 Machine learning & NLP
2.interactive- web 1 not interactive
web 2 blogs and so
web 3 addes Semantic markup
3.user personalisation- web 1 not aware of the user at all
web 2 basic users understanding
web 3 addes information or suggestions for the user.
use case:
if we search for ben gurion in the web
in web 1 we will get sites with basic information static site perhaps a site who someone wrote abut the person.
in web 2 we will get sites with information about multiple meanings, blog or websites about the topic from multiple
users.
in web 3 we will get sites with context about the topic regards my history in the web, if i am a student in ben
gurion university i probably get the university site.
