WebSocket, developer tools not yet HTML5-ready
HTML5 has been paired with complementary specifications, such as CSS (Cascading Style Sheets) 3 and WebSocket, for two-way Web communications, in an effort to promote an "open Web." HTML5 is in pretty good shape in terms of the language, but WebSocket capabilities are needed for applications like stock trading and real-time data feeds, Hammond said. "You can do that fine with Flash or Java," but not with HTML5, he said. There's also a security issue: WebSocket implementations have been pulled from current browsers because of concerns over potential screen hijacking, he said.
Developer tools support is also lacking for HTML5, Hammond said. Although there are some HTML-savvy tools available today, there's nothing on the order of a Microsoft Visual Studio or Adobe Dreamweaver, Hammond said.
HTML5's newest target date could slip again
The July 2014 deadline for the final HTML5 standard is not set in stone, Hickson noted. He pointed out that in 2007, the W3C projected a final specification would arrive in 2010, which did not happen.
That lack of certainty may explain why Jacobs is championing use of HTML5 as it is right now. "We're telling people to use it already," he said. "The goal is to get feedback to improve interoperability," he added. That advice contradicts what Philippe Le Hegaret, the W3C interaction domain leader, said last fall, when he cautioned against deploying HTML5 in websites at the time because of the incompleteness of the specification.
This story, "What's still missing in the HTML5 spec," was originally published at InfoWorld.com. Follow the latest developments in programming at InfoWorld.com. For the latest business technology news, follow InfoWorld.com on Twitter.