ISSUE-117: Issues in Note in 2.1.2

Issues in Note in 2.1.2

State:

CLOSED

Product:

MLW-LT Standard Draft

Raised by:

Felix Sasaki

Opened on:

2013-02-11

Description:

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

Related Actions Items:

• ACTION-446 on Shaun McCance to Re-write example mentioned in issue-117 - due 2013-02-18, closed

Related emails:

1. [Minutes] MLW-LT call 2013-04-03 (from fsasaki@w3.org on 2013-04-04)
2. [Agenda] DRAFT MLW-LT call 3 April, noon UTC (from fsasaki@w3.org on 2013-04-03)
3. ISSUE-117: Issues in Note in 2.1.2 (from jirka@kosek.cz on 2013-03-29)
4. [Minutes] MLW-LT call 2013-02-11 (from fsasaki@w3.org on 2013-02-11)
5. mlw-lt-track-ISSUE-117: Issues in Note in 2.1.2 [MLW-LT Standard Draft] (from sysbot+tracker@w3.org on 2013-02-11)

Related notes:

Display change log