OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: XInclude [was: XLink transformations]

[ Lists Home | Date Index | Thread Index ]
  • From: Ken MacLeod <ken@bitsko.slc.ut.us>
  • To: xml-dev@xml.org
  • Date: Tue, 25 Jul 2000 12:15:57 -0500

David Orchard <orchard@pacificspirit.com> writes:

> There is no elegent way to remove some particular PIs from an
> included document and keep the future of XInclude open.  XInclude
> must be non-lossy.
> XInclude as it stands is simply the first step towards a goal.
> Eventually, I would like to realize some of transclusion in
> XInclude/XSLT/Query combinations.  With regard to XSLT, a next
> logical step for XInclude/XPath is to add 2 things:

> 1) the ability to specify what the state of the included document
> should be, ie before schema validation, default, after transform,
> after query, etc.  This might require an xpointer addition to
> specify state in URIs

> 2) the ability of the XInclude author to specify when the inclusion
> itself should take place, ie before schema validation, defult, after
> transform, after query, etc.
> Then we could actually meet the use case of an author creating a
> single element that specified including a document that has been
> styled into an source document after the source document's styling
> is complete, thus preserving included documents style aka copyright
> notice.

How does this differ from XLink's behaviors?

I recently needed a similar "include" type functionality (pre- or
post-transform) and asked on xsl-list, and then came to the conclusion
that XLink's behaviors were the likely solution, but just not
available yet (so, back to external merges).

  -- Ken


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS