This is nothing more than some corporate politics at play. This has
nothing to do with the issues over browse mode. What this means is
that the next generation of browsers will not be able to include the
little graphic that says they are HTML5 compliant since the standard
is still technically not finalized. What is important for
screenreader development is which current iteration will be supported
by the major browsers. This will be set regardless of the little
graphic and the official seal of finality. The move of certification
puts it way past the expected release date of the next major release
of the major browsers. It is entirely possible that IE 10 and Firefox
5 will not be able to have the certification either.
The final version of HTML5 which may or may not be set by the time IE
10 and Firefox 5 along with the next major version of the other
browsers come out isn't likely to be all that different, and if it
is, GW Micro will by then know what is coming and will be able to
develop for it just as they are able to develop for what is coming in
IE 9 and Firefox 4 regardless of a standards group tweaking the noses
of the smaller group formed by corporations left out of the bigger
group. There are a whole host of reasons for a standards group like
this to drag their feet, particularly when there are major players
like Apple that are not a part of the organization. Once the standard
is set and done, the group might as well be dissolved, all of the
importance will be set on the group developing the next standard and
which individuals and corporations have the most influence will shift
and change. So, if you are among the leaders of the current group,
why not drag it out as long as you possibly can? Browser and site
developers will continue to use the unofficial standard, changes can
be implemented fluidly and with little disruption, and you get to
keep your place in the influence totem pole while excluding your
competitors that aren't in the current group. This is why there has
been a surge of support from many quarters to start a new standards
group, drop the numbered version system, just calling the standard
HTML and allowing it to evolve with the new group simply overseeing
the adoption of new additions and changes and certification would be
by date of last major update or by which features within the standard
are supported. I don't know how well that would work, politics would
still play in no matter what they do.
Regards,
Chris
At 09:31 AM 2/19/2011, Sam bushman wrote:
Hi all,
this is an FYI for those who believe the web standards for html 5 are set:
CNet:
HTML5 spec set for 2014 completion
The W3C sets a date for when it expects to finalize the next-gen Web
page language, but it's tough to reconcile the pace of
standardization with the pace of Web technology development.
Thanks,
Sam
If you reply to this message it will be delivered to the original sender only.
If your reply would benefit others on the list and your message is related to
GW Micro, then please consider sending your message to [email protected] so
the entire list will receive it.
GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage
your list subscription at http://www.gwmicro.com/listserv.
