Re: [xml] Xinclude w/DTD segs
- From: Bruce Miller <bruce miller nist gov>
- To: veillard redhat com
- Cc: xml gnome org
- Subject: Re: [xml] Xinclude w/DTD segs
- Date: Sat, 16 Jun 2001 12:32:34 -0400
Daniel Veillard wrote:
On Fri, Jun 15, 2001 at 08:10:17PM -0400, Bruce Miller wrote:
I'm under the impression that Xinclude allows you to include a
complete, valid XML document, B, into another one, A. That is,
Hum, the concept of validity is defined at parse time (c.f. the
XML specification) while XInclude is based on the Infoset, i.e.
the set of information gathered by parsing XML files.
Hmmm... Is _validity_ (as opposed to well-formed-ness) really
defined at parse time? When initially experimenting with xinclude,
I was hoping I didn't have to cope with declaring xinclude in the
dtd (both declaring the element itself, and declaring all places
it could appear --- that would be a REAL headache!!!)
As far as xmllint is concerned,
xmllint --xinclude --postvalid --noout file.xml
seems to do what I want: parse, do inclusions, and _then_ validate.
But, perhaps, this approach isn't really, um, ... valid :>
At any rate, libxml2 v. 2.3.10 is seg'ing when B does have a DOCTYPE.
This has been reported and is fixed in CVS :-) I think it's time
to ship yet another release. Could you try the cvs snapshot
Yep, that fixes the xinclude problem! Thanks!!
But does this version significantly alter the interface, somehow?
xslt wouldn't run until I discovered that you had also dropped
a snapshot of libxslt at ftp://xmlsoft.org/XSLT/cvs-snapshot.tar.gz
That new xsltproc works again, but even after recompiling
XML::LibXML & LibXSLT, I had to backup from AxKit 1.3.98 to 1.3.97
(which are both old versions, but I'm having some other problems
which aren't really relevant here...)
Thanks for the quick response!
<bruce miller nist gov> http://math.nist.gov/~BMiller/
] [Thread Prev