Lists Home |
Date Index |
- From: Paul Grosso <email@example.com>
- To: firstname.lastname@example.org
- Date: Mon, 21 Sep 1998 12:10:08 -0500
At 20:51 1998 09 20 -0400, John Cowan wrote:
>I've just finished the first cut of my implementation of Socats
>as a SAX EntityResolver, and two points have come up:
>1) With the minor exception of notation declarations, every public id
>in XML has an accompanying system id. Therefore, the OVERRIDE entry
>does not make sense: it must be ignored, and the default must be YES
>rather than NO.
>To explicate OVERRIDE: in SGML Socats, OVERRIDE NO means that when
>an explicit system id is present, the catalog entries are ignored;
>OVERRIDE YES means the catalog entries override an explicit system id.
I'm not understanding why OVERRIDE NO doesn't make sense. Perhaps
I'm missing something about SAX or your implementation. (Assume I
understand TR9401, since I edited it.)
>2) As another consequence of system ids being always present and always
>URLs, a usable Socat implementation must not search the whole
>public catalog space for SYSTEM entries. When should the search stop?
>In some sense "when going offsite", but just when is that?
I don't understand what the problem is, and I don't understand how--if
there really is a problem--anything about XML makes it a problem that
isn't a problem with SGML in general (XML is SGML, you know).
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)