- From: <bugzilla@jessica.w3.org>
- Date: Thu, 02 Jun 2016 09:46:43 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29683 Bug ID: 29683 Summary: [FO31] Map lookup through function-call syntax does not explain what happens if the key does not exist Product: XPath / XQuery / XSLT Version: Member-only Editors Drafts Hardware: PC OS: Windows NT Status: NEW Severity: minor Priority: P2 Component: XPath 3.1 Assignee: jonathan.robie@gmail.com Reporter: abel.braaksma@xs4all.nl QA Contact: public-qt-comments@w3.org Target Milestone: --- Section 3.11.1.2 Map Lookup using Function Call Syntax in FO31 does not explain what happens if 1) the key does not exist (should it through an error, or behave like map:get?) 2) the key is not comparable using the collation (behave like map:get?) Perhaps we should normatively link this section to the semantics of map:get, or conversely, move the semantics of map:get to this section and link back from map:get to this section. Alternatively, using this syntax may raise an error for non-existing map keys, but I doubt that was the intend. Note: sections 3.11.3.1 Unary Lookup and 3.11.3.2 Postfix Lookup do not seem to explain this either. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 2 June 2016 09:46:46 UTC