SAX: ModSAX addition, general property query

John Wilson tug at
Tue Mar 9 10:43:27 GMT 1999

----- Original Message -----
From: Kay Michael <Michael.Kay at>
To: XML Developers' List <xml-dev at>
Sent: 09 March 1999 09:54
Subject: RE: SAX: ModSAX addition, general property query

>> I've been thinking about this issue, and I'm fairly convinced
>> that the URI is the right choice.
>> Think of the URI a statement of ownership.  Assume that my ISP is
>>, and that I've been allocated 5MB of web space at
>I don't often disagree with David, but I think this is quite misguided.

I agree - I don't actually see the benefit of using a string identifier at

I don't think that it's unreasonable to insist that objects representing a
Feature, Handler or Property should either implement a distinct interface or
subclass a distinct class. If this is so the Parser can tell what Feature,
Handler or Property is being set by enquiring of the type of the object. (I
favour insisting that they subclass distinct classes because (in Java) that
naturally imposes the restriction that a single object can only represent a
single Property.)

The get() member function could take a Class parameter.

The advantage of this approach is that it relies only on the type naming
scheme of Java and there are already well established mechanisms that
ensures that different implementers create distinct types.

I am by no means an expert in the other languages that are supported by
SAX - would this approach cause dreadful problems in other languages?

John Wilson
The Wilson Partnership
5 Market Hill, Whitchurch, Aylesbury, Bucks HP22 4JB, UK
+44 1296 641072, +44 976 611010(mobile), +44 1296 641874(fax)
Mailto: tug at

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at
Archived as: and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo at the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at

More information about the Xml-dev mailing list