W3C home > Mailing lists > Public > public-webapi@w3.org > December 2006

Re: Selectors API naming

From: Robin Berjon <robin@berjon.com>
Date: Wed, 20 Dec 2006 12:59:28 +0100
Message-Id: <CD93A585-B76D-417F-89DF-074F426746EC@berjon.com>
Cc: Dave Massy <Dave.Massy@microsoft.com>, "Web API WG (public)" <public-webapi@w3.org>, Chris Wilson <chris.wilson@microsoft.com>, Tina Duff <tinad@microsoft.com>
To: Anne van Kesteren <annevk@opera.com>

On Dec 19, 2006, at 21:50, Anne van Kesteren wrote:
> On Tue, 19 Dec 2006 21:35:17 +0100, Dave Massy  
> <Dave.Massy@microsoft.com> wrote:
>> For example if we map html as the prefix for XHTML in our document  
>> then wed write it like:
>> 	<html:table><html:tr><html:td></html:td></html:tr></html:table>
>> But then we can write a selector such as:
>> 	h|table > h|tr > h|td
>> With a NSResolver that maps h to the same namespace as the html in  
>> the primary document. This seems potentially confusing.
>
> This is similar to how CSS and DOM Level 3 XPath deal with it. It  
> allows scripts to be written independently from the markup. Seems  
> useful to me.

Not only is it useful but any other way of doing is radically  
useless. The whole point of prefixes is the indirection.

-- 
Robin Berjon - http://berjon.com/
------------------------------------------------------------------------
Change is inevitable except from a vending machine.
Received on Wednesday, 20 December 2006 12:00:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:56 GMT