Re: IE5 xmlns DTD attribute BUG was Re: Use of default namespace declaration

["Jonathan Borden" <jborden at mediaone dot net>]

Clarification, the non-local DTD problem exists with the October release
version of MSXML3 (as well as the Sept version), and is not an issue of the
SYSTEM identifier starting with http://... as I stated below, but rather
when a <!DOCTYPE xxx PUBLIC "..." "yyy.dtd"> definition is present in a file
located at a non-local URL and the DTD is located in the same directory as
the XML file e.g. see:

http://www.openhealth.org/ASTM/operative.note.example.xml

(this browses fine when it and the collection of DTDs/module are downloaded
to a local directory).

Jonathan

> Joshua Allen wrote:
>
>
> > Hi Sebastian,
> >
> > I think this was lax conformance on part of the earlier parser, and has
> > since been tightened.  See
> > http://www.rpbourret.com/xml/NamespacesFAQ.htm#q7_2.
> >
> >
>
> Err... no. This is a BUG. Explicitly an xmlns attribute can be defaulted
in
> a DTD (see section 4.3 in the article you quote above.) This error message
> from IE5 is a non-conformance. See http://www.w3.org/TR/REC-xml-names
> Namespace Constraint: Prefix Declared if a question remains.
>
> Another BUG in IE5s handling of DTDs ... parsing of DTDs (using the Sept
> MSXML3) hangs the browser when the SYSTEM ID is a URI of the form
http://...
> but not when the same DTD file is located on the local disc. (This
behavior
> is not constant but reproducable across multiple installations and people
in
> multiple organizations ... i.e. I am not the only one having this
problem).
>
> Jonathan Borden
> The Open Healthcare Group
> http://www.openhealth.org
>
>
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list