469,299 Members | 2,066 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,299 developers. It's quick & easy.

how to output unresolved xinclude element

I should like to use xslt to produce a document like the following:

<crate xmlns:xi="http://www.w3.org/2001/XInclude">
<rod id="0">
<slot>1</slot>
<xi:include href="./endcapA/disk/1a/10011.xml"/<!--D1A TR
middles-->
<xi:include href="./endcapA/disk/1a/10012.xml"/<!--D1A TR
middles-->
<xi:include href="./endcapA/disk/1a/10001.xml"/<!--D1A TR
outers-->
<xi:include href="./endcapA/disk/1a/10002.xml"/<!--D1A TR
outers-->
<xi:include href="./endcapA/disk/2a/20001.xml"/<!--D2A TR
outers-->
<xi:include href="./endcapA/disk/2a/20002.xml"/<!--D2A TR
outers-->
<xi:include href="./endcapA/disk/3a/30001.xml"/<!--D3A TR
outers-->
<xi:include href="./endcapA/disk/3a/30002.xml"/<!--D3A TR
outers-->
</rod>
</crate>

i.e. it should contain 'manufactured' unresolved xi:include elements.
How can I get my xsl to output such an element?

thanks

shaun
Mar 7 '07 #1
7 1719
i.e. it should contain 'manufactured' unresolved xi:include elements.
How can I get my xsl to output such an element?
The simplest answer: http://www.w3.org/TR/xslt#element-namespace-alias

An alternative is to construct the element explicitly using the
xsl:element directive.

Either will prevent the new element from being prematurely interpreted.

(These tricks are more often used when writing stylesheets that produce
stylesheets, but they're certainly applicable to this problem as well.)

--
Joe Kesselman / Beware the fury of a patient man. -- John Dryden
Mar 7 '07 #2

The namespace-alias seems neat, but I get a bit of ugliness with it:

I declare my namespaces:

<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
version="1.0" xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xout="myAlias">

and my alias:

<xsl:namespace-alias stylesheet-prefix="xout" result-prefix="xi"/>

and then use it...

<xout:include href="concat($MurPathRoot,$diskpath,'/',xmlMur) "/>
and sure enough all my elements come out ok:

<xout:include href="./endcapA/disk/1a/10301"/>
but the root document element is:

<configuration xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xout="http://www.w3.org/2001/XInclude">

i.e. its declared both the original xi: and my xout: ... is this
expected?

thanks

shaun

In article <45eee4de$1@kcnews01>,
Joseph Kesselman <ke************@comcast.netwrote:
http://www.w3.org/TR/xslt#element-namespace-alias
Mar 7 '07 #3
shaun roe wrote:
i.e. its declared both the original xi: and my xout: ... is this
expected?
There's a similar directive which lets you suppress namespace
declarations that aren't in use. See the spec and/or Kay's book, or wait
a few hours for me to get around to looking it up.

--
Joe Kesselman / Beware the fury of a patient man. -- John Dryden
Mar 7 '07 #4
Joseph Kesselman wrote:
There's a similar directive which lets you suppress namespace
declarations that aren't in use. See the spec and/or Kay's book, or wait
a few hours for me to get around to looking it up.
Since you waited: What you want is the exclude-result-prefixes attribute
of the xsl:stylesheet element. It's described in
http://www.w3.org/TR/xslt#section-Cr...and-Attributes

--
() ASCII Ribbon Campaign | Joe Kesselman
/\ Stamp out HTML e-mail! | System architexture and kinetic poetry
Mar 8 '07 #5
In article <Y-******************************@comcast.com>,
Joe Kesselman <ke************@comcast.netwrote:
>There's a similar directive which lets you suppress namespace
declarations that aren't in use. See the spec and/or Kay's book, or wait
a few hours for me to get around to looking it up.
>Since you waited: What you want is the exclude-result-prefixes attribute
of the xsl:stylesheet element. It's described in
http://www.w3.org/TR/xslt#section-Cr...and-Attributes
I think this won't necessarily do quite the right thing in this case.
Despite its name, exclude-result-prefixes specifies a namespace uri to
be excluded, not a prefix. Since in this case he does need the
xinclude namespace, he may well still get a spurious xout prefix
declared somewhere.

-- Richard
--
"Consideration shall be given to the need for as many as 32 characters
in some alphabets" - X3.4, 1963.
Mar 8 '07 #6
Richard Tobin wrote:
I think this won't necessarily do quite the right thing in this case.
Despite its name, exclude-result-prefixes specifies a namespace uri to
be excluded, not a prefix. Since in this case he does need the
xinclude namespace, he may well still get a spurious xout prefix
declared somewhere.
In the implementation I'm familiar with (Xalan), it should do the right
thing, because it's take as a request not to issue any declarations for
prefixes bound to that URI except those which are actually used by an
element or attribute. But while that's a reasonable interpretation It
may not be the only one... Best suggestion I can make is to try it and
see what happens.

If it doesn't work -- well, an unused namespace declaration really is
pretty harmless.
--
() ASCII Ribbon Campaign | Joe Kesselman
/\ Stamp out HTML e-mail! | System architexture and kinetic poetry
Mar 8 '07 #7
In article <H7******************************@comcast.com>,
Joe Kesselman <ke************@comcast.netwrote:
Richard Tobin wrote:
I think this won't necessarily do quite the right thing in this case.
Despite its name, exclude-result-prefixes specifies a namespace uri to
be excluded, not a prefix. Since in this case he does need the
xinclude namespace, he may well still get a spurious xout prefix
declared somewhere.

In the implementation I'm familiar with (Xalan), it should do the right
thing, because it's take as a request not to issue any declarations for
prefixes bound to that URI except those which are actually used by an
element or attribute. But while that's a reasonable interpretation It
may not be the only one... Best suggestion I can make is to try it and
see what happens.

If it doesn't work -- well, an unused namespace declaration really is
pretty harmless.
I did indeed try this as a first move, and as Richard Tobin has said, it
did not suppress the declaration. (using Saxon) I can live with two
declarations of the namespace, its just not as neat as I'd hoped.

In fact, give that both namespaces are declared anyway in the output, I
found I can reverse the alias/output assignation:

<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
version="1.0" xmlns:x="http://www.w3.org/2001/XInclude"
xmlns:xi="myAlias">

..
..
..

<xi:include href="concat($MurPathRoot,$diskpath,'/',xmlMur) "/>
and get, as output:

<configuration xmlns:x="http://www.w3.org/2001/XInclude"
xmlns:xi="http://www.w3.org/2001/XInclude">
..
..
..
..
<xi:include href="./endcapA/disk/2a/20302"/>
which leaves my end users looking at the familiar <xi:include .../>,
which I suspect they will be happier with.

thanks for the help

shaun
Mar 8 '07 #8

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by Erdem Guven | last post: by
1 post views Thread by CB | last post: by
3 posts views Thread by rene | last post: by
9 posts views Thread by Tjerk Wolterink | last post: by
2 posts views Thread by tllee | last post: by
11 posts views Thread by john fra | last post: by
4 posts views Thread by Tim Arnold | last post: by
2 posts views Thread by McSwell | last post: by
1 post views Thread by CARIGAR | last post: by
reply views Thread by harlem98 | last post: by
1 post views Thread by Geralt96 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.