- From: Alex Danilo <alex@abbra.com>
- Date: Tue, 01 Jun 2010 19:58:54 +1000
- To: Henri Sivonen <hsivonen@iki.fi>
- Cc: robert@ocallahan.org, www-svg@w3.org, Henri Sivonen <hsivonen@iki.fi>, Chris Lilley <chris@w3.org>, abarth@webkit.org, eric@webkit.org
Hi Henri, --Original Message--: ><snip/> >In any case, whatever incompleteness there might be is so small that it doesn't make any sense at all not to treat HTML5 as completely SVG-relevant as-is right now. You can see that http://wiki.whatwg.org/wiki/ParserIssues is pretty short. I realize that REC might be a bit further away, but it would be folly for the SVG WG to treat HTML5 as vaporware until it's "done" from the Process perspective. Just to clairfy my comment so you don't assume something sinister about the WG and put the comment into perspective. It was my comment, not the WG. HTML5 is vapourware _until_ the spec. reaches recommendation status. The press keep going on and on about HTML5 and how it's the great new thing. But it is a _work in progress_. Yes, features from HTML5 have made it into some new browser builds, but there are no browsers that implement the entire HTML5 working draft now. When it gets finalised then features will get added and dropped. So IMHO it fits the description of vapourware until someone actually implements all of the parts of a very comprehensive and complex spec. Implementing a subset does not qualify as having implemented HTML5 despite what the nerd press would have you believe. Alex
Received on Tuesday, 1 June 2010 09:59:56 UTC