Good idea. For Inkscape we listed 'full SVG compliance' as one of our core missions & goals, so the DTD is extremely important. I don't know if Inkscape's output passes the W3C DTD, but if it doesn't then those items should probably be treated as critical bugs (as bad as crash bugs).

No it does not pass W3C DTD, and it will never be able to, simply because DTDs are not namespace-aware. In a DTD, you cannot say "pay no attention to anything outside svg namespace". DTDs are an extremely old and inflexible technology. The best we can do about it is ignore it.

We've also talked about having a DTD for the SVG additions. This is definitely something that should be written and included with the Inkscape package - wouldn't hurt to include the W3C SVG DTD too, for completeness. Maybe we should have a share/dtd/ directory?

Any schemas are useful when you have different suppliers and different consumers of information using a shared format. In our case, we have one supplier (Inkscape) and one consumer (Inkscape), so I don't see much use for a DTD or schema. When people will begin generating Inkscape SVG documents by scripts, or do some meaningful things to them outside of Inkscape, then a shema will be more useful. Right now it's ultimately Inkscape itself that defines what is "valid" and what not. Also, the inkscape: additions are very much in a flux, new ones are added often, and we still don't have a big enough body of SVG documents in Inkscape format.

_________________________________________________________________ Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2f...