A URL for the SYSTEM path is great for specifying "a stable and central
location" as Tomaz points out. Just be aware that not all parsers will
accept a URL as a SYSTEM path. Xerces does; nsgmls doesn't. nsgmls is much
faster than Xerces -- particularly useful when parsing many documents in
one fell swoop.
Digital Library Production Services
University of Virginia Library
[log in to unmask]
On Sat, 22 Feb 2003, 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