W3C home > Mailing lists > Public > public-multilingualweb-lt@w3.org > February 2013

mlw-lt-track-ISSUE-117: Issues in Note in 2.1.2 [MLW-LT Standard Draft]

From: MultilingualWeb-LT Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Mon, 11 Feb 2013 15:28:58 +0000
Message-Id: <E1U4vJS-0007wY-1a@tibor.w3.org>
To: public-multilingualweb-lt@w3.org
mlw-lt-track-ISSUE-117: Issues in Note in 2.1.2 [MLW-LT Standard Draft]

http://www.w3.org/International/multilingualweb/lt/track/issues/117

Raised by: Felix Sasaki
On product: MLW-LT Standard Draft

From
http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2013Feb/0048.html
http://www.w3.org/TR/its20/#basic-concepts-selection-global

The note in section 2.1.2 has problems. First, it points out
that only absolute location paths are allowed in the selector
attribute, then gives this as an example of a legitimate value:

  myElement/descendant-or-self::*/@*

But that's not a legitimate value, because *absolute* location
paths must start with a '/'.

It then points out that this isn't a valid pattern because it
contains a descendant-or-self component, and instead provides
the alternative

  *[self::myElement]/@* | myElement//*/@*

This uses '//', which is allowed in patterns, even though the
full descendant-or-self axis is not. But knowing that, we can
instead just rewrite the original as

  myElement//@*

On a more general note, what's the point of this note? If you
make an implementation that puts selectors into matches, and
therefore can't handle all absolute location paths, wouldn't
that be non-conforming? Is that something we ought to support
or encourage?

--
Shaun
Received on Monday, 11 February 2013 15:28:59 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 9 June 2013 00:25:08 UTC