HTML 5 - First Tests and Analysis
As a Web Development Lead at Tekriti, I have been at the forefront of developing the HTML, CSS and JS for several projects which Tekriti has been executing. What has been notable in this entire experience of mine is how little the HTML markup has evolved in the past 10 years or more. Sure we have definitely moved from table'd layouts to table less layouts, we have made concentrated efforts on keeping the HTML fluid, using CSS 2.0 and following W3C standards to the maximum. All of the above was the learning which me and my team has had over the past 4 years as Web 2.0 came calling. However there was still something lacking, as all this learning was more from a standards and discipline perspective, nothing new from a markup or technology perspective. One thing is for sure, HTML'ization of websites is a specialized job with a special set of skills and experience (especially with the plethora of browsers around these days IE6, 7, 8, Mozilla FF, Chrome, Safari, Opera).
The advent of HTML 5 is a breath of fresh air for the community of Web Developers whose core focus is to do the work as described above. Even though the draft reflects an effort started in 2004, the issues associated with browsers adding support for HTML made it hard for the roll out. Chrome and FireFox have taken the lead in this effort, with Chrome 3.0 and FF 3.5 supporting a sub-set of the tags for HTML 5. I believe HTML 5 will have a great impact on the Website development for the new age Web 2.0 sites and browsers.
This series of posts will cover details about HTML 5. If you have anything to do with web based software development , then HTML is the air you breathe. So follow this series to increase your awareness about the revolution called HTML 5.
HTML 4 introduced in 1997 gave a rough guide to many of the core features of HTML, but it did not provide enough definition on the kind of content deployed on the page (like video, article, audio etc). The same goes for XHTML 1, which defines an XML for HTML 4, which defines JavaScript APIs for both HTML and XHTML.
The HTML5 draft reflects an effort, started in 2004, to study contemporary HTML implementations and deployed content. The draft:
The following areas / features defined in HTML 5 are believed to impact the Web architecture (Source: W3C draft on HTML5)
Cheers to the new revolution !!
The advent of HTML 5 is a breath of fresh air for the community of Web Developers whose core focus is to do the work as described above. Even though the draft reflects an effort started in 2004, the issues associated with browsers adding support for HTML made it hard for the roll out. Chrome and FireFox have taken the lead in this effort, with Chrome 3.0 and FF 3.5 supporting a sub-set of the tags for HTML 5. I believe HTML 5 will have a great impact on the Website development for the new age Web 2.0 sites and browsers.
This series of posts will cover details about HTML 5. If you have anything to do with web based software development , then HTML is the air you breathe. So follow this series to increase your awareness about the revolution called HTML 5.
HTML 4 introduced in 1997 gave a rough guide to many of the core features of HTML, but it did not provide enough definition on the kind of content deployed on the page (like video, article, audio etc). The same goes for XHTML 1, which defines an XML for HTML 4, which defines JavaScript APIs for both HTML and XHTML.
The HTML5 draft reflects an effort, started in 2004, to study contemporary HTML implementations and deployed content. The draft:
- Defines a single language called HTML 5 which can be written in HTML syntax and in XML syntax.
- Defines detailed processing models to interoperable implementations.
- Improves markup for documents.
- Introduces markup and APIs for emerging idioms, such as Web applications.
- It will replace these documents HTML4, XHTML
The following areas / features defined in HTML 5 are believed to impact the Web architecture (Source: W3C draft on HTML5)
- The use of the DOM as a basis for defining the language.
- The concept of browsing contexts.
- The distinction between user agent requirements and authoring requirements.
- The new content model concepts (replacing HTML 4's block and inline concepts).
- The focus on accessibility as a built-in concept for new features (such as the hidden attribute, the progress element, et cetera) instead of an add-on (like the alt attribute).
- The focus on defining the semantics in detail
- The menu and command elements.
- The origin concept.
- Offline Web application caches.
- The definition of the browsing context "navigation" algorithm and the related session history traversal algorithms.
- The content-type sniffing and character encoding sniffing.
- The very explicit definition of a parser.
- The contentEditable feature and the UndoManager feature.
- The Drag and Drop and Copy and Paste architecture.
- The cross-document messaging feature (the postMessage API).
- The new sandboxing features for iframe.
- The definition of URL.
Cheers to the new revolution !!
