SAX: ModSAX addition, general property query

[David Megginson]

MikeDacon at aol.com writes:

 > 1. I still strongly urge not to use a URI for a feature or infoID.
 > These are not resource locations they are just a descriptive
 > string.  In fact, I bet that most parsers just implement your
 > initial recommended set.

Yes, but what about filters that perform specialised actions?  And
what about adding support (stable or experimental) for new XML-related
features like schemas, datatyping, and linking as they become
available?

The problem with SAX 1.0 is that it froze the XML status quo of about
a year ago, and many interesting things have happened since then; with 
ModSAX, I'd like to leave the API open for two reasons:

1. so that we can extend it without breaking existing implementations; 
   and

2. so that people can experiment with different ways of supporting new 
   features within the SAX framework.

As I wrote before, it doesn't much matter whether we use Java property 
names incorporating domain names (like
'org.xml.sax.features.validation') or URIs (like
'http://xml.org/sax/features/validation'), as long as we have the
ability for people to create new names without fear of collision.


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/ and on CD-ROM/ISBN 981-02-3594-1
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)