“HTML5, which updates the HTML specification to accommodate modern Web applications, has gained a lot of adherents in vendors like Microsoft, Google, and Apple,” Paul Krill reports for InfoWorld.
MacDailyNews Take: Paul, in case you missed it, there’s a new world order. Learn it. Know it. Live it: “Apple, Google, Microsoft.” It’s even alphabetical.
Krill continues, “But the specification is plain [sic] not ready yet for deployment to websites, an official with the World Wide Web Consortium (W3C), which oversees HTML5, stressed this week. ‘The problem we’re facing right now is there is already a lot of excitement for HTML5, but it’s a little too early to deploy it because we’re running into interoperability issues,’ including differences between video on devices, said the official, Philippe Le Hegaret, W3C interaction domain leader. He is responsible for specifications like HTML and SVG.”
“Le Hegaret acknowledged HTML5 is viewed as a ‘game changer.’ Companies now can deploy HTML5 in their applications or in intranets where a rendering engine can be controlled, said Le Hegaret,” Krill reports. “But it is a different story on the ‘open Web'” where interoperability is an issue, he added. ‘What’s happening is the industry is realizing that HTML5 is going to be real,’ said Le Hegaret.”
Krill reports, “Apple has positioned HTML5 as a replacement for Adobe’s Flash rich Internet technology. But Flash and similar technologies, such as Microsoft Silverlight, still have a place, Le Hegaret said.”
MacDailyNews Take: What’s that, grinding processors to a halt, providing malware vectors, draining batteries, being proprietary and closed, or something else equally wonderful?
Krill continues, “It will take years before all Web clients support HTML5, he said. He cited Microsoft’s IE6 browser as an example of popular client not supporting the standard. ‘IE6 is still being used on the Web today, and it is 10 years old.’ Over time, however, HTML5 will become the standard for websites, he said. ‘You will see less and less websites using Flash,’ said Le Hegaret.”
“Meanwhile, HTML5 is headed toward final approval in two to three years,” Krill reports. “HTML5 development was begun in 2004 by the Web Hypertext Application Technology Working Group.”
MacDailyNews Take: Fast-tracked. Molasses-like legal proceedings involving blatant patent infringement move faster.
Krill continues, “Digital rights management also is not supported in HTML5, Le Hegarete said. This means some video producers will not deploy their videos in HTML5 without this type of protection, he said. HTML5 is an open standard, presenting a problem for DRM. ‘If we are going to develop a solution for DRM which is open, it would be broken by a hacker within two days,’ he said. ‘There is no point of us doing that.’ There is a possibility for DRM in HTML5 at some point, however, but it is not in the plan at the moment, said Le Hegaret.”
MacDailyNews Take: Yet another reason why Steve Jobs wants videos to use HTML5, not Flash. No DRM means convenience for customers, which means more content sales, which leads directly to more device sales; where the healthy margins are, at least for Apple.
Full article here.
I dont like microsoft, but netflix uses their silverlight technology for their streaming feature and it works great
I dont like microsoft, but netflix uses their silverlight technology for their streaming feature and it works great
One word. PORN. When you see lot’s of porn using HTML 5…game over. The browsers will follow.
One word. PORN. When you see lot’s of porn using HTML 5…game over. The browsers will follow.
Wonder how much Adobe paid this guys to make these comments.
Wonder how much Adobe paid this guys to make these comments.
IE6 is holding up deployment of HTML5? The folks that ares using it, and can’t upgrade to newer version because of hardware limitations shouldn’t be the issue. They can get off the web, get new machines, or upgrade their browsers.
Really, the machines (or users, in some cases) are probably already dead, for all practical purposes. And, newsflash W3C: that’s one of the hallmarks of what we so generically refer to as “technology”. It changes. Fast. Those that don’t change with it are left in the dust.
Kinda like Adobe Flash.
IE6 is holding up deployment of HTML5? The folks that ares using it, and can’t upgrade to newer version because of hardware limitations shouldn’t be the issue. They can get off the web, get new machines, or upgrade their browsers.
Really, the machines (or users, in some cases) are probably already dead, for all practical purposes. And, newsflash W3C: that’s one of the hallmarks of what we so generically refer to as “technology”. It changes. Fast. Those that don’t change with it are left in the dust.
Kinda like Adobe Flash.
Oh, I take that back. Paul Krill is funded by MS. He’s a heavy proponent of Silverlight. SOrry Adobe, but honestly, you still suck too.
Oh, I take that back. Paul Krill is funded by MS. He’s a heavy proponent of Silverlight. SOrry Adobe, but honestly, you still suck too.
@Steve Ballmer
(I never thought I’d tell you this, but) Porn is already making the switch.
Oh, I don’t use the stuff, but consider it my civic duty to keep an eye on technology that affects people’s lives.
@Steve Ballmer
(I never thought I’d tell you this, but) Porn is already making the switch.
Oh, I don’t use the stuff, but consider it my civic duty to keep an eye on technology that affects people’s lives.
I would think that a plug-in that handles DRM would not have to be “open”, just how it connects to the browser should be described. How is DRM currently handled in HTML4 ?
I would think that a plug-in that handles DRM would not have to be “open”, just how it connects to the browser should be described. How is DRM currently handled in HTML4 ?
Attention standards bodies…
No one is listening to you. Instead of writing standards and telling people what to use, document what people do use.
Attention standards bodies…
No one is listening to you. Instead of writing standards and telling people what to use, document what people do use.
“But Flash and similar technologies, such as Microsoft Silverlight, still have a place, Le Hegaret said.”
yeah, in the trash can…
“But Flash and similar technologies, such as Microsoft Silverlight, still have a place, Le Hegaret said.”
yeah, in the trash can…
Internet starts to become a real industry? We are not allowed to make progress because some may be left behind.
Internet starts to become a real industry? We are not allowed to make progress because some may be left behind.
When does M$ stop support of XP and IE6?
When does M$ stop support of XP and IE6?
[sic] fail.
[sic] fail.
His principal argument against HTML5 is handling of video (apparently) and DRM.
Video handling is likely referring to Firefox, where we have Mozilla Foundation refusing to implement rendering of video encoded in codec that isn’t open source. In other words, if you want to embed a video using HTML5 and render it on Firefox, it must use Ogg Theora (about the only open-source video codec). MPEG-4, MPEG-2, AVC, DivX or any such stuff is out of the question, since it requires license for playback, which would require Mozilla to pay millions of dollars per year. Apple, MS, Adobe and others can easily afford it. Mozilla Foundation? Not so easily.
As for DRM, it does NOT have to be closed in order to provide DRM. You can build proper encryption technology on completely open-source model, and it will be as secure (or as vulnerable) as CSS (for DVDs) or AACS (Blu-Ray). There are several open-source DRM initiatives (as counter-intuitive as it may sound).
The above two are NOT real problems. Neither is the issue of Flash and replacing it with HTML5. Real problem is the pace of adoption of the standard.
HTML5 is just still not fully specified, which makes it a moving target for browsers. Safari may claim full HTML5 compatibility, but that full is a very relative term. We simply won’t see much progress, despite the proliferation of iOS (Flash-free) devices, until HTML5 is locked down and ratified as a complete set of specifications.
Hopefully, Apple will forcefully lead the way in locking the specification down and pushing the relevant bodies towards that ratification.