Tim Oreilly of OReilly Books has written a piece on the bet that Google is making on HTML5. This is a good introduction a)to some of the key features of HTML5 and b)where they stand in terms of implementation by the key players in the browser and smartphone community. Here are some of those key features of HTML5:
1)Structuring is enhanced with <header>, <footer>, <section>, <aside> and other meaningful tags which have nesting and interelationship rules;
2)<video> and <audio> tags break the dependence on Flash or QuickTime player for adding your own sizing controls and basic behaviours to video and audio embeds;
3)DOM revisions place all the tags on the DOM tree and in a uniform manner including addressing elements/tags. This, when implemented, eliminates browser differences and developer headaches;
4)XForms 2 updates features and options to forms elements that have not changed in 12 years;
5)Several new tags to accomodate new Web 2.0 capabilities:
markrepresents a run of marked text.
meterrepresents a measurement, such as disk usage.
progressrepresents a completion of a task, such as downloading or when performing a series of expensive operations.
timerepresents a date and/or time.
canvasis used for rendering dynamic bitmap graphics on the fly, such as graphs or games.
commandrepresents a command the user can invoke.
datagridrepresents an interactive representation of a tree, list or tabular data.
detailsrepresents additional information or controls which the user can obtain on demand.
datalisttogether with the a new
inputis used to make comboboxes:
keygenrepresents control for key pair generation.
eventsourceis used to set up a persistent connection with a server of which messages (events) can be received.
bbrepresents a user agent command that the user can invoke.
outputrepresents some type of output, such as from a calculation done through scripting.
rpallow for marking up ruby annotations
My question is an Obama-like one – why treat the Web standards breaker so tactfully? Their IE Web browser monopoly is going the way of the dodos. Why not demand more of Redmond [like rigid schedules/commitments to CSS 2.x + 3, DOM, E4X, and other longstanding Web standards adherence] ?? Or is it to the other browser vendors advantage to just let Microsoft slide – quickening the demise of IE8 and Redmond as a major Web+Mobile player?