RE: RE: RE: RE: FW: XSL processes XML incorrectly whe

Hi Charles...

a) There are seven <optionListx> elements, where "x" represents a digit
from 1 through 7. Are there always exactly seven <optionListx> elements?

>> correct

b) Each <optionListx> contains zero or more <option> child elements
with no guarantee as to the number of <option> elements in each.

>> correct

c) The number of rows in the output table will the the the same as the
number of <option> elements in the <optionListx> with the largest number
of <option> child elments.

>> correct

d) A row should have as many <td> elements as there are <optionListx>
elements.

>> correct

e) In a given row, the successive <td> elements should contain the
values of one <option> element from each successive <optionListx> such
that the first row would contain optionList1/option[1],
optionList2/option[1], optionList3/option[1], optionList4/option[1],
optionList5/option[1], optionList6/option[1], optionList7/option[1].

>> if numbered from [1] correct, some people say [0] is the first
occurrence. But you are correct.

Each successive row would vary in that the number in the square brackets
"[]" would increment by one.

>> correct

f) At the point where optionListx/option[y] would return a null value,
an empty <td> should be emitted by the stylesheet.

Is this correct?

>> this is where it gets tricky. For example in optionList2 there are 10
occurrences, the first 8 have values, then 9 is a null and 10 has a
value. I need to display occurrence 9 as a blank, so that occurrence 10
is displayed in row 10. Null elements that come after the actual data
are trimmed by the application sending the XML.









-----Original Message-----
From:     Cave, Neil <Neil.Cave@xxxxxxxxxxxxxx>
Sent:     Thu, 9 Mar 2006 16:01:57 +0100
To:       <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>
Subject:  RE: RE: RE:  FW:  XSL processes XML incorrectly when
uneven number of values returned in array elements

Hi Charles, thanks for having a look at this for me.

Each optionList/option should be in a unique row.
That row should match the occurrence of the option element under
optionList*/

So if there is a value in the first occurrence of optionList*/ then it
should be displayed in row 1

If you look at the XML under /free-xml you see that optionList1 has 7
array values starting from the first occurrence of optionList1/option.

optionList2 has 10 with a Null value in occurrence 9.

When I apply the stylesheet the display shows the first occurrence of
optionList1 starting from row 3, whereas optionList2 starts from row one
(i.e. matching the occurrence in the XML).

Each unique optionList is the source of a new column (7 in total), and
each occurrence of option within each optionList is the source of a new
row.

The first occurrence of all optionList/options should be on row one.

Do this possibly make more sense?


-----Original Message-----
From: cknell@xxxxxxxxxx [mailto:cknell@xxxxxxxxxx]
Sent: 09 March 2006 04:47 PM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: RE: RE: RE:  FW: XSL processes XML incorrectly when uneven
number of values returned in array elements

Now, I've looked over the relevant part of the stylesheet and I'm still
confused as to what element in the data file should be the source of a
new row and what element should be the source of a new table division.
Can you shed some light on this?
--
Charles Knell
cknell@xxxxxxxxxx - email



-----Original Message-----
From:     Cave, Neil <Neil.Cave@xxxxxxxxxxxxxx>
Sent:     Thu, 9 Mar 2006 15:28:06 +0100
To:       <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>
Subject:  RE: RE:  FW:  XSL processes XML incorrectly when uneven
number of values returned in array elements

That is correct...

My apologies for flooding the list with eXcessML

-----Original Message-----
From: cknell@xxxxxxxxxx [mailto:cknell@xxxxxxxxxx]
Sent: 09 March 2006 04:26 PM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: RE: RE:  FW: XSL processes XML incorrectly when uneven
number of values returned in array elements

Actually, Neil, I only really wanted the part of the document that's
causing the problem. After looking over the input, I have made the
hypothesis that the part of the transformation that's troubling you is
the <free-xml> element and its children, is that correct?
--
Charles Knell
cknell@xxxxxxxxxx - email