<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><BR><DIV><DIV>On Sep 26, 2007, at 12:49 AM, Tor Lillqvist wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica"><space name="RGB"></FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica"><SPAN class="Apple-converted-space"> </SPAN><color name="blue">0 0 1</color></FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica"></space></FONT></P> </BLOCKQUOTE></DIV><BR><DIV>Looking to "XML-ness" of things, there are a few points that come to mind.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>The actual contents of the color there are just a free-form text blob. Not as handy.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Also... I would not think that a color space would be the "thing that logically hold a bunch of colors". Yes, colors are in a colorspace, but that is more of an attribute of the colors.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><color name="blue" colorspace="2ndFloorCMYK"></DIV><DIV> <sRGB r='0' g='0' b='0'/></DIV><DIV></color></DIV><DIV>...</DIV><DIV><colorspace name="2ndFloorCMYK" xlink:href="2nd_floor.icm"/></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>So in this refactoring, the <color> element is the key container. One attribute of any color is it's functional name, so that is there. Another attribute of a color is the colorpsace it is in. Then I've added the actual RGB value as an <sRGB> element, since that's a handy fallback. And since it is a child element, it's easily optional.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Hmm... but as I think about it, the colorspace is not really an attribute of that swatch, but of a specific implementation of it.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><color name="blue"></DIV><DIV> <icc-color space="2ndFloorCMYK" val="0, 0.75, 0, 1"/></DIV><DIV> <sRGB r='0' g='0' b='0'/></DIV><DIV></color></DIV><DIV>...</DIV><DIV><colorspace name="2ndFloorCMYK" xlink:href="2nd_floor.icm"/></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Then another XML consideration comes up. What about internationalization? Is there any data that might be translatable or perhaps could use multiple variants? If so, then an element is warranted instead of an attribute. I could see that a name would be very useful. Also we would want to avoid overloading the term "name"...</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><color name="blue"></DIV><DIV> <label lang="en">Blue</label></DIV><DIV> <label lang="es">Azul</label></DIV><DIV> <label lang="en_US_SoCal">glassy</label></DIV><DIV> <icc-color space="2ndFloorCMYK" val="0, 0.75, 0, 1"/></DIV><DIV> <sRGB r='0' g='0' b='0'/></DIV><DIV></color></DIV><DIV>...</DIV><DIV><colorspace name="2ndFloorCMYK" xlink:href="2nd_floor.icm"/></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><BR class="khtml-block-placeholder"></DIV></BODY></HTML>