Bryce Harrington wrote:
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).
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?
Yes, it would be good to use XML namespaces for this. One for the base SVG spec, then maybe others for SP and Inkscape.
The XML reading code needs to be able to handle namespaces. One of the purposes of an SVG document is for it to be embedded in other XML documents to provide images. This is ---especially--- true of XHTML.
<?xml version="1.0"?> <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"> <svg xmlns:sodipodi="http://wherever/sp/DTD/located" xmlns:inkscape="http://wherever/inkscape/DTD/located"
<!-- now you can insert sodipodi and inkscape nodes without interfering with normal SVG -->
sodipodi:stuff </sodipodi:stuff> inkscape:stuff </inkscape:stuff>
.....blah.....
</svg>
Bob