• From: James Clark <jjc@j...>
• To: david@m...
• Date: Sun, 24 Jan 1999 09:57:22 +0700

david@m... wrote:

>   public interface NamespaceParser
>   {
>     public void enableNamespaceProcessing (boolean flag);
>     public void setSeparator (String sep);
>   }

This looks good, but I don't see the need for two functions. Just

 void setNamespaceSeparator(String sep);

seems to me to be enough: null means disable namespace processing (the
default); non-null means expand names using the specified separator.

However, I wonder whether it's really a good idea to allow apps to
choose the separator. It makes it harder to chain together SAX processes
using things like the Filter.  If one DocumentHandler expects names
separated by # and another expects them separated by !, then they can't
work together without some additional glue. I think consideration should
be given to mandating a specific separator character. It's not obvious
to me what the right answer is here.

James



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

• Follow-Ups:
  • Re: SAX: Next Round (Namespace support)
    • From: John Cowan <cowan@l...>

• References:
  • SAX: Next Round
    • From: <david@m...>

• Prev by Date: Re: Are PI targets arbitrary?
• Next by Date: Re: SAX: Next Round
• Previous by thread: the "upwards funarg" problem.
• Next by thread: Re: SAX: Next Round (Namespace support)
• Index(es):
  • Date
  • Thread