HTML5 : Vocabulary and Interfaces

HTML5 can be difficult to understand at high end usage. Basic usage of HTML5 is otherwise easy. Here is a list of Vocabulary and Interfaces for HTML5. We talked about the HTML5 Basics in previous article. This is an advanced article for the developers and who actually want to create more interactive websites with web applications like WordPress.

 

Preface to HTML5 Vocabulary and Interfaces

 

HTML5 without using the all features practically has no difference with previous versions. That is how over 80% general developers still uses HTML5. The first landmark in CMS category is definitely WordPress. Without a custom crafted Child Theme of a specific theme framework, the full advantage of WordPress is not utilized. This child theme is the main game where the developer’s skill can change many things. If you can not afford that price, it is better to use the default one. Others are jokes because they never implement or rather has the the knowledge to implement schema.org. We were not updating anything about HTML5 because the only practical WordPress theme framework was not releasing their Beta version of Theme Framework.

Practically the Webpages on a scalable platform becomes like a web application. It goes fully interactive, you can implement your own API. With CSS3, the need of graphical parts has been decreased. But to really make your website like Google Plus, like the smaller examples – Twitter Card Embed Options in WordPress, Google Plus Interactive Posts ; a real semantic web is possible to build. Its really a tougher work to work with.

Google will discontinue to use other than schema.org markup in future. So actually we can eliminate the other microdata except the Open Graph and Dublin Core. We wrote that article on Dublin Core, right 2 years back. They all are not a part of HTML5 – true. But, you actually can not think of a webpage without these markups. The reason to publish this article on HTML5 – Vocabulary and Interfaces is to create a list of attributes, which will work as a reference in future guides to make an average developer to use all the features of HTML5.

 

HTML5 : Vocabulary and Interfaces

 

The vocabulary : The vocabulary of HTML5 is composed of the vocabulary of previous HTML specifications up to date, proprietary ingredients, as well as some new elements together, including for example parts of the Ruby -element group, which were introduced in XHTML 1.1. However, this includes only the portion of HTML, developers may use for creating documents and Web applications. In addition to the vocabulary of a clear structural model is defined, so the rules by which the various elements may be nested.

The HTML parser : For the first time, since the emergence of HTML, the language is no more than an application of SGML , but even as a generalized language in the form of SGML. This is justified by the fact that even modern browser with HTML not an SGML parser, but a matching for web parser process. How this function parser must work is currently not defined. HTML5 will change this by defining an HTML parser and avoid that there are differences between the HTML parsers of different browsers manufacturers. What makes the parser contained in HTML5 is that part only the allowed vocabulary, but also all the other elements that were present in earlier versions will exist only as proprietary elements. Through these precise definition HTML5 aims are to ensure that the parser to documents available on the web is backwards compatible.

HTML, XHTML, and the DOM : Each element and attribute that is known in HTML5 is defined in terms of the document object model. This applies regardless of whether the element or attribute is a permitted language component. This means that, besides the importance of the structural elements and its DOM interface and related interfaces (methods and properties) can be defined. Based on this definition, HTML5 allows the representation of documents in three variants: Documents that the media type ” text/html possess “shall be deemed to HTML documents. They are processed by the HTML parser. This variant is colloquially referred to as HTML5.

Documents that is of an XML media type – “application/xhtml+xml”or “application/xml “- which possess valid as XML documents are processed by an XML parser. This variant is referred to colloquially as XHTML5. The previous documents have a common document object model. The DOM is often mentioned in this context as dom5. HTML5 tries to reduce the differences between these three variants on the form of the respective inherent limitations. The core of the DOM specification says that HTML elements in the null namespace are included.

HTML Microdata : This specification tries to define the embedding machine readable information in HTML documents. The aim is that this mechanism is clearly defined and to other formats such as RDF and JSON is compatible.

Inclusion of SVG and MathML : HTML5 provides a simple way of SVG and MathML in the HTML source.

HTML Canvas 2D Context : In this specification, interfaces are defined for drawing two-dimensional shapes. As a sign of the surface is introduced in the main specification as canvas element.

HTML5 History API : You can see live example of simple usage here :

 

Example of Using Various New Methods to Combat Internet Explorer

 

Internet Explorer itself is a solid joke from Microsoft. Since Internet Explorer doesn’t recognize the article tag :

 

 
Resulting in appearing of the text as plain text without CSS in the above example; We need to use :
 

We need to use HTML5Shiv :

 

HTML5Shiv is an example fix for combating issues. There are good number of such fixes, tricks for HTML5.

This Article Has Been Shared 3152 Times!

Facebook Twitter Google+ Pinterest