Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

W3C Finalizes HTML5 Standard

DZone's Guide to

W3C Finalizes HTML5 Standard

· Java Zone ·
Free Resource

Download Microservices for Java Developers: A hands-on introduction to frameworks and containers. Brought to you in partnership with Red Hat.

Alright, so maybe it was only a matter of time, but yesterday, W3C has officially made HTML5 a W3C Recommendation.

This may not mean much to the vast majority of web developers out there who have long-since accepted HTML5 as the new standard. And yes, HTML5 has been around for years, and was adopted with little fight from anyone (except for Adobe).

So why is this so important?

For one, browsers will have to be developed around the new features HTML5 brings about, such as embedded video, vector graphics, and added API support. 

“Today we think nothing of watching video and audio natively in the browser, and nothing of running a browser on a phone. We expect to be able to share photos, shop, read the news, and look up information anywhere on any device. Though they remain invisible to most users, HTML5 and the Open Web Platform are driving these growing user expectations.”
- Tim Berners-Lee, W3C Director

If not for the huge strides HTML5 has taken, we’d still be years away from seamless, native in-browser video and audio. 

Going forward, W3C emphasizes community engagement and collaboration. With the Internet of Things emerging as the next big thing, W3C wants to be on the forefront of development with a focus on web-based applications.

But most importantly, now that HTML5 has been finalized, W3C can now start putting the bulk of its energy into working on HTML5.1.

Web standards for the future from W3C on Vimeo.

Download Building Reactive Microservices in Java: Asynchronous and Event-Based Application Design. Brought to you in partnership with Red Hat

Topics:

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}