Nmap Development mailing list archives
Re: Hard-coded xmloutputversion in nmap.dtd--remove it?
From: Kris Katterjohn <katterjohn () gmail com>
Date: Fri, 15 Aug 2008 14:08:50 -0500
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 David Fifield wrote:
On Fri, Aug 15, 2008 at 12:17:46PM -0500, Kris Katterjohn wrote:Finally, what does every use xmloutputversion for? I notice that the parser in Zenmap never uses it. Is validity (in an XML sense) important to your application? Zenmap's USR files are remarkably invalid yet they get the point across. It could be that xmloutputversion isn't worth much fuss.So while my answer to this is pretty much "meh", I think that's a good enough answer for an opinion on this matter since it means there's no fuss :) Of course this does mean I'll need to update my library again for another change...Unless I'm mistaken, this shouldn't require changing any parsers, it should be fully backward-compatible. Instead of saying, "xmloutputversion has to be '1.02'," we'll say, "xmloutputversion is any string," and of course "1.02" will continue to be valid. If we ever do make a backward-incompatible change to the XML output, like removing a requried element or changing the structure of an element, then we could create a new DTD that would live with the current one in parallel.
Ah, yes, this indeed sounds OK. I had only skimmed your proposal (since I still don't care either way), and misread it in the process.
David Fifield
Thanks, Kris Katterjohn -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIVAwUBSKXUO/9K37xXYl36AQIIaA//R0xQNlQ+IAbilbNJ8YWeEOkTc+4klboG 69OuVfFYC60Po+bs8pn0xaqwurIOGVEWKBL7E20IxX3SoPYBpLCtbvnCKLa8VQa+ xim1o7kkFS0ZaHaMfudOG9nabk4O6pwe+gGa55U7LLEV4rpd1OqnriYlbUNgX9/h lO/BJA4d7+k+yMJ02iw78oMx8YGVmiGttbyTW3dmokGJ4i3fQI5QGs7hGh9fUzBF 7ZZbCIKYDzSHyY67Bl8KViOGsiDOzeirK/nLGBjz2il2YmLMvixV5okZVaa2GVbz wFKH+LH/YYDofsqQqcY3vSXM0JXJMzaltGEMK/r0LMBzy2JkcfrXhyrjE+Qznzdx O/nbZOv6Ik1UkhuTrd14NIg+oXbGo4ze3cwV7mHXzlktQaa2E7Bvbii+ejSw9pkx 7jzgYqWzbNiNwtpIpHwp11l8n2JMaPDKxPOqz9Tc/fi2RkPbqiHmJ7SfE2KoBIiG lCqCZ6srqacvwwS8PCtMWIfpE9lQlaE8zzeRgj+KCfTdzsIF0R9ago2ndu0InjP6 49WNwUmO4sc/n5tjOpu3KIhA+K2biocsEgngNK3fn/rgmvDI4Cr+IMaYsC1MHbj8 +GlSzAXtMM/kV+Px7M8E0nVj65JwuoXo363Z/7CPdxOQ3s940BtrDJCaitCPsejF 3lUALx4J6PM= =sh9b -----END PGP SIGNATURE----- _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org
Current thread:
- Hard-coded xmloutputversion in nmap.dtd--remove it? David Fifield (Aug 15)
- Re: Hard-coded xmloutputversion in nmap.dtd--remove it? Kris Katterjohn (Aug 15)
- Re: Hard-coded xmloutputversion in nmap.dtd--remove it? David Fifield (Aug 15)
- Re: Hard-coded xmloutputversion in nmap.dtd--remove it? Kris Katterjohn (Aug 15)
- Re: Hard-coded xmloutputversion in nmap.dtd--remove it? David Fifield (Aug 15)
- Re: Hard-coded xmloutputversion in nmap.dtd--remove it? Michael Pattrick (Aug 15)
- Re: Hard-coded xmloutputversion in nmap.dtd--remove it? Kris Katterjohn (Aug 15)