W3C home > Mailing lists > Public > www-svg@w3.org > December 2008

Re: [selectors-api] SVG WG Review of Selectors API

From: Jonas Sicking <jonas@sicking.cc>
Date: Mon, 8 Dec 2008 01:14:28 -0800
Message-ID: <63df84f0812080114y6761d9a8h9dde49cd569d1e2c@mail.gmail.com>
To: "Doug Schepers" <schepers@w3.org>
Cc: "public-webapps@w3.org" <public-webapps@w3.org>, www-svg <www-svg@w3.org>

> == Section 6. The NodeSelector Interface
>
>> > The caller must pass a valid group of selectors.
>
> That's an authoring requirement, explain how that is applicable?
>
>> > The group of selectors must not use namespace prefixes that need to be
>> > resolved.
>
> That also sounds like an authoring requirement. If it's an authoring
> requirement please mark it as informative, or as only applying to
> "conforming applications".

Aren't most W3C Recommendations intended as specifications for both
implementations and authors?

> Since NSResolver was taken out, please consider adding hardcoded namespace
> prefixes for svg and xhtml similar to how the empty and any namespaces are
> handled by this draft.
>
> Or alternatively forward the reader to DOM 3 XPath for the cases where the
> Selectors API falls short. Even if hardcoded namespace prefixes are added
> it'd still be a good idea to link to DOM 3 XPath, since it looks like
> Selectors API is unable to deal with arbitrary xml markup.

Do note that XPath can't deal with 'arbitrary xml markup' either as it
is not turing complete. (only when combined with XSLT it is).

However I do agree that having informative links to DOM 3 XPath is a
very good idea as it is a very similar technology.

/ Jonas
Received on Monday, 8 December 2008 09:15:04 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:41 GMT