This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 3291 - Selector attribute and XSLT
Summary: Selector attribute and XSLT
Status: RESOLVED FIXED
Alias: None
Product: ITS
Classification: Unclassified
Component: ITS tagset (show other bugs)
Version: LastCall
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Felix Sasaki
QA Contact: Felix Sasaki
URL: http://www.w3.org/TR/2006/WD-its-2006...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-17 02:13 UTC by Karl Dubost
Modified: 2006-09-06 23:11 UTC (History)
0 users

See Also:

Attachments

Description Karl Dubost 2006-05-17 02:13:25 UTC 
"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?
Comment 1 Yves Savourel 2006-05-31 15:12:57 UTC 
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.
Comment 2 Felix Sasaki 2006-07-13 12:52:15 UTC 
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.
Comment 3 Felix Sasaki 2006-07-24 11:52:11 UTC 
Wait: answer sent, wait respone.
Comment 4 Yves Savourel 2006-09-06 23:07:53 UTC 
Closed. No answer after 2 weeks.