- From: <bugzilla@jessica.w3.org>
- Date: Sun, 17 Feb 2013 11:18:31 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21025
Michael Kay <mike@saxonica.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mike@saxonica.com
Component|XQueryX 3.0 |XQuery 3.0
Assignee|jim.melton@acm.org |jonathan.robie@gmail.com
--- Comment #1 from Michael Kay <mike@saxonica.com> ---
Personal response: I agree there are many use cases where this would be
convenient, and indeed where the namespace axis would be convenient. However,
there is a workaround in 3.0 (unlike 1.0) which will have to do for now: you
can use
in-scope-prefixes($e)!namespace-node(){.}{namespace-uri-for-prefix($e,.)}
to "reconstruct" the namespace nodes for element $e that you would have found
using the namespace axis if it were available.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Sunday, 17 February 2013 11:18:32 UTC