This is one of those "XML processing model" ratholes!
Uche, does your document() function also do XInclude expansion? If so,
I'd have to agree with Elliotte that it would be confusingly different
than every other document() function on the planet! I would say that if
the XSLT specification does not describe a particular transformation be
applied to the input stream, then this expansion is potentially
confusing. I would personally not expect XInclude expansion to happen
without my specific action.
How about this as a middle ground: Could you require some kind of
statement in the XSLT transform that indicated that the user was aware
that XInclude processing might take place?
Paul Prescod