[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: "Elliotte Rusty Harold" <elharo@m...>,<michael.h.kay@n...>, <xml-dev@l...>
• Subject: RE: JAXP's ID Transform failing to include namespacedeclaration attributes
• From: "Evan D. Lenz" <elenz@x...>
• Date: Sat, 5 Jan 2002 11:34:21 -0800
• Cc: <xml-interest@j...>
• Importance: Normal
• In-reply-to: <p04330100b85cfee56f56@[192.168.254.4]>

Elliotte Rusty Harold wrote:
> If it is supposed to be the same effect as an XSLT identity
> transform, then the JAXP spec needs to state this explicitly.

Yes, that would be a good idea. However, since the whole point of a
Transformer is to model an XSLT stylesheet, that seems like the most natural
interpretation. This is a matter of perspective; either way, it should be
more explicit.

Note, however, because of ID attributes, an XSLT identity transformation is
*not* the same thing as preserving everything in the XPath data model! Saxon
seems to take advantage of the underspecification, preserving ID attributes
even though that would never be possible in an XSLT transformation
(unfortunately).

Evan

• Follow-Ups:
  • Re: JAXP's ID Transform failing to includenamespacedeclaration attributes
    • From: David Brownell <david-b@p...>

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

• Prev by Date: RE: JAXP's ID Transform failing to include namespacedeclaration attributes
• Next by Date: Re: JAXP's ID Transform failing to includenamespacedeclaration attributes
• Previous by thread: RE: JAXP's ID Transform failing to include namespacedeclaration attributes
• Next by thread: Re: JAXP's ID Transform failing to includenamespacedeclaration attributes
• Index(es):
  • Date
  • Thread