[
Lists Home |
Date Index |
Thread Index
]
> From: "Simon St.Laurent" <simonstl@simonstl.com>
>
>
> > (Somewhat paradoxically, I'm hoping that xpath1() will encourage the
> > creation of more XInclude implementations, in order that these issues are
> > encountered more frequently and best practices can start to evolve.)
>
> I've never quite cottened on to why XIncludes are useful. Is it because
> the longevity of ID/IDREF means that "document scope" has not gone
> away, yet because entities are not first-class constructs in XML the current
> generation of tools promotes an all-element solution (and bugger the
> structure)?
To me, the following are the most useful things about XIncludes which are
lacking in EPEs:
1) the ability to include only part of the referent, through XPointer.
2) the ability to include the other document as text.
I have found these very useful in practice. I don't always have control over
the document I'm including, so the ability to select only in part can be very
important. And as one who writes many articles in XML form, the ability to
include external listings, and have them all escaped for me on inclusion saves
a lot of work.
--
Uche Ogbuji Fourthought, Inc.
http://uche.ogbuji.net http://4Suite.org http://fourthought.com
Python&XML column: 2. Introducing PyXML - http://www.xml.com/pub/a/2002/09/25/p
y.html
The Past, Present and Future of Web Services 1 - http://www.webservices.org/ind
ex.php/article/articleview/663/1/24/
The Past, Present and Future of Web Services 2 - 'http://www.webservices.org/in
dex.php/article/articleview/679/1/24/
Serenity through markup - http://adtmag.com/article.asp?id=6807
Tip: Using generators for XML processing - http://www-106.ibm.com/developerwork
s/xml/library/x-tipgenr.html
|
