Lists Home |
Date Index |
- From: Chris Maden <email@example.com>
- To: firstname.lastname@example.org
- Date: Tue, 16 Dec 1997 10:04:29 -0500
> So if interpreted as "file:" the above parses fine on Windows and
> fails on Unix. If the same pair of files would have been served via
> "http:", the error would have become obvious on both platforms (404
> File Not Found).
Are you sure about that? I think that Windows servers will attempt to
find a non-case-matching file. But in any case:
> Should XML try to overcome this (e.g. by requiring case-sensitivity
> in file:-URL, despite of the underlaying OS), or is this out of
> scope ?
It's out of scope. Case screw-ups are only one way you can break your
URLs; I don't see why XML should try and define resolution for this
one case, *especially* since the rest of the language is case-
sensitive. A very simple rule: "Broken URLs in XML documents are
broken." I think we can all live with that one.
<!NOTATION SGML.Geek PUBLIC "-//Anonymous//NOTATION SGML Geek//EN">
<!ENTITY crism PUBLIC "-//O'Reilly//NONSGML Christopher R. Maden//EN"
<USMAIL>90 Sherman Street, Cambridge, MA 02140 USA" NDATA SGML.Geek>
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)