HISTORY OF HTML
In 1980, physicist
Tim-Berners-Lee, a contractor at CERN proposed internet-based hypertext
system.
It was formally defined
by Internet Engineering Task Force (IETF).
After the development of
Html, IETF created an Html working group. The HTML working group developed Html 2.0 in
1995.
The combined work of the World Wide Web Consortium (W3C) and Web Hypertext Application Technology
Working Group (WHATWG) released a greater number of advanced Html versions Html
3.2 in 1997, Html 4.0 in 1997, Html 4.01 in 1999
After a long interval,
Html released a new version called Html5 in 2014. Html5 enhances the web pages
to a new world.
In 2016 Html 5.1 version
was released by W3C.
Now let's have a brief
history of versions of HTML that we have till now.
HTML 1.0
HTML
1.0 was the first release of HTML to the world. Not many people were involved
in website creation at the time, and the language was very limiting. There
really wasn’t much you could do with it bar getting some simple text onto the
web.
HTML 2.0
HTML
2.0 included everything from the original 1.0 specifications but added a few
new features to the mix. HTML 2.0 was the standard for website design until
January 1997 and defined many-core HTML features for the first time.
HTML 3.0
More
and more people were getting into the HTML game around now, and while the previous
standards offered some decent abilities to webmasters (as they became known), they
thirsted for more abilities and tags. They wanted to enhance the look of their
sites.
This
is where the trouble started. A company called Netscape was the clear leader in the
browser market at the time, with a browser called Netscape Navigator. To
appease the cries of the HTML authors, they introduced new proprietary tags and
attributes into their Netscape Navigator browser. These new abilities were
called Netscape extension tags. This caused big problems as other browsers
tried to replicate the effects of these tags so as not to be left behind but
could not get their browsers to display things the same way. This meant that if
you designed a page with Netscape ETs, the page would look bad in other
browsers. This caused confusion and irritation for the markup pioneers.
At
this time, an HTML working group, led by a man named » Dave Raggett introduced a
new HTML draft, HTML 3.0. It included many new and improved abilities for HTML and promised far more powerful opportunities for webmasters to design their
pages. Sadly, the browsers were awfully slow in implementing any of the new improvements,
only adding in a few and leaving out the rest. Partly,
this failure can be
attributed to the size of the overhaul, and so the HTML 3.0 spec was abandoned.
Thankfully, the people in
charge noted this and so future improvements were always designed to be
modular. This meant they could be added in stages, which makes it easier on the
browser companies.
HTML 3.2
The browser-specific tags
kept coming, and it became increasingly apparent that a standard needed to be found.
To this end, the » World Wide Web Consortium (abbreviated the W3C) was
founded in 1994 to standardize the language and keep it evolving in the right
direction. Their first work was code-named WILBUR, and later became known as »
HTML 3.2. This was a toned-down change to the existing standards, leaving many
of the big steps forward for later versions. Most of the extension tags that
had been introduced by Netscape (and to a lesser extent, Microsoft) did not
make it into these new standards. It soon caught on and became the official standard
in January ’97, and today practically all browsers support it fully.
HTML 4.01
HTML 4.0 was a large
evolution of the HTML standards and the last iteration of classic HTML. Early
in development, it had the code-name COUGAR. Most of the new functionality
brought in this time is from the ill-fated HTML 3.0 spec, as well as a host of trimmings
on old tags and support for HTML’s new supporting presentational language,
cascading stylesheets.
HTML
4.0 was recommended by the W3C in December ’97 and became the official standard
in April 1998. Browser support was undertaken surprisingly earnestly by Microsoft
in their Internet Explorer - browser, and the market-leading IE5 (and current successor
IE6) has excellent support for almost all of the new tags and attributes. In comparison,
Netscape’s terribly flawed Navigator 4.7 was inept when it came to HTML 4.0 and
even basic CSS. Modern browsers however are a vast improvement.
Once
HTML 4.0 had been out for a little while, the documentation was revised and corrected
in a few minor ways and was entitled HTML 4.01; the final version of the specification.
XHTML 1.0 (Extensible
hypertext markup language)
Close to the beginning of
the 21st century, the W3C issued their » specifications of XHTML 1.0 as a
recommendation. Since January 26, 2000, it stands as the joint standard with
HTML 4.01. XHTML marks a departure from the way new specs have worked — it is
an entirely new branch of HTML, incorporating so that code must be properly
written if it is to work once it reaches the reader’s browser. There weren’t
many new or deprecated tags and attributes in XHTML, but some things changed
with a view of increased accessibility and functionality. It’s mainly just a
new set of coding rules.
HTML5
After HTML 4.01 and XHTML
1.0, the guys who were in control of HTML’s direction got sidetracked working
on a new proposal for XHTML 2. At the same time, clever web developers were
innovating constantly, hacking new functionality into websites and browsers.
The path that XHTML 2 was taking started to look both boring and unrealistic,
and it became pretty clear that a new approach was needed.
It
was around this time that a bunch of pragmatic web technology fans, browser programmers, and specification writers started building something of their own, outside of the
usual W3C procedures. They called themselves the Web Hypertext Application Technology
Working Group (WHATWG). After some soul-searching, the W3C decided that HTML
was still the future of the web. XHTML 2 was discontinued and HTML5 became the
new specification that everyone’s effort should be poured into.
Comments
Post a Comment
Subscribe Us and Thanks for visiting blog.