Hello,
Accidentally sent a post earlier, the admin can disregard.
Anyway, I posted a SR on sf.net some months ago that can be found here:
https://sourceforge.net/tracker/?func=detail&aid=742081&group_id=405...
Anyway, I came away with the impression that lauris didn't much care about the spirit of the W3C documentation and interpreted it to the letter whenever convenient. I didn't bother to argue the fact that the DTD does need to exist, and as mhnoyes points out, the DTD provided by W3C could just as easily be used.
Date: 2003-11-29 11:29 Sender: lauris Logged In: YES user_id=19294
No, DTD does not exist, because nobody wants to maintain it (and unmaintained DTD is much useless). Also, W3C guidelines only say, that xmlns indicator has to be valid URL, not really existing document. Also, there is 'plain-svg' saving option and --export-svg command line option, that should create pure W3C variant. So I move this to feature request category from bugs.
Anyway, I disagree that this is a Feature Request. This is a problem, not a feature I'm looking for. I realize that valid files are created, but the DTD's are part of the process. I and am wondering how this with be addressed with InkScape?
Wendall
On Tue, 2 Mar 2004, Wendall Cada wrote:
Hello,
Accidentally sent a post earlier, the admin can disregard.
Anyway, I posted a SR on sf.net some months ago that can be found here:
https://sourceforge.net/tracker/?func=detail&aid=742081&group_id=405...
Anyway, I came away with the impression that lauris didn't much care about the spirit of the W3C documentation and interpreted it to the letter whenever convenient. I didn't bother to argue the fact that the DTD does need to exist, and as mhnoyes points out, the DTD provided by W3C could just as easily be used.
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?
It might be useful to have an optional extension that did a DTD check of documents on load, so people who want to ensure DTD compliance could make use of that as a filter/check.
Wendall, would you be interested in checking some of the output against the W3C DTD and get a feel for how far off we are from compliance? Also, if you know the ins and outs of DTD making, would you be interested in helping make the DTD for the added svg items? (I think mental could probably itemize what the svg additions in Inkscape are, if you catch him on Jabber).
Bryce
Date: 2003-11-29 11:29 Sender: lauris Logged In: YES user_id=19294
No, DTD does not exist, because nobody wants to maintain it (and unmaintained DTD is much useless). Also, W3C guidelines only say, that xmlns indicator has to be valid URL, not really existing document. Also, there is 'plain-svg' saving option and --export-svg command line option, that should create pure W3C variant. So I move this to feature request category from bugs.
Anyway, I disagree that this is a Feature Request. This is a problem, not a feature I'm looking for. I realize that valid files are created, but the DTD's are part of the process. I and am wondering how this with be addressed with InkScape?
Wendall
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
On Tue, 2004-03-02 at 16:32, 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).
It wouldn't currently, just because we'd need to emit an internal DTD subset as part of our SVG documents describing the extra elements/attributes (in the inkscape or sodipodi namespaces) that we add.
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?
See above.
One of the interesting problems is that DTDs predate the XML namespaces standard, so DTDs and namespaces don't really mix -- DTDs interpret qnames literally, for instance, so you're forced to use the same prefixes throughout as are used in the DTD.
I'm not really sure what the best solution to that is.
-mental
participants (4)
-
Bob Jamison -
Bryce Harrington -
MenTaLguY -
Wendall Cada