OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: SAX 2.0 Enhancement proposal (2nd Ed)

Rob Lugt wrote:

> The weight of opinion then is on the side of change.  The
> proposal for a new
> interface in the next version of SAX (SAX 3.0?) remains unmodified so I
> propose it goes onto the 'list of proposed enhancements' that I presume
> David Megginson has tucked away somewhere to be resurrected when SAX
> eventually goes to its new home.

To be clear, I don't think that this feature warrants a change to the
current SAX interfaces which would result in SAX 3.0. I consider James
Clarks' suggestion a perfectly good solution to the issue using the current
SAX interfaces.

> The proposal for a bug-fix to SAX 2.0 needs modification along
> the lines of
> James Clark's suggestion.

I would not call this a bug fix, rather a request for a new standard feature
(and property). The current interface works as documented. That said, I
wholeheartedly agree that this is a good feature and property to have.

> 2) In order to furnish the application with the base URI of the entity
> containing the ENTITY declaration, I would like your opinion on a choice
> between:-

> b) A new standard property: http://xml.org/sax/properties/baseURI.  This
> property will contain the baseURI as described in (a) above.

This is actually an important property to have, and is one of the (few)
missing information items of the XML Infoset that SAX fails to provide. I
think we need _both_ but I am more interested in the base URI property than
the standard feature.

 The value of
> this property will only be valid during the invocation of a
> resolveEntity()
> call.

This property should be valid at all times. When the base URI is
unknown/undefined the value can be null.