Re: What to do given both SYSTEM and PUBLIC?
> >That's sensible, although there would then be no standard XML way of
> >processing a document with PUBLIC -- you'd have to use a resolution
> But you have to do this with all apps of SGML: it's what a PUBLIC id
> is _for_.
People are meaning different things by "resolution". Joe's point was
that if you receive an XML document over the web and you don't have the
DTD, your XML software hass to figure out automatically how to fetch
tbe DTD, and do it, with no user intervention.
> I still don't see the problem with being directive about this:
> <!doctype foo PUBLIC "-//Foo, Inc//DTD Ab Fab Stuff//EN"
If we end up using CATALOG to link to style sheets too, this may make sense,
since then we'll need the public ID to associate the style sheet with
all documents using a given DTD (and that particular catalog).
If we don't, the public ID isn't really needed in this case, and you're
best off with a normal URL cache.
If some systems use the PUBLIC ID in some way to fetch DTDs, and some
future system fetches a different DTD than the one you specified, e.g.
because they happened to use the same public ID as you, there may of
course be problems...
> At 16:57 19/02/97 -0500, Liam Quinn wrote:
Actually, there is a Liam Quinn at Waterloo who posts to the HTML groups
about SGML, but I am Liam Quin (one "n")... this is a source of confusion
for some people, I know...
Liam Quin, email@example.com | lq-text freely available Unix text retrieval
Senior Technical Consultant | FAQs: Metafont fonts, OPEN LOOK UI, OpenWindows
SoftQuad Inc. +1 416 544-9000 | xfonttool (Unix xfontsel in XView)
http://www.softquad.com/ | the barefoot programmer