W3C home > Mailing lists > Public > public-qt-comments@w3.org > December 2012

[Bug 19750] [XQ30] Error code required

From: <bugzilla@jessica.w3.org>
Date: Fri, 21 Dec 2012 07:52:43 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-19750-523-lleDp1ZKkU@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19750

--- Comment #11 from Tim Mills <tim@cbcl.co.uk> ---
(In reply to comment #10)
> (In reply to comment #9)
> 
> We do make decisions in later meetings that are different from decisions we
> made at earlier meetings.
> 
> I think you and Tim are asking for a feature that we do not currently
> provide. I do not believe that this is a bug or a requirement for XQuery
> 3.0. Perhaps we should explore this in XQuery 3.1?

I reluctantly think this is a feature request, but observe that marking a
module as prohibiting the schema aware feature is a pointless activity, merely
resulting in one error code being substituted for another (in the case that the
processor is not schema aware).  In the case that the processor is schema
aware, it seems far fetched that a developer would bother to write a
prohibition statement after having written an import schema declaration!

Marking modules as prohibiting the module import feature appear equally
pointless.

Personally I'd remove the prohibit/require feature from the spec until it does
something more useful.  Its lamentable location in the grammar, following many
of the syntactic features which it affects, doesn't help.  Being able to switch
on or off static typing is quite useful, but that is about it.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 21 December 2012 07:52:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 21 December 2012 07:52:46 GMT