• To: xml-dev@l...
• Subject: Re: XInclude Support
• From: David Megginson <david@m...>
• Date: Fri, 9 May 2003 13:29:14 -0400
• In-reply-to: <200305091652.h49GqQ924728@d...>
• References: <5.2.0.9.0.20030509074459.06111b30@m...><200305091652.h49GqQ924728@d...>

Joe English writes:

 > 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).

I chaired a session at XML Europe where Michael Grimley presented a
system from the U.S. Navy that uses XInclude on the client
(implemented in XSLT) for compound documents.


All the best,


David

-- 
David Megginson, david@m..., http://www.megginson.com/

• Follow-Ups:
  • Re: XInclude Support
    • From: Daniel Veillard <veillard@r...>

• References:
  • XInclude Support
    • From: Jonathan Robie <jonathan.robie@d...>
  • Re: XInclude Support
    • From: Joe English <jenglish@f...>

• Prev by Date: Re: Blended Authentication (AKA "Granular Access Control")
• Next by Date: SALT Transaction Protocol [was: Blended Authentication (AKA "Granular Access Control")]
• Previous by thread: Re: XInclude Support
• Next by thread: Re: XInclude Support
• Index(es):
  • Date
  • Thread