[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: JAXP's ID Transform failing to include namespacedeclaratio

• To: xml-dev@l...
• Subject: Re: JAXP's ID Transform failing to include namespacedeclaration attributes
• From: Mike Champion <mc@x...>
• Date: Tue, 08 Jan 2002 09:54:31 -0500
• In-reply-to: <p04330100b860a7756adf@[192.168.254.4]>

1/8/2002 8:48:31 AM, Elliotte Rusty Harold <elharo@m...> wrote:

>My personal opinion? Throw out the requirement for DOM N-1 
>compatibility. Then throw out IDL, and define separate APIs for each 
>language of interest.
>
>Of course, if the W3C doesn't do this, others will, 

I pretty much agree, although I'd suggest that the deeper
you dig, the messier it will get even if you relax these constraints.  In particular
the problem of defining the "right" behavior when a namespace-aware nodes
are added, deleted, and moved is harder than it looks on the surface.  SAX2 and
XPath have more elegant models for namespaces in part because these
are read-only. I haven't looked closely enough at JDOM or dom4j to see if they
have any brigher ideas on how to handle this than DOM does.

At some point this all needs to get refactored, but that is going to be disruptive.

• References:
  • Re: JAXP's ID Transform failing to include namespace declaration attributes
    • From: Elliotte Rusty Harold <elharo@m...>

• Prev by Date: Re: JAXP's ID Transform failing to include namespace declaration attributes
• Next by Date: Aelfred for C++
• Previous by thread: Re: JAXP's ID Transform failing to include namespace declaration attributes
• Next by thread: Re: JAXP's ID Transform failing to include namespacedeclaration attributes
• Index(es):
  • Date
  • Thread