HTML5 vs HTML6

Developments in coding HTML5 brought the ability to create dynamic faster and robust web apps and mobile-optimized solutions. In fact, HTML5 is a great mobile application template and has enabled support for video and audio, JavaScript API’s such as local storage, geolocation, and drag and drop, along with new organizational tags like <header>, <footer>, <article>, and <section>. But it has technical limitations and still leaves a lot to be desired.

The need of the hour is a semantic markup language that can help create a dynamic web app store. It shall allow freedom of code, not limited by standards and rules, in a human-readable format.

HTML6 provides XML-type namespaces and allows using only the required tags, without any conflict with other tags. These tags are defined for the user and not dependent on the browsers.

‍

Here is a comprehensive list of advantages that HTML6 can have over HTML5:

1. Integration with Camera:

HTML5 does not support this feature. Since users are now using apps on mobile phones and with devices that have a microphone and a camera attached, HTML6 allows adding video and photos captured from cameras into the forms. The form can also access stored photos in a device, and control the camera for the best live capture.  Websites thus can stay at par with apps that automatically integrate mobile camera shots.
‍

2. Control Over Video Objects:

There are many compression algorithms for the video objects embedded in HTML5, but there is no control over how the actual video frames are presented on a page. Currently, a rectangle is simply filled with video frames, and we can control only the text, with annotations and subtitles. HTML6 can give the advantage of using callback hooks along with synchronization, such as mixing of video with DOM objects.
‍

3. Guaranteed Libraries:

HTML5 has integrated JavaScript along with jQuery, but this entails different versions of the libraries separately loaded by each website. This wastes energy and performance. Some bandwidth is saved by standard libraries from Google and Yahoo. HTML6 can step this up by allowing standard libraries to be published along with the browsers. This could require a consortium of developers to agree on an approved generic library. This would save time in caching up the jQuery version as well.
‍

4. Flexible Image Sizing:

Images on a mobile need a different type of resolution than the image on a laptop, but HTML5 allows only <img> tag from a single standard SRC. The number of pixels is fixed; hence when the image has too many pixels, the browser must first downgrade it before displaying it. This is a hit on performance and wastes machine effort. HTML6 can support the specification of the required height and width of the image while retrieving the image from the server so that only the optimal resolution image is downloaded.
‍

5. Pluggable Pre-Preprocessors and Pluggable Languages:

Up till HTML5, you can use JavaScript to write your code, but it is strange that you need to specify the language as JavaScript, although none other is supported. Perhaps, this is for future compatibility which shall give flexibility to developers to move towards open-source that can be adopted by all the browsers. HTML6 could well provide this capability, by allowing pluggable languages that are more robust and familiar to the developer. The language could be pre-processed by the browser into JavaScript, leveraging the machine-specific capabilities for the most optimum code generation.
‍

6. Organized Annotation:

HTML5 allows for comments only at the base of the articles, but HTML6 can allow annotations to paragraphs, sentences, words, images, and even video for better organization.
‍

7. Power Micro-Formats:

HTML5 differentiates between headers, footers, headlines, etc. HTML6 could allow micro-formats to specify details such as phone numbers or parts of an address. This would make web crawlers faster. The markups for locations, items for sale, times, and dates can also be standardized.
‍

8. Auto Access to Contact Information:

HTML6 could allow the code to dig into the contact info stored say in a mobile phone automatically, instead of copy/paste that goes with HTML5. Automatic access over contact information should be restricted to only trusted and well-known domains, not all.
‍

9. Hard Authentication:

Hardwiring keys that can act as signing tokens instead of cookies and sessions authentications used by HTML5. This will make authentication faster and make sites more efficient. HTML6 can also add an API from trusted software to accept digital signatures.
‍

The features of HTML6 above can lead to making simpler websites, using the language that the developer is comfortable in and that best suits the nature of the app that is being developed. Automation and ease of semantics will lead to lesser error-prone development, which in turn makes the development process faster and more robust. Writing HMTL code shall not only be easier, but also more exciting, opening doors to more innovative designs and ideas.