- From: <bugzilla@jessica.w3.org>
- Date: Sun, 19 Jul 2015 02:22:07 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28966 Bug ID: 28966 Summary: [XQ31] Section 5.2.3: "may only" Product: XPath / XQuery / XSLT Version: Last Call drafts Hardware: PC OS: All Status: NEW Severity: minor Priority: P2 Component: XQuery 3.1 Assignee: jonathan.robie@gmail.com Reporter: mike@saxonica.com QA Contact: public-qt-comments@w3.org Section 5.2.3 (Static Typing Feature) says: If an implementation does not provide the Static Typing Feature, then it MAY report type errors during the static analysis phase only in cases where the inferred static type and the required type have an empty intersection (that is, where evaluation of the expression is guaranteed to fail). It MAY defer some or all type checking until the dynamic evaluation phase. The use of an RFC MAY here is very misleading. The sentence is not intended to be permissive, it is intended as a constraint. "MAY... ONLY" here means "MUST NOT.... EXCEPT". I suggest: If an implementation does not provide the Static Typing Feature, then it MUST NOT report type errors during the static analysis phase except in cases where the inferred static type and the required type have an empty intersection (that is, where evaluation of the expression is guaranteed to fail). It MAY defer some or all type checking until the dynamic evaluation phase. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Sunday, 19 July 2015 02:22:10 UTC