- From: <bugzilla@jessica.w3.org>
- Date: Tue, 01 Feb 2011 16:02:40 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11931
Mary Holstege <holstege@mathling.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |holstege@mathling.com
--- Comment #1 from Mary Holstege <holstege@mathling.com> 2011-02-01 16:02:39 UTC ---
(For myself)
I don't think a distinct error code is warranted. I think the analogy with
how collation URIs are handled is a good one. While in theory one could
take the URI as a literal reference to some resource that gets dereferenced
at query time, in most implementations it is taken as a name that references
a precompiled efficient data structure or code module. I can see that if an
implementation does choose to dereference it as a live URI, then you may
want to report somewhat different information to the end-user, but that is
not the same as saying the error code in the spec has to be different.
The fact is, for most implementations, the distinction you want to make is
meaningless and untestable.
--
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:02:43 UTC