- From: Henry S. Thompson <ht@inf.ed.ac.uk>
- Date: Mon, 09 May 2005 11:17:27 +0100
- To: Ian Hickson <ian@hixie.ch>
- Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, Chris Lilley <chris@w3.org>, www-style@w3.org, public-xml-core-wg@w3.org
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). I would recommend the XPointer framework spec. [1] as a model here -- it describes the deal for DTD and W3C XML Schema in some detail, then has a general clause covering 'other methods' for determining IDness. . . ht [1] http://www.w3.org/TR/xptr-framework/#shorthand -- Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh Half-time member of W3C Team 2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440 Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk URL: http://www.ltg.ed.ac.uk/~ht/ [mail really from me _always_ has this .sig -- mail without it is forged spam]
Received on Monday, 9 May 2005 10:18:33 UTC