Oops,
my gripe was actually not about the namespace of NS nodes
issue, but about the use of the empty string instead of
null, for "no value" of the namespaceURI and qName args
... but it's equivalent, a desired change that is resisted
by the (entirely reasonable) inertia of an open API spec.
Another issue is de facto compliance ... are most drivers
complying already, or would the API change perhaps just
be breaking about as many as are already broken? I dunno,
just speculating! SAX is itself a de facto standard, so
de facto compliance should probably be a consideration in
the cost estimate.
In the present state of affairs we'll all end up writing
our apps to check both cases for robustness, I guess.
That's a small but permanent cost, whereas the API change
would be a larger but one-time cost.
OK, enough one-and-a-half cents from me! :)
Cheers,
- Gulli
> -----Original Message-----
> From: Gunnlaugur Thor Briem [mailto:[EMAIL PROTECTED]]
> Sent: 27. november 2001 19:13
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: RE: [Sax-devel] Re: SAX and namespace attributes
>
>
> Hi,
>
> I may be taking a naive view here, so please excuse
> me if I'm making you roll your eyes, but isn't this
> just the kind of thing API versioning is for? If SAX2
... [snip]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
