[SVGMobile12] Too many issues

I printed the SVG 1.2 Tiny spec out. It came out at 370 pages. I have so 
far managed to get only as far as page 22 and have already sent over 25 
issues. In doing so I have tried to avoid sending issues that were 
rendundant with other issues already sent to the list.

Drawing those numbers to their logical conclusion, if I were to continue 
reporting issues that I found, I would easily get to three hundred or more 
mostly unique problems. This, again, would be in addition to the hundreds 
of other issues that have been reported by other people.

Many of these issues are fundamental problems, such as lacking clear 
conformance criteria or huge ambiguities in error handling behaviour, 
issues that are obvious on a first reading of the specification.

In short, I do not feel that this specification is even remotely close to 
being ready for last call.

I request that this specification be returned to working draft status, so 
that the working group can more carefully proof-read the specification, 
ensuring that it is internally consistent, that its language is 
appropriate for a specification, that the language be compatible with 
other existing W3C languages, and that, most importantly, it be possible 
to interoperably implement SVG UAs in the context of HTML and CSS UAs that 
behave in the same way for both correct and incorrect content.

I strongly recommend that the next release of the SVG 1.2 Tiny 
specification be normal a working draft, not a last call, so as to set 
expectations at a realistic level.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

Received on Friday, 20 May 2005 14:27:25 UTC