This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: Ignore the DTD
- To: xsl-list at lists dot mulberrytech dot com
- Subject: RE: [xsl] Ignore the DTD
- From: bryan dot s dot schnabel at exgate dot tek dot com
- Date: Fri, 12 Jan 2001 11:29:02 -0800
- Reply-To: xsl-list at lists dot mulberrytech dot com
Thank you. Now it makes perfect sense. It was my desired result that was
flawed. If the DTD assigns a default value to an attribute, and an instance
has an occurrence of that element without the attribute, it is assumed the
attribute is there with the default value.
I should not forget basic XML. Thanks for the clue.
Bryan
-----Original Message-----
From: Eric van der Vlist [mailto:vdv@dyomedea.com]
Sent: Friday, January 12, 2001 10:06 AM
To: xsl-list@lists.mulberrytech.com
Subject: Re: [xsl] Ignore the DTD
bryan.s.schnabel@exgate.tek.com wrote:
>
> > I cannot change the way the instances come to me. Is there a way I can
> > stop the processor from referencing the DTD?
Beyond the XSLT issue, there is a semantic flaw if you need to
differentiate null from default values as defined in the DTD ;) ...
If it's not the case, you can just test that the 3 values of the
attribute are not all equal to their default values.
Otherwise, if you do need to force the parser to skip the DTD and if you
are using a SAX parser, you can implement a specific entity resolver
that will skip this DTD...
Eric
> > Thanks,
> >
> > Bryan
>
> XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
--
------------------------------------------------------------------------
Eric van der Vlist Dyomedea http://dyomedea.com
http://xmlfr.org http://4xt.org http://ducotede.com
------------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list