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

[Bug 16583] [XQ30] Compatibility Claims

From: <bugzilla@jessica.w3.org>
Date: Fri, 08 Jun 2012 09:16:04 +0000
To: public-qt-comments@w3.org
Message-Id: <E1ScvIa-0007NI-OD@jessica.w3.org>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16583

--- Comment #4 from Tim Mills <tim@cbcl.co.uk> 2012-06-08 09:16:04 UTC ---
(In reply to comment #3)

> Ditch this answer. I prefer the answer that I gave in comment #2.

I wasn't really asking for a change to the sentence

"Every valid XQuery 1.0 expression MUST be valid in XQuery
3.0 and it MUST evaluate to the same result."

as I think it was obvious what the intent was.  That said, if I were being
pedantic, the only references to what a 'valid' XQuery expression might be in
XQ30 refers to syntactic validity.  However validity could mean:

1.  syntactically valid with respect to the EBNF
2.  valid with respect to static analysis (e.g. type checking)
3.  valid with respect to dynamic execution (not raising errors)

fn:error() is syntactically valid, valid with respect to static analysis, but
does raise an error.

Regarding 

"Yes, unless an implementation chooses to use different values for the two.
This
is a requirements document, I don't think we should say we did not meet the
requirement because it's also possible to use settings that give different
behavior."

It is not always possible to use settings to give the same answer.  I'll try to
put a set of examples together to demonstrate this.

-- 
Configure bugmail: https://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 Friday, 8 June 2012 09:16:10 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:39 UTC