Altova Mailing List Archives


RE: [xsl] Common Element Solution (XSL 2.0)

From: "Pawson, David" <David.Pawson@----------->
To:
Date: 3/23/2005 8:24:00 AM
-----Original Message-----
    From: Michael Kay
    > I  also thought about the one-such-name-to-a-table problem,

    For your particular application the source data obviously
    satisfies this constraint, but the constraint needs to be
    stated in case someone tries to apply the same algorithm to
    a different situation where the constraint doesn't hold.

    It's not hard to generalize the solution: instead of

       count(current-group()) = $number-of-tables

    you want something like

       count(current-group()/parent::table) = $number-of-tables

    relying on the fact that "/" eliminates duplicates.

That last line has me puzzled Mike. Would someone expand please,
for the uninitiated? In your previous emails you didn't say how
the $number-of-tables variable was defined, same way?



regards DaveP

Disclaimer

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.