This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: xml to xml identity transforms, and reading the DTD
- To: xsl-list at mulberrytech dot com
- Subject: RE: xml to xml identity transforms, and reading the DTD
- From: "Sebastian Rahtz" <sebastian dot rahtz at computing-services dot oxford dot ac dot uk>
- Date: Thu, 8 Jun 2000 22:14:13 +0100 (BST)
- References: <01BA10F0CD20D3119B2400805FD40F9F0249D8FC@MDYNYCMSX1>
- Reply-To: xsl-list at mulberrytech dot com
DuCharme, Robert writes:
> XML parser is required to pass along an element's attribute values, and has
> various places to look for them (the start tag, the element type's attribute
> list declaration), but isn't required to report where it found them, so the
> app using the parser has no way of knowing whether an attribute value is
> being supplied because it was specified as the default value.
understood. so I need a parser which does NOT read the DTD to that
depth, and that solves my problem, surely?
> values substituted for the references": you're looking for a way to prevent
> the parser from doing something that it's required to do by the XML spec, so
a non-validating parser is surely not required to read the DTD itself?
just the subset, I thought?
> Or, of course, a post-processing step that copies the document without
> copying certain attributes if they have a certain value, but I assume you're
that would indeed be unutterably tedious.... :-}
sebastian
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list