- From: <bugzilla@jessica.w3.org>
- Date: Wed, 15 Dec 2010 14:36:27 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11555 Summary: [FO3.0] Requirement for path() function Product: XPath / XQuery / XSLT Version: Working drafts Platform: PC OS/Version: Windows NT Status: NEW Severity: normal Priority: P2 Component: Functions and Operators 3.0 AssignedTo: mike@saxonica.com ReportedBy: mike@saxonica.com QAContact: public-qt-comments@w3.org The original use case for the introduction of the EQName syntax was to allow users to generate a persistent path to a node that could then be fed back into the system to retrieve the original node. Such a path might take the form "http://ns1.uri/":doc[1]/"http://ns1.uri/":chap[2]/"http://ns1.uri/":section[4] Well, we did half the job: we added EQNames, but we didn't add the ability to generate the path. A function to do so can be written by users, of course, but it's not trivial. This entry proposes the addition of such a function. (Note, XQuery still has no facility to evaluate a path presented as a string in this form. XSLT 3.0 does have this capability, in the form of the xsl:evaluate instruction.) -- Configure bugmail: http://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 Wednesday, 15 December 2010 14:36:30 UTC