W3C home > Mailing lists > Public > www-svg@w3.org > June 2010

Re: Minutes, SVG WG Brussels f2f day 4 (Monday)

From: Adam Barth <w3c@adambarth.com>
Date: Tue, 1 Jun 2010 07:50:22 -0700
Message-ID: <AANLkTimqWwr-rbAane_PDSdIH6VklHPvoTgfCvZng_X-@mail.gmail.com>
To: Alex Danilo <alex@abbra.com>
Cc: Henri Sivonen <hsivonen@iki.fi>, robert@ocallahan.org, www-svg@w3.org, Chris Lilley <chris@w3.org>, eric@webkit.org
On Tue, Jun 1, 2010 at 2:58 AM, Alex Danilo <alex@abbra.com> wrote:
> Hi Henri,
> --Original Message--:
>>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.

Treating HTML5 as vaporware until the spec reaches REC is folly.

W.r.t. the specific question of implementing the HTML5 parsing
algorithm in WebKit: Yes, we're implementing it verbatim from the
spec.  It's a lot of work, and we're doing it carefully, but we expect
to get SVG-in-HTML working along the way.  The WebKit implementation
is independent of Firefox's implementation, and all our testing shows
the two are remarkably interoperable for the pieces we've done so far.
 Hooray for the relentless march of progress!


> 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 14:57:09 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:54:26 UTC