worldwidewebconsortium
Latest
W3C completes HTML5 definition, starts interoperability testing
Long heralded as the darling of the open web, the standards for HTML5 haven't actually been finalized by the W3C -- it was just recently that the international consortium pledged to get it done by 2014. So it's good to hear the group just hit a significant milestone on the road to that goal by publishing the full definition for the spec this Tuesday. With that accomplished, the next step is interoperability and performance testing to make sure HTML5 plays nice with any and all browsers, servers and other web tools. The W3C hopes that this will bring "broad HTML 5 interoperability" by 2014, which fits right in to the organization's philosophy of bringing the entirety of the web -- however divisive -- together.
W3C teams with Apple, Google, Mozilla on WebPlatform, a guide to building the open web (video)
The World Wide Web Consortium might just be the United Nations of web development, as it's bringing together some frequent enemies to fight for a common cause through WebPlatform.org. The collaboration will see Adobe, Apple, Facebook, Google, HP, Microsoft, Mozilla, Nokia and Opera pool educational resources to create a comprehensive, frequently updated guide to creating HTML5 and other content for the open web. The companies' instructional oversight is just the start, however -- visitors will have chats and forums to devise their own solutions, and they'll even have a better than usual chance at influencing mid-development web standards. It may be some time before we'll see the first fruits of the organization's work, but we're already happy to see technology companies set aside some of their differences.
W3C says HTML 5 will be finalized in 2014, HTML 5.1 to follow in 2016
HTML 5 has been a buzz word around the interwebs for so long you'd be forgiven if you thought it was a well-established standard looking for a successor. In fact, nothing could be farther from the truth. The World Wide Web Consortium (W3C), which helps establish the primary standards used online, didn't actually intend to complete HTML 5 until 2022. Thankfully, the group has reconsidered that seemingly absurd timeline and now plans to have this whole mess wrapped up by the end of 2014. The revised plan calls for an HTML 5 Candidate Recommendation (sort of like a feature-frozen beta) to be submitted by the end of 2012, before being finalized in 2014. All existing bits of the standard that are unstable or that suffer interoperability problems will be pulled from that candidate and pushed to a draft version of HTML 5.1. While HTML 5 is being completed, its evolutionary successor will begin the process of marching towards standardization, with a target completion date of 2016. For a more detailed exploration of the future of HTML hit up the source link.
Microsoft no fan of existing WebRTC standard, proposes its own to get Skype onboard
Microsoft, objecting to a web standard promoted by its competitors? Get out. While Firefox, Opera and now Chrome have implemented WebRTC on some level for plugin-free VoIP and webcam chats, Microsoft doesn't think the existing, proposed standard is up to snuff for linking with existing devices or obeying "key web tenets." It's suggesting a new CU-RTC-Web standard to fix what it claims is broken with WebRTC. Thankfully, the changes are more technical improvements than political maneuvering: Microsoft wants a peer-to-peer transport level that gives more control as well as to reduce some of the requirements that it sees holding the technology back as of today. There's no doubt an economic incentive for a company that wants to push Skype in the browser, but the format is already in front of the W3C and could become a real cross-platform standard. If other W3C members are willing to (slightly) reinvent the wheel, Microsoft's approach could get Chrome and Internet Explorer users talking -- no, really talking.
Google, Microsoft and Netflix want DRM-like encryption in HTML5
HTML5 is supposed to set the web free. Free to deliver and shape online media in any web browser. However, several of the standard's greatest champions want to be able to restrict the use of audio and video tags through encrypted media extensions. A draft proposal has been submitted by Google, Microsoft, and Netflix to the W3C -- the curators of HTML5 -- to add encrypted media extensions to the web standard's spec. The proposed system works using a key-based content decryption system controlled by applications, thusly providing the copy protection that so many content owners desire. Naturally, the proposal specifically states that "no DRM is added to the HTML5 specification" if it's adopted, but letting apps lock up audio and video content sure sounds like digital rights management to us. However, there's already some discord amongst the W3C's members as to whether the proposal will work as promised, so its addition to HTML5 is far from assured. You can read the full proposal at the source below, and check out the more coverage links for some added perspective. and tags through encrypted media extensions. A draft proposal has been submitted by Google, Microsoft, and Netflix to the W3C -- the curators of HTML5 -- to add encrypted media extensions to the web standard's spec. The proposed system works using a key-based content decryption system controlled by applications, thusly providing the copy protection that so many content owners desire. Naturally, the proposal specifically states that "no DRM is added to the HTML5 specification" if it's adopted, but letting apps lock up audio and video content sure sounds like digital rights management to us. However, there's already some dischord amongst the W3C's members as to whether the proposal will work as promised, so its addition to HTML5 is far from assured. You can read the full proposal at the source below, and check out the more coverage links for some added perspective on the proposal.
