By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,879 Members | 1,809 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,879 IT Pros & Developers. It's quick & easy.

HTML 5 - the evolving tag soup

P: n/a
As you can see from the W3C main page now, http://www.w3.org , or from the
press release http://www.w3.org/2007/03/html-pressrelease , the Consortium
has decided that HTML 5 is a good idea if they define it.

They want to be "compatible" wth "'classic HTML' parsers", which presumably
means that HTML 5 documents must make sense when rendered by existing tag
soup processors.

They also want all kinds of widgets and gadgets and extras, as outlined at
http://www.w3.org/2007/03/HTML-WG-charter.html

I didn't find anything referring to a semantically richer language, so this
probably won't be another HTML 3. Rather, it'll be HTML 4 extended with
<embed(under a different name), if you see what I mean.

--
Jukka K. Korpela ("Yucca")
http://www.cs.tut.fi/~jkorpela/

Mar 14 '07 #1
Share this Question
Share on Google+
1 Reply


P: n/a
In article <TW******************@reader1.news.saunalahti.fi >,
"Jukka K. Korpela" <jk******@cs.tut.fiwrote:
As you can see from the W3C main page now, http://www.w3.org , or from the
press release http://www.w3.org/2007/03/html-pressrelease , the Consortium
has decided that HTML 5 is a good idea if they define it.

They want to be "compatible" wth "'classic HTML' parsers", which presumably
means that HTML 5 documents must make sense when rendered by existing tag
soup processors.
More to the point, the parsing algorithm for HTML5 should cope with
existing content. HTML5 should degrade reasonably gracefully as well.
They also want all kinds of widgets and gadgets and extras, as outlined at
http://www.w3.org/2007/03/HTML-WG-charter.html

I didn't find anything referring to a semantically richer language, so this
probably won't be another HTML 3. Rather, it'll be HTML 4 extended with
<embed(under a different name), if you see what I mean.
Apple, Opera and Mozilla have proposed that the new HTML WG adopt WHATWG
HTML5 as the starting point.
http://lists.w3.org/Archives/Public/...7Apr/0429.html

--
Henri Sivonen
hs******@iki.fi
http://hsivonen.iki.fi/
Mozilla Web Author FAQ: http://mozilla.org/docs/web-developer/faq.html
Apr 12 '07 #2

This discussion thread is closed

Replies have been disabled for this discussion.