Cart
[Home] [By Thread] [By Date] [Recent Entries]
[Ingo Macherius] > 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. -Chris -- <!NOTATION SGML.Geek PUBLIC "-//Anonymous//NOTATION SGML Geek//EN"> <!ENTITY crism PUBLIC "-//O'Reilly//NONSGML Christopher R. Maden//EN" "<URL>http://www.oreilly.com/people/staff/crism/ <TEL>+1.617.499.7487 <USMAIL>90 Sherman Street, Cambridge, MA 02140 USA" NDATA SGML.Geek> xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i... Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ To (un)subscribe, mailto:majordomo@i... the following message; (un)subscribe xml-dev To subscribe to the digests, mailto:majordomo@i... the following message; subscribe xml-dev-digest List coordinator, Henry Rzepa (mailto:rzepa@i...)
|
