This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: Carrying Namespaces through a XSL to XSL Transformation
- To: "'xsl-list at lists dot mulberrytech dot com'" <xsl-list at lists dot mulberrytech dot com>
- Subject: RE: [xsl] Carrying Namespaces through a XSL to XSL Transformation
- From: "Smith, Chad" <chadsm at mitre dot org>
- Date: Wed, 27 Dec 2000 13:56:36 -0500
- Reply-To: xsl-list at lists dot mulberrytech dot com
Nevermind - stupid question ;)
> -----Original Message-----
> From: Smith, Chad [mailto:chadsm@mitre.org]
> Sent: Wednesday, December 27, 2000 1:47 PM
> To: 'xsl-list@lists.mulberrytech.com'
> Subject: RE: [xsl] Carrying Namespaces through a XSL to XSL
> Transformation
>
>
> Kevin:
>
> Do you by chance have the matching template to close
> this tag? I'm
> afraid I don't know the escape sequence for the '/'
> character. Other than
> that, this seems to be working perfectly - thanks much!
>
> CS
>
> > -----Original Message-----
> > From: Kevin McCarthy [mailto:Kevin@McCarthy.net]
> > Sent: Wednesday, December 27, 2000 1:39 PM
> > To: xsl-list@lists.mulberrytech.com
> > Cc: chadsm@mitre.org
> > Subject: Re: [xsl] Carrying Namespaces through a XSL to XSL
> > Transformation
> >
> >
> > Chad,
> >
> > Here is a template that I have used in the past, using MSXML3.
> > This successfully outputs multiple namespace references in
> > the resulting
> > XSLT.
> > I am using parameters in the below example to define on of my
> > namespaces and
> > schema locations.
> >
> > Good luck,
> > -Kevin
> >
> >
> >
> > <!--
> > renderXSLStylesheetStart:
> > renders the opening xsl:stylesheet tag and attrs
> > -->
> > <xsl:template name="renderXSLStylesheetStart">
> > <xsl:text disable-output-escaping="yes"><?xml
> > version="1.0"?></xsl:text>
> > <xsl:text disable-output-escaping="yes">
> > <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
> > version="1.0"</xsl:text>
> > xmlns:s="urn:schemas-microsoft-com:xml-data"
> > xmlns:dt="urn:schemas-microsoft-com:datatypes"
> > xmlns:<xsl:value-of select="$ns"
> > />="x-schema:http://localhost/schema/<xsl:value-of select="$name"
> > />Schema.xml"
> >
> > xmlns:editA="x-schema:http://localhost/schema/EditAttributes.x
> > ml" >
> > </xsl:text>
> > </xsl:template>
> >
> > -----Original Message-----
> > From: Smith, Chad <chadsm@mitre.org>
> > To: 'xsl-list@lists.mulberrytech.com'
> > <xsl-list@lists.mulberrytech.com>
> > Date: Wednesday, December 27, 2000 10:30 AM
> > Subject: [xsl] Carrying Namespaces through a XSL to XSL
> Transformation
> >
> >
> > >> Because of the inability to convert XPath strings to XPath
> > nodesets, I am
> > >> forced to perform XSL to XSL Transformations. these
> > transformations have
> > >> worked out well with a single exception: I cannot migrate
> > more than one
> > >> namespace to the resulting XSLT file. This is a problem
> > because I would
> > >> like for the resulting XSLT to utilize some form of
> > embedded script, but
> > >> since I am using Xalan, this requires two additional namespaces.
> > >>
> > >> I am currently using 'xsl:namespace-alias' to carry over
> > the actual XSL
> > >> namespace, however multiple uses of this tag with
> > different properties do
> > >> not migrate additional namespaces but only attempt to
> overwrite the
> > first.
> > >>
> > >> Any ideas?
> > >
> > > XSL-List info and archive:
> http://www.mulberrytech.com/xsl/xsl-list
> > >
> > >
> >
> >
> > XSL-List info and archive:
> http://www.mulberrytech.com/xsl/xsl-list
> >
>
> XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
>
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list