Re: Minutes, 22 April 2010 SVG WG meweting

Doug Schepers:
> Hi, Dr. Olaf-
>
> I think it would be a good idea to get rather more precise on these
> points in SVG 2.0.  

Of course, there are several open issues, partly explicitly mentioned
in tiny 1.2, that have to be solved somehow...

> For SVG 1.1 SE, I personally want to simply finish 
> it, and work with browser vendors, other implementers, and folks like
> you to define things like this with better detail and more
> interoperability for SVG 2.0.
>
> To some extent, making SVG 1.1 more precise risks making existing UAs
> unconforming, which is less of a concern for SVG 2.0.

For several problematic cases I think, there is no real problem with the
current specifications. Those issues are already defined, but several/many 
implementations fail - this is a hint, that some (informative) text might help
implementors a lot to get it right now. Of course this does not change 
SVG 1.1 itself and it does not change bugs in already published versions 
of viewers.
Because there will be typically several versions, until SVG 2.0 becomes
a recommendation, such bugs will typically persist for years or several
versions of some viewers, if there is no hint, maybe just due to a
minor problem with the mathematical skills of the programmer.
With some hints (and bug reports) I think, several of those bugs
can be fixed.

And until those bugs are fixed in the majority of viewers, 
several nice features of SVG remain unusable for most authors.
If this happens already for basic paths, there is often no 
workaround possible with the result, that people will argue, that
SVG is still not ready for use today and one has to wait for 
proper SVG 2.0 or SVG 3.0 viewers.

>
> As far as adding the link you suggest, I don't see any harm in that.

Sounds good...


Olaf

Received on Monday, 26 April 2010 09:00:19 UTC