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: Wed, 7 Feb 2001 00:43:43 +0000
- Organization: Silmaril Consultants
- References: <3.0.32.20010206181923.01173090@notesmail.arbortext.com>
- Reply-To: xsl-list at lists dot mulberrytech dot com
On Wed, 07 Feb 2001, Paul wrote:
> Some XML parser has to parse all the entities-to-be-included,
> and it sounds like your application should use a validating
> parser to do that. That way, each bit would be validated
> against its own DTD before inclusion.
Yep. All the files are validated because they're created in a
validating editor :-) But that doesn't stop some authors
and [human] editors deciding to correct an error spotted
at a late stage by "quickly" opening the file in a plaintext
editor and "fixing" the problem -- invalidly. This is a
management problem, not an XML or XSL problem, but
the nature of the politics surrounding the application has
convinced the implementors that a belt-and-braces
approach is the safest course. Their apparently seamless
join of a fragment-inclusion mechanism to a chunking
server is quite impressive.
///Peter
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list