Altova Mailing List Archives


From: "Chris Barber" <chris@----------.--.--.------>
Date: 7/17/2003 12:21:00 AM
A very quick read of an XML / XSL book when I started and I've never managed
to get the difference wrong. Semantics aside, I think its accurately named.
Bear in mind that xsl:copy can act on attributes individually as well as
nodes so naming it xsl:copy-node would be incorrect.
Just me though so feel free to ignore.


"Mark Johnson" <102334.12@c...> wrote in message
> "Chris Barber" <chris@b...> wrote:
> >Sorry - what was the question again - you seem to have answered it
> >Is xsl:copy not doing something that you feel it should in a specific
> Good question. I just wondered that - copy-of - was perhaps misnamed,
> or even, copy. Copy doesn't imply that the copy is immediately used,
> then, by passing to the output thread. It implies it's held for some
> purpose. But . . . at any rate, if aliases were allowed, I suppose
> that I, myself, would use them for these. I suppose, even better,
> would be a pre-proc layer on top of the xslt, another language, which
> could present more meaningful names. I don't know. Probably isn't any
> big deal.


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.