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

Re: ITS 2.0, Selectors 4 and Selectors API 2

From: Liam R E Quin <liam@w3.org>
Date: Mon, 01 Jul 2013 23:26:36 -0400
Message-ID: <1372735596.9039.355.camel@slave.barefootcomputing.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: Daniel Glazman <daniel.glazman@disruptive-innovations.com>, "www-style@w3.org" <www-style@w3.org>, public-webapps <public-webapps@w3.org>, public-multilingualweb-lt-comments@w3.org, Felix Sasaki <fsasaki@w3.org>
On Mon, 2013-07-01 at 19:46 -0700, Tab Atkins Jr. wrote:
> If you want Selectors to be able to select attribute nodes, address it
> directly with a new selector.  This should not be smuggled in via the
> subject indicator.

Maybe it would be simpler to support an XPath() selector?

When you start using ITS you'll find other cases that get difficult with
existing CSS selectors, e.g.
  . partShortDescription elements whose id attribute value appears in
the list of id attributes in the "includes" attribute of a partsDiagram
element in the same section, and where that diagram has a
language="only" attribute on the "replacementCopies" element, and the
diagram issue year is earlier than 1996.

This sort of thing is fairly frequently written with XPath selectors
today, and is a plausible use case (e.g. the older exploded parts
diagram is only available in spanish, includes Spanish labels for the
parts that readers will have to match up to a table of part numbers, so
they need the same text in the diagram and in the table).

A rigorous comparison of XPath with CSS selectors would be worth doing;
piecemeal attempts to duplicate functionality don't seem worthwhile to
me. On the other hand I do agree that it sounds like some limitation in
CSS selector namespace handling could be alleviated.


Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/
Pictures from old books: http://fromoldbooks.org/
Ankh: irc.sorcery.net irc.gnome.org freenode/#xml
Received on Tuesday, 2 July 2013 03:26:39 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:32:28 UTC