On Mon, 2003-04-21 at 15:28, James J. Ramsey wrote:
--- Andrew Watt <andrew(_at_)andrewwatt(_dot_)com> wrote:
1. What do I want to output?
2. Where will get that data?
3. How can I code it?
I'd suggest separating point 3 into two subpoints:
3a. *How* will I get the data?
3b. How will I channel that data into the output?
As was mentioned in a recent response here, that really isn't
anything to do with XSLT or even XML.
In my short experience with XSLT, point 3a was the
difficult part. I knew what data I wanted, but didn't
know at the time how to get to it. That's especially a
difficulty if one is not in control of the format of
the data source.
A more frequent problem seems to be that the data -- when it
is acquired -- turns out to be some gibberish with pointy
brackets that the client has automagically concocted under
the mistaken belief that adding pointy brackets makes it XML.
That certainly *is* a problem, but it's separate from any
difficulty with actually getting hold of the data.
///Peter
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list