Why SAX needs namespace support

[david at megginson.com]

Michael.Kay at icl.com writes:

 > Perhaps a setOption(option, flag) interface would be more extensible.

I could live with this, but only if the options were namespace
qualified, i.e.

try {
  parser.setOption("http://xml.org/sax/features/validation", true);
  parser.setOption("http://xml.org/sax/features/namespaces", false);
  parser.setOption("http://xml.org/sax/features/entity-expansion", true);
  parser.setOption("http://simonstl.org/ns/sax/xlink", true);
} catch (SAXUnsupportedFeatureException e) {
  System.err.println("This parser ain't up to snuff -- try another!");
}

Do people like this?  I was almost afraid to suggest it...


All the best,


David

-- 
David Megginson                 david at megginson.com
           http://www.megginson.com/

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)