- From: <bugzilla@jessica.w3.org>
- Date: Fri, 04 Jul 2014 11:09:11 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24551 --- Comment #7 from Michael Kay <mike@saxonica.com> --- Proposal: add a new XSLT function current-output-uri() -> xs:anyURI? When an instruction is executed in final output state, there is a current output URI. Initially this is the base output URI; executing an xsl:result-document instruction changes the current output URI to the absolute URI established by the href attribute of the xsl:result-document instruction. When the current-output-uri() function is invoked from an instruction executing in final output state, it returns the current output URI as an absolute URI. When the current-output-uri() function is invoked from an instruction executing in temporary output state, it returns the empty sequence. The function is not stable/deterministic. Add a note/example explaining how to capture the base output URI in a tunnel parameter. Add current output URI to the set of XSLT dynamic context components in section 5.4.4. ADDITIONAL CHANGE In section 2.3.2, base output URI is not required when priming a stylesheet, only when invoking a stylesheet component, and it can vary from one invocation to another. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 4 July 2014 11:09:13 UTC