At 18:35 2002 02 20 -0800, Paul Prescod wrote: >Julian Reschke wrote: >> >>... >> >> For instance, I may have an XHTML document, which somewhere inside contains >> XInclude instructions. I'd have to run this through an XInclude processor >> before it can be passed to the browser. >> >> So, while the XSLT problem can be worked around, I don't think this can be a >> general solution.... > >Well there is currently no solution to this problem. Right, I think this is the XML Processing Model problem. > Multiple levels of >top-level elements would actually be one solution that isn't entirely >inelegant. It is a big problem if you see XInclude and XSLT in the same >document to know which to apply first. Right, processing model problem. > I think that's part of why >XInclude hasn't taken off. I think part of the reason is that it *just* became a CR minutes ago. See http://www.w3.org/TR/2002/CR-xinclude-20020221/ . paulReceived on Thursday, 21 February 2002 11:26:05 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 12 September 2008 07:01:49 GMT