Next Round

[Don Park]

David,


>I'd like to lose EntityResolver and DTDHandler (who uses them?), but I
>don't know if we can.


I don't recommend this.  People are using it.

>1. Filter Interface


I agree with James that DocumentHandler is the appropriate place.

>2. Lexical Event Handler


Looks good.

>Of course, we need a new parser interface that knows about lexical
>handlers:


Or we could just redefine setDocumentHandler so that LexicalHandler is
automatically set if the given DocumentHandler implementation also
implements that interface.  The two interfaces are strongly related after
all.

>3. Namespace Support


How about  this?

public interface NamespaceHandler {
    public void startNamespace(Namespace ns);
    public void endNamespace();
}

public interface Namespace {
    public String getPrefix(String qname);
    public String getURI(String qname);
}

Namespace implemention is responsible for keeping track of inheritance.
Again, we can use setDocumentHandler to automatically check for
NamespaceHandler implementation.

For efficiency sake, we might also require that if NamespaceHandler is
supported then all names (tag name, attribute name, namespace prefix and
URI) should be 'interned'.

Best,

Don Park
Docuverse



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/
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)