OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: MS IE5, PURL's, Entities (fwd)

[ Lists Home | Date Index | Thread Index ]
  • From: John Robert Gardner <jrgardn@emory.edu>
  • To: xml-dev@xml.org
  • Date: Fri, 26 May 2000 12:25:00 -0400 (EDT)


I posted the following on XML-L and Paul Kelly was kind enough to give a
bit of a how-to reply.  I'm posting here b/c I'm curious about the more
theoretical issue of how MSXML handles PURL's in SYSTEM identifiers for
external entities.  I've managed to make my DTD work, using the
"hardwired" or absolute URL, but I am wondering if it's normative for the
PURLS to not work from within the DTD.  The DTD itself is called from the
instance by a SYSTEM identifier which uses the PURL location of the DTD.

Thanks for any light shed on this.  I'm curious as it seems odd for MSXML
to simply refuse to accept a PURL . . . 'cept that it gives BizTalk more
biz-ness maybe?



<snip source="XML-L post">

I have a TEI-xlite DTD with some external entity sets, which, when
declared with the purl.org, do not work:

<!ENTITY % translit SYSTEM

but which do work with the proper URL:

<!ENTITY % translit SYSTEM

These declarations do work.  Feel free to go and have a look, but when I
changed it to the hard link, all was well.  The xml instance in the same
directory calls the DTD via a purl to that directory, but teh calls to the
purl from inside teh DTD do not work.

Is this a standard behavior, or is it an MS IE5 version of reality?

thanks, jr

Date: Wed, 24 May 2000 15:32:56 +0100
From: Paul Kelly <paul.kelly@MERANT.COM>
Reply-To: General discussion of Extensible Markup Language
Subject: Re: MS IE5, PURL's, Entities

The "proper" URL points to an actual entity set; the other URL points to
something which redirects my browser to the proper URL. MSXML probably
doesn't understand HTTP redirection, which is why it only works when you
point it to an actual entity set.

There are two flags on XMLDOMDocument, resolveExternals and validateOnParse
which might be relevant to you. These are both set to TRUE by default. Set
them to false, and MSXML won't go chasing down external entities defined in
document DTDs. However... even if you set validateOnParse to FALSE, MSXML
will throw an exception if it comes across an entity it can't resolve in a
document it is parsing. This is behavior that has caused me a fair amount of
grief in the past...

thanks again everyone, 

John Robert Gardner
XML Engineer
Emory University
"There is a difference between knowing The Path, and walking the Path."

John Robert Gardner, Ph.D.
XML Engineer
Emory University
"If there is something you're thinking of doing, or wish you could do,
begin it.  In boldness there is mystery and power . . . . "  -Goethe

This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS