RE: [xsl] Creating namespace nodes

[<tomas.vanek@xxxxxxxxxxxxx>]

Thanks for clarification.

The last point is querying with namespaces, if we have qualified names
in the attribute.
See http://www-106.ibm.com/developerworks/library/ws-trans/?dwzone=ws,
this paragaph:

Next comes the transport that uses the binding-uri variable, and that in
turn uses binding-local-name. Both of these variables are defined right
inside the xsl:for-each. In the binding-local-name definition you can
see what I meant about the problem with qualified names in the
attribute. To match the contents of the port's binding attribute against
the corresponding WSDL binding element, we must strip away the namespace
prefix, as accomplished by the substring-after() function.

tomi


-----Original Message-----
From: David Carlisle [mailto:davidc@xxxxxxxxx]
Sent: Tuesday, June 07, 2005 1:05 PM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [xsl] Creating namespace nodes

  Do not expect miracles!
  The result will be the same - you add a dummy attribute with desired
  namespace to your element and so you force the XSLT engine to add the
  namespace. In XSLT 1.0 you have hard time to play with namespaces
nicely
  :-(


The namespace is apparently fixed at the time that the stylesheet is
written so there is no problem generating the required namespace node in
XSLT1. XSLT1 can copy namespace nodes from the source or the stylesheet
and can dynamically generate nodes required for elements or attributes
in a particular namespace.

  Are this issues addressed in XSLT 2.0 (adding namespace nodes to
  elements)?

The only feature that XSLT1  lacks is the ability to dynamically
genearte a namespace node for a namespace that does not appear in the
source or stylesheet and is not the namespace of any element or
attribute at that point in the result. In order to cater for this
requiremnt in XSLT1 you have to use an x:node-set() extension function
to first create a temporary source tree which has the namespace, and
then copy  the namespace node. In xslt2 there is an xsl;namespace
element taht allows the namespace node to be constructed directly.


  I had to kick-off all the namespaces staff (using
  local-name() function in all Xpath queries :-(

This appears to be an unrelated issue, querying documents using
namespaces, rather than generating them, (unless I misunderstand??)


David

________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The service is
powered by MessageLabs. For more information on a proactive anti-virus
service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________



This message is for the designated recipient only and may contain privileged,
proprietary, or otherwise private information.  If you have received it in
error, please notify the sender immediately and delete the original.  Any
other use of the email by you is prohibited.