Signaling Polymer's production readiness, Google announced release 1.0 at its annual I/O developer conference. A core library used to build and style Web components, Polymer transitioned rapidly from concept to production release in less than two years.
The Electronic Frontier Foundation (EFF) has issued an angry formal response to a proposed set of HTML5 standards from the World Wide Web Consortium, saying that stringent digital rights management technology will be harmful to online freedom and prevent many users from getting access to important content.
Those curious about the final release date for the hotly debated HTML5 need wonder no more: The W3C (World Wide Web Consortium) plans to finalize the standard by July 2014, the organization announced Monday.
Several standards exist for storing large amounts of data in a user's Web browser. Each has its benefits, tradeoffs, W3C standardization status and level of browser support. All are better than cookies.
New APIs in the forthcoming HTML5 make it much easier for Web applications to access software and hardware, especially on mobile devices. The W3C is taking privacy seriously as it puts the finishing touches on HTML5, but there are still some important things to consider.
It was all the way back in the Spring of 2011 that Google released <a href="http://en.wikipedia.org/wiki/WebRTC">WebRTC</a>, its nascent real-time, browser-based, HTML5-powered, no-plugin-required video chat project to the public. In the three and a half years since, the Internet Engineering Task Force and the W3C have been working together to try to formalize the standard, prepare the stable 1.0 release, and get it ready for prime time.
The Netflix-backed Encrypted Media Extensions (EME) proposal, and recent revelations that requirements for DRM in HTML5 are confidential, have generated furor among advocates of the Open Web. Let's cut through the hyperbole.