Lists Home |
Date Index |
Michael Kay wrote:
>>There is another approach that does not involve a URIResolver at all.
>>After changing the location of the imports, just have either a batch
>>file or the program itself rewrite the imports section of the
>>with the current paths, as obtained from the configuration file. You
>>could actually do this each time you run the program.
>>You could also do it with another xslt stylesheet, for that
>>it would probably be easier to do with a bit of code.
> Yes, this is certainly an option: but you need to be aware that recompiling
> a stylesheet every time you run it is rather inefficient.
> I can't see why anyone who knows XSLT would choose to do this with "a bit of
> code" rather than with XSLT.
We don't know the operational scenario here. I pictured a process where
the software would get loaded once and then run for a long time (perhaps
hours or days) without changes. In this case, any recompilation time
would be negligible. Another variant situation occurs when the program,
on startup, gets the stylesheet paths from the config file and loads the
stylesheet at that time. In this case too, creating the imports
stylesheet would take just a little code and would incur no significant
performance penalty (since the stylesheets would get compiled anyway,
changed or not).
Thomas B. Passin
Explorer's Guide to the Semantic Web (Manning Books)