- From: Henri Sivonen <hsivonen@iki.fi>
- Date: Mon, 5 Oct 2009 16:09:58 +0300
- To: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- Cc: Shelley Powers <shelleyp@burningbird.net>, "public-html@w3.org WG" <public-html@w3.org>, Adrian Bateman <adrianba@microsoft.com>, Sam Ruby <rubys@intertwingly.net>
On Oct 5, 2009, at 15:53, Leif Halvard Silli wrote: > Henri Sivonen On 09-10-05 14.09: > >> On Oct 3, 2009, at 02:45, Shelley Powers wrote: >>> I can speak for an SVG editor, Inkscape, which uses namespaced >>> elements and attributes to record information about the SVG it >>> produces. And before you mention using HTML comments, you should >>> spend time with an Inkscape SVG file, to see how extensive the >>> use of namespaced elements and attributes are in an Inkscape >>> managed SVG file. >> Inkscape is indeed a good example. >> It isn't clear to me why Inkscape couldn't serialize its state >> using a proprietary key-value syntax inside comment nodes instead >> of using attributes as the key-value syntax. > > > Another version of IE Conditional Comments, you mean? Can even be > used to hack a "namespace" solution ... HTML as we are forced to > speak it ... Doesn't sound lovely. Not at all. I'm not suggesting that comments change tree building in any way. I'm suggesting that authoring tools could locate their own comments in the parsed tree and parse the contents of the comments. (This would of course be highly inappropriate for any other kind of application except authoring tools storing data strictly for themselves. For example, I think putting RDF/XML in comments for Trackback is a bad design pattern.) -- Henri Sivonen hsivonen@iki.fi http://hsivonen.iki.fi/
Received on Monday, 5 October 2009 13:10:37 UTC