Re: best practices re xsl:{import,include,next-match,

> No magic answer to this one. You could use apply-imports instead of
> next-match - interesting to see that there is a use case for this. Is there
> any reason the generic match="node()|@*" template can't be moved into the
> generic stylesheet module?
> 
> Changing the import to include seems to me to be storing up other problems
> for the future.

I suppose that the reason I hadn't considered the match="node()|@*"
template because I had thought of traversal logic as being "more specific"
than would be appropriate for a generic stylesheet.  I suppose if one
thinks of this as part of the library contract, that traversal is handled
by the generic stylesheet and you can override that if necessary, then
moving it would be appropriate.

I think I'll do that, then... Thank you. :)

Jim

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
James A. Robinson                       jim.robinson@xxxxxxxxxxxx
Stanford University HighWire Press      http://highwire.stanford.edu/
+1 650 7237294 (Work)                   +1 650 7259335 (Fax)