- From: <bugzilla@jessica.w3.org>
- Date: Tue, 01 Feb 2011 16:26:29 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11931 --- Comment #2 from Paul J. Lucas <paul@lucasmail.org> 2011-02-01 16:26:28 UTC --- Even if I think that everything you've just said were correct, you could still get the same effect by simply not including a URI mapping in the XQFTTS catalog file. Then the URI would truly be unknown. That's all I want, not a change to the spec, i.e., I am not suggesting that a new error code be created. If the mapping were not there, then I could easily return FTST0018. However, for my implementation (as a "quality of implementation" improvement), I'd be free to return some other "file not found" error when the mapping is there but the mapped-to resource is not. So if you simply remove the mapping from the XQFTTS catalog file, I think everybody would be happy. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Tuesday, 1 February 2011 16:26:31 UTC