[
Lists Home |
Date Index |
Thread Index
]
Jonathan Robie wrote:
> How important is XInclude? Few products support it today. How strong is
> user demand for it?
My impression is that XInclude is a wrong-size-fits-nothing
kind of thing. Other specs that need XInclude-like functionality
often need something with _slightly_ different semantics, and
end up specifying it themselves instead of reusing XInclude
(<xsl:import>, for instance).
I've developed a number of vocabularies that could have used
XInclude, but ended up using a simpler ad-hoc solution instead.
The main reasons I didn't use XInclude are: XPointer was unnecessary
for my needs (relative URIs were sufficient, I only needed whole-document
transclusion); XPointer was unimplementable (at least by me);
and in a number of cases leaving XInclude out meant I could
leave out XML namespaces as well (since nothing else in the
vocabulary called for them).
--Joe English
jenglish@flightlab.com
- References:
- XInclude Support
- From: Jonathan Robie <jonathan.robie@datadirect-technologies.com>
|
