> Elliotte,
>
> I believe that Mike Kay has won this on a TKO, but IMHO it is a tragically
> pyrrhic victory. If, in fact, the stuff of XSLT is not to be XML but a source
> tree abstracted by unspecified means, perhaps from XML and perhaps not, then
> Antaeus has truly cut off his own legs. I won't put words in Len's mouth (!),
> but surely the grounding of legally acceptable transactions in the precise
> language of contracts requires at some point coming back to a very specific
> document at a lexical level, and not to what might be XIncluded as an
> elaboration of that text.
OK, in the spirit of tit-for-tat classical references; when Dionysius
unexpectedly transformed Acoetes' crew into beasts, they only had themselves
to blame. No one made them try to shanghai an innocent, harmless-looking lad
into slavery.
Translation to the pertinent argument: if you construct a source document that
uses elements in the namespace and with the name reserved by the XInclude
specification, why on earth would you blame a processor for acting on those
instructions? 4Suite advertizes itself as an XInclude processor, among other
things. Act accordingly.
It's simple. If you don't want 4XSLT to pergorm XInclude processing on your
docuemnts, either tell it not to, or don't use XInclude in the first place.
What does Pyrrhus have to do with it?
--
Uche Ogbuji Fourthought, Inc.
http://fourthought.com
http://4Suite.org http://uche.ogbuji.net
Track chair, XML/Web Services One (San Jose, Boston):
http://www.xmlconference.com/
RDF Query using Versa - http://www-106.ibm.com/developerworks/xml/library/x-thi
nk10/index.html
WSDL and the Wild, Wild West - http://adtmag.com/article.asp?id=6004
XML, The Model Driven Architecture, and RDF @ XML Europe -
http://www.xmleurope.com/2002/kttrack.asp#themodel
