This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
"The value of the selector attribute must be an XPath expression which starts with "/". That is, it must be an AbsoluteLocationPath as described in [XPath 1.0]. This ensures that the selection is not relative to a specific location." The group has designed an its:selector attribute with an XPath expression. Is there a specific reason to not reuse the select of XSLT?
From the viewpoint of re-using the name 'select' vs. 'selector'. No reason, except maybe because it's not exactly the same as xsl:select. From the semantic viewpoint: its:selector is always an absolution XPath expression (never relative) and it always point to an elemnt or an attribute. So it's not exactly the same as xsl:select.
This is a response of the ITS working group. As we explained at http://www.w3.org/Bugs/Public/show_bug.cgi?id=3291#c1 , the selector attribute is always an absolute location path. This is different to the "select" attribute in XSLT. Does this reply to your concerns? If we don't here from you within 2 weeks, we will regard the issue as closed. Regards, Felix Sasaki.
Wait: answer sent, wait respone.
Closed. No answer after 2 weeks.