On Apr 10, 2006, at 2:48 PM, robert burrell donkin wrote:
(sounds like your plan is a good match to your problem so this is
just a
FYI)
binding the XSLT specification gives you a way to generate XSL
documents. the old, experimental code generated ECS bound to a
schema or
DTD in a similar fashion.
Okay. I thought that was maybe the way you were going (if I
understand what you are saying correctly - generate code from the
w3.org XSL spec). I was just looking at the spec and thinking that -
but I think it is a bit beyond me to do that at this point - I
vaguely grok XML/XSL/etc., much less language grammars not being a
CompSci person (I am just a lowly Code Monkey).
Anyway, it just occurred to me that my XSL is so simple and mostly
static, that I can use another XSLT to generate it from the XML
config file. I only need to be able to change two small portions of
it; one element needs it's name changeable, and one set of elements/
transforms need to be added for each element in the config file. The
transforms are the same for each element so I can just do a for-each
on each one. I am sure there is a yet more elegant way to do it, but
this will work well enough and it won't be reused except by the
customer.
Thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
