- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 08 Jul 2008 07:47:20 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5840
Summary: [XSLT 2.1] Enhancements to pattern syntax
Product: XPath / XQuery / XSLT
Version: Working drafts
Platform: PC
OS/Version: Windows NT
Status: NEW
Severity: normal
Priority: P2
Component: XSLT 2.1
AssignedTo: mike@saxonica.com
ReportedBy: mike@saxonica.com
QAContact: public-qt-comments@w3.org
(Captured en-passant during a WG telcon)
There are a number of restrictions on patterns that don't really have any good
justification. This was an area we left largely untouched in 2.0 except where
we automatically inherited changes being made to XPath expressions.
Constructs that would often be useful in patterns include:
* parentheses: (//title)[1]
* union in a step: (chapter|appendix)/title
* anchoring the pattern to a specific document:
$lookup-doc//entry
doc('lookup.xml')//entry
* matching any node that is a member of a preselected node-set
$preselection
* use of "." with a predicate:
.[f:is-special(.)]
All of these can currently be expressed, but often rather inelegantly; the 4th
case above, for example, is match="node()[. intersect $preselection]".
--
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 Tuesday, 8 July 2008 07:47:55 UTC