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.
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--