@ks2problema Apple was the one who pushed for the concept of HTML5 in the first place instead of XHTML and created the consortium of independent browser makers (WHATWG) like Mozilla and Opera to push for modern HTML5, CSS3, and AJAX. There is nothing proprietary about Apple's push, it is all done within the purview of the W3C. It is official W3C policy to encourage browsermakers to experiment with proposed standards using temporary proprietary CSS exensions until a proposal has been agreed upon, which usually takes years; in the case of Firefox, it's 'moz-'. Are you going to rail against them and Opera too? Apple has not added ANY proprietary tags to HTML5. Considering that HTML5 may not reach recommendation status until 2022 or later, and CSS3 is not expected to be ratified for some time, that is just as well. That said, Apple do have a more immediate vision of what they want to accomplish with HTML5 and CSS3, so they do put proposals forward to the W3C and implement them in WebKit before they are approved. Once they are ratified, the 'webkit-' extension is removed from the CSS, the same as what Mozilla and Opera does. That, as mentioned, is the officially-sanctioned way of the W3C. All the proposals Apple have devised with Mozilla and Opera has been put forward for consideration by the W3C in the form of HTML5, nothing is kept proprietary. WebKit itself is an opensource project, everything in it is free in terms of freedom as well as in beer. Kudos to Apple for going the Standards route as they have a longstanding record of doing, and in this case as well as numerous others, the Opensource route. Apple has opensourced numerous major projects like Clang or released specs to Standards bodies or everyone to use freely. The only controversy in regards to HTML5 is the standard for the Video tag; Apple and Microsoft want to standardise in the MPEG4 standard, Mozilla and Opera want Ogg. Google is supporting both, and has now put forward their own proposal in the form of WebM. I see the logic in both positions, and I believe both H264 and WebM should be sanctioned for video, and AAC and Ogg for audio. Theora was never a good alternative technically.
So I frankly don't know what you are babbling about.
The best of ZDNet, delivered
ZDNet Newsletters
Get the best of ZDNet delivered straight to your inbox
