W3C home > Mailing lists > Public > public-xml-core-wg@w3.org > May 2005

Re: CSS selectors and xml:id

From: Chris Lilley <chris@w3.org>
Date: Mon, 9 May 2005 12:29:12 +0200
Message-ID: <192121618.20050509122912@w3.org>
To: ht@inf.ed.ac.uk (Henry S. Thompson)
Cc: Ian Hickson <ian@hixie.ch>, Bjoern Hoehrmann <derhoermi@gmx.net>, www-style@w3.org, <public-xml-core-wg@w3.org>

On Monday, May 9, 2005, 12:17:27 PM, Henry wrote:

HST> Ian Hickson writes:

>> The alternative would be for CSS to list every possible way of getting an
>> ID onto an element (<html:* id="">, <svg:* id="">, xml:id="", DTDs, 
>> Schemas, the DOM3 Core methods, etc), and then have this list repeated
>> every other place that needed to know about IDs (e.g. the definition of
>> <html:label for="", the getElementById() method, the text/html fragment
>> identifier definition, and so on and so forth).

HST> I would recommend the XPointer framework spec. [1] as a model here --
HST> it describes the deal for DTD and W3C XML Schema in some detail, then
HST> has a general clause covering 'other methods' for determining
HST> IDness. . .

HST> ht
HST> [1] http://www.w3.org/TR/xptr-framework/#shorthand

So, to be clear, you are suggesting that the CSS spec describe the DTD,
W3C XML Schema, and xml:id methods and then have a similar general
clause about 'other methods'?

 Chris Lilley                    mailto:chris@w3.org
 Chair, W3C SVG Working Group
 W3C Graphics Activity Lead
Received on Monday, 9 May 2005 10:29:29 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:34 UTC