Friday, 1 October 2010

Brief History of HTML5


excerpt from this great post: http://bit.ly/9IhTKA (Smashing Mag)
Once upon a time, there was a lovely language called HTML, which was so simple that writing websites with it was very easy. So, everyone did, and the Web transformed from a linked collection of physics papers to what we know and love today.
Most pages didn’t conform to the simple rules of the language (because their authors were rightly concerned more with the message than the medium), so every browser had to be forgiving with bad code and do its best to work out what its author wanted to display.
In 1999, the W3C decided to discontinue work on HTML and move the world toward XHTML. This was all good, until a few people noticed that the work to upgrade the language to XHTML2 had very little to do with the real Web. Being XML, the spec required a browser to stop rendering if it encountered an error. And because the W3C was writing a new language that was better than simple old HTML, it deprecated elements such as  and.

A group of developers at Opera and Mozilla disagreed with this approach and presented a paper to the W3C in 2004 arguing that, “We consider Web Applications to be an important area that has not been adequately served by existing technologies… There is a rising threat of single-vendor solutions addressing this problem before jointly-developed specifications.”
The paper suggested seven design principles:
  1. Backwards compatibility, and a clear migration path.
  2. Well-defined error handling, like CSS (i.e. ignore unknown stuff and move on), compared to XML’s “draconian” error handling.
  3. Users should not be exposed to authoring errors.
  4. Practical use: every feature that goes into the Web-applications specifications must be justified by a practical use case. The reverse is not necessarily true: every use case does not necessarily warrant a new feature.
  5. Scripting is here to stay (but should be avoided where more convenient declarative mark-up can be used).
  6. Avoid device-specific profiling.
  7. Make the process open. (The Web has benefited from being developed in the open. Mailing lists, archives and draft specifications should continuously be visible to the public.)
The paper was rejected by the W3C, and so Opera and Mozilla, later joined by Apple, continued a mailing list called Web Hypertext Application Technology Working Group (WHATWG), working on their proof-of-concept specification. The spec extended HTML4 forms, until it grew into a spec called Web Applications 1.0, under the continued editorship of Ian Hickson, who left Opera for Google.
In 2006, the W3C realized its mistake and decided to resurrect HTML, asking WHATWG for its spec to use as the basis of what is now called HTML5.

4 comments:

tarek bdworker24 said...

This web site is very nice.
white hat SEO services

tarek bdworker24 said...

this web site is very helpful.
white hat SEO services

tarek bdworker24 said...

this web site is very helpful.
white hat SEO services

5j7q3h4nu9 said...

Another methodology consists of an inkjet 3D printing system, which creates the model Duvet Covers one layer at a time by spreading a layer of powder and printing a binder in the cross-section of the half utilizing an inkjet-like process. With laminated object manufacturing, thin layers are minimize to shape and joined. In addition to the previously mentioned methods, HP has developed the Multi Jet Fusion which is a powder base approach, although no lasers are concerned. An inkjet array applies fusing and detailing agents that are then mixed by heating to create a strong layer. The primary variations between processes are in finest way|the means in which} layers are deposited to create parts and in the materials may be} used.

Real Time Web Analytics