Actually, no, that won't work in this case because I do not trust the
DTD to be stable: the project is in active development. (The developer
swears he hasn't touched it in months and never intends to again, but we
all know how such good intentions turn out!) So the production server
needs to have its own copy of the DTD, and the development servers,
developer's laptop, etc. need to have their own. While I could do that
with a 'localhost' URL, that would mean being able to enforce the same
'directory' structure on the various machines -- so that, for example,
would work on all of them. Since I do not control all these machines,
I'm reluctant to insist on that. That's why I don't want a URL.
Tomaz Erjavec wrote:
> I think XML treatment of PUBLIC ids is a mess.
> But what about specifying a URL for the SYSTEM id?
> This could be a stable and central location.
> But of course you get some overhead in access - it might not be enough
> to matter though.
> Anne Mahoney writes:
> > This is a question about the "system" part of a public identifier in an
> > XML environment.
> > Does this mean I'm stuck actually putting a URI for the DTD file into
> > every one of the user's XML files, and having to maintain it when it
> > changes? Or am I missing something stupid (e.g., telling xalan where
> > to find the catalog)?
> > --Anne Mahoney
> > Tufts University