ISSUE-117: Issues in Note in 2.1.2

Issues in Note in 2.1.2

MLW-LT Standard Draft
Raised by:
Felix Sasaki
Opened on:

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:


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


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?

Related Actions Items:
Related emails:
  1. [Minutes] MLW-LT call 2013-04-03 (from on 2013-04-04)
  2. [Agenda] DRAFT MLW-LT call 3 April, noon UTC (from on 2013-04-03)
  3. ISSUE-117: Issues in Note in 2.1.2 (from on 2013-03-29)
  4. [Minutes] MLW-LT call 2013-02-11 (from on 2013-02-11)
  5. mlw-lt-track-ISSUE-117: Issues in Note in 2.1.2 [MLW-LT Standard Draft] (from on 2013-02-11)

Related notes:

RESOLUTION: accepted

David Filip, 3 Apr 2013, 12:37:45

CHANGE-TYPE: editorial

David Filip, 3 Apr 2013, 12:38:29

DECISION-DETAILS: Editorial action ACTION-475 pending. The note was dropped, hence example rework became irrelevant.

David Filip, 3 Apr 2013, 12:41:00

[fsasaki]: COMMENTER-RESPONSE: satisfied, see

8 Apr 2013, 09:59:06

Display change log ATOM feed

Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <>.
$Id: 117.html,v 1.1 2014-01-21 15:46:09 kahan Exp $