Lists Home |
Date Index |
> Uche Ogbuji wrote:
> > A process-xinclude option for output is also a good idea. The
> > tricky bit is that XInclude requires an infoset and XSLT can
> > produce output without a corresponding infoset (i.e. multiple
> > root elements).
> Isn't this in principle just as tricky for the input, since input has the
> same characteristic? That's a question I guess you'll have to address should
> you decide to support EGPE parsing for source trees in 4XSLT :-)
Yes, it would be tricky. I think we'd have to turn off XInclude processing in the case of source as EGPE.
I agree with Jeni that XInclude should consider relaxing the proper infoset requirement in order to allow XInclude processing in EGPE documents.
Uche Ogbuji Fourthought, Inc.
http://uche.ogbuji.net http://4Suite.org http://fourthought.com
Track chair, XML/Web Services One (San Jose, Boston): http://www.xmlconference.com/
DAML Reference - http://www.xml.com/pub/a/2002/05/01/damlref.html
The Languages of the Semantic Web - http://www.newarchitectmag.com/documents/s=2453/new1020218556549/index.html
XML, The Model Driven Architecture, and RDF @ XML Europe - http://www.xmleurope.com/2002/kttrack.asp#themodel