The World Wide Web Consortium (W3C), the official governing body that oversees HTML5, warned the Web community that HTML5 is not a ratified standard and that implementing it too soon is not wise.
"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," said Philippe Le Hegaret, W3C interaction domain leader.
The earliest date that was floated around for HTML5 is early 2012. If you're really going into HTML5, just be prepared that you may need to change it again in 2 years time as the battle may go anywhere now. Not only is Ogg fighting against H264, Google has also complicated the landscape (again) by introducing WebP, a method of lossy compression that can be used on photographic images.
Things will most probably change closer to 2012. They always do. Is it wise to implement HTML5 now? If your target audience are the iPad, iPhone and Android users, maybe. Your code will just be a whole lot more complicated and if you're using video, you'll need to provide both ogg and H264 videos to ensure usability across browsers. You can take a look at my post here on how to use HTML5 for videos.
No comments:
Post a Comment