in reply to XML to XHTML table

In reference to your using attributes, I would avoid doing that for anything that is supposed to be information. Why? Consistency. I would keep attributes to help define the object and child nodes to describe all the information that is used by the parent.

Whatever way you chose be consistent, don't let yourself or others have to guess WHERE they are going to find the information. KNOW where the information is going to be.

You can identify that this is a problem basically by looking at your XSL, if it is turning out to be very complicated, then you are probably doing something wrong.

Replies are listed 'Best First'.
Re^2: XML to XHTML table
by bladestonight (Novice) on Apr 27, 2007 at 00:38 UTC
    My problem with this is I what to group nodes by Name, Version, cellsize and refinement. So in the following the information which changes are refinement, runtime and CumulativeVol, could I get my desired output just by having?:
    <VolumeReport> <Name>v_example.gri</Name> <Version>1.0</Version> <Refinement>10</Refinement> <CellSize> <CellSizeX>500.000</CellSizeX> <CellSizeY>500.000</CellSizeY> <VolumeUnits id="m3">Cubic Metres</VolumeUnits> <CumulativeVol>147977918</CumulativeVol> </CellSize> </VolumeReport> <VolumeReport> <Name>v_example.gri</Name> <Version>1.0</Version> <Refinement>4</Refinement> <CellSize> <CellSizeX>500.000</CellSizeX> <CellSizeY>500.000</CellSizeY> <VolumeUnits id="m3">Cubic Metres</VolumeUnits> <CumulativeVol>147751938</CumulativeVol> </CellSize> <VolumeReport>
    Desired output:
    v_example.griGrid Refinements
    Version 15.5410
    CellSize Runtime Volume Runtime Volume
    (500.000,500.000) 10 147751938 12 147977918