|
Subject: Re: [xsl] Restricting Element Order with Attribute Values From: Rudi Starcevic <tech@xxxxxxxxxxxx> Date: Tue, 27 Sep 2005 00:33:55 +1000 |
David,
>Can you give a small
>example where you think that constraining the source order would save you a
>test?
>
>
My current stylesheet is hard-coded with the order of webstats.
<xsl:template name="list_servers">
<a>
<xsl:attribute name="href">
<xsl:value-of select="webstats[1]/@uri"/>
</xsl:attribute>
MRTG</a>
<a>
<xsl:attribute name="href">
<xsl:value-of select="webstats[2]/@uri"/>
</xsl:attribute>
Bytes</a>
</xsl:template>
I'm investigating ways to make sure the webstat uri's do not
get mixed up. Hard coding output on unrestricted input order
seems like trouble if I don't add some error/order controls.
Sorry I understand xsd is off-topic, apologies, I'll keep to
the list topic from now on.
Thanks.
Regards,
Rudi.
| Current Thread |
|---|
|
| <- Previous | Index | Next -> |
|---|---|---|
| Re: [xsl] Restricting Element Order, David Carlisle | Thread | Re: [xsl] Restricting Element Order, David Carlisle |
| [xsl] Handling Tree Fragments, Gustave Stresen-Reut | Date | [xsl] Need help using variable in s, Frank Stoner |
| Month |