This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: XInclude in Cocoon
- To: xsl-list at lists dot mulberrytech dot com
- Subject: Re: [xsl] XInclude in Cocoon
- From: Peter Flynn <peter at silmaril dot ie>
- Date: Tue, 6 Feb 2001 23:43:55 +0000
- Organization: Silmaril Consultants
- References: <3.0.32.20010206155806.00fed004@notesmail.arbortext.com>
- Reply-To: xsl-list at lists dot mulberrytech dot com
On Tue, 06 Feb 2001, Paul wrote:
> >What I meant was, what happens when you include a TEI Lite file
> >inside a DocBook file? The two have incompatible markup.
>
> You're still thinking in terms of parsing a document with
> external entities against a DTD.
Actually I was thinking of how to construct the XSL to let me
do exactly this. Working with other people's documents, ones
which you can't go changing, means having to devise ways to
get around the conflicts of some element type names.
> XML--along with its
> concept of well-formedness and its companion specs such as
> Infoset, XInclude, XSLT, XML Schema etc.--has, for better
> or worse, taken us beyond that.
I'm not sure "beyond" is right. "Beside" is probably closer.
Your description of the process of xinclusion is very useful,
but when working with some applications there is a requirement
to conduct some form of checking that the entity being included
conforms to some kind of known pattern _before_ inclusion
(or indeed, rejection) takes place, in order to ensure that any
subsequent process (like applying styles) won't blow up in your
face because some idiot edited the file with Notepad and got
a typo in some markup.
///Peter
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list