[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: <michael.h.kay@n...>, <xml-dev@l...>
• Subject: RE: JAXP's ID Transform failing to include namespacedeclaration attributes
• From: Elliotte Rusty Harold <elharo@m...>
• Date: Sat, 5 Jan 2002 14:14:19 -0500
• Cc: <xml-interest@j...>
• In-reply-to: <001601c19615$5c41cba0$465169d5@pcukmka>
• References: <001601c19615$5c41cba0$465169d5@pcukmka>

At 6:18 PM +0000 1/5/02, Michael Kay wrote:


>I certainly wouldn't expect the namespace declaration to be lost. If Saxon
>is losing it, it's because the namespace declaration isn't present in the
>DOM in the form Saxon expects. There seem to be 57 varieties of ways that
>namespaces may or may not be represented in a DOM, and Saxon often has
>trouble with DOM input for this reason. I don't think your message actually
>said which DOM implementation you were using: in my experience, they are all
>different.
>

I've tried it with Crimson, Xerces-J 1.4.3, and GnuJAXP. The problem 
is present in the first two. GNU JAXP has another bug that cancels 
out this bug so it actually works. :-)

>I would expect the DOCTYPE declaration to be lost. Saxon is basically doing
>an identity transformation according to the XPath data model. If information
>isn't present in the XPath data model, then it's lost during an identity
>transformation.

I guess my question here is whether we can say that this indeed an 
XSLT transform according to the XPath data model? I don't see 
anything in the JAXP spec that actually says that. What it does say 
is:

If all that is desired is the simple identity transformation of a 
source to a result, then
TransformerFactory 90 provides a newTransformer()93 method with
no arguments. This method creates a Transformer that effectively 
copies the source
to the result. This method may be used to create a DOM from SAX events or to
create an XML or HTML stream from a DOM or SAX events.

If it is supposed to be the same effect as an XSLT identity 
transform, then the JAXP spec needs to state this explicitly.
-- 

+-----------------------+------------------------+-------------------+
| Elliotte Rusty Harold | elharo@m... | Writer/Programmer |
+-----------------------+------------------------+-------------------+
|          The XML Bible, 2nd Edition (Hungry Minds, 2001)           |
|              http://www.ibiblio.org/xml/books/bible2/              |
|   http://www.amazon.com/exec/obidos/ISBN=0764547607/cafeaulaitA/   |
+----------------------------------+---------------------------------+
|  Read Cafe au Lait for Java News:  http://www.cafeaulait.org/      |
|  Read Cafe con Leche for XML News: http://www.ibiblio.org/xml/     |
+----------------------------------+---------------------------------+

• Follow-Ups:
  • RE: JAXP's ID Transform failing to include namespace declaration attributes
    • From: "Michael Kay" <michael.h.kay@n...>
  • RE: JAXP's ID Transform failing to include namespacedeclaration attributes
    • From: "Evan D. Lenz" <elenz@x...>

• References:
  • RE: JAXP's ID Transform failing to include namespace declaration attributes
    • From: "Michael Kay" <michael.h.kay@n...>

• Prev by Date: ANNOUNCE: XPipe 0.2
• Next by Date: RE: JAXP's ID Transform failing to include namespacedeclaration attributes
• 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