- From: Chris Lilley <chris@w3.org>
- Date: Thu, 26 Mar 2009 20:11:37 +0100
- To: Erik Dahlström <ed@opera.com>
- CC: public-svg-wg@w3.org
On Wednesday, March 25, 2009, 3:03:22 PM, Erik wrote: ED> - Color module I have checked in what I have, and portions are ready for some group discussion http://dev.w3.org/SVG/modules/color/master/SVGColor.html I have re-arranged some of the content so that each syntactic form is separately discussed in its own section, instead of being discussed in passing in the 'paint' section. Some other properties will also need updating with the ICC values, named colors etc so this will avoid needless duplication and makes the spec easier to read. The stuff about the 'deviceColor' element needs a careful look at what the use cases really are. The current wording waffles on about private namespaces and device URIs and I don't like it much. The actual use case, as I see it, is to say "here is some CMYK, don't color manage it". Using an IRI and some private namespaces to identify the device is not super useful. The part about color profiles and external images is still not very good; it was rather hidden before that a user agent should apply the profile that comes with the image. Instead, the text concentrates on overriding that profile which is much less useful. I also have a start on some test cases http://dev.w3.org/SVG/modules/color/test/svg/ it sees that support for sRGB fallback kcolors when the profile is not found, is not very good. ED> - Vector Effects module The color stuff took longer to sort out than I had anticipated, so the progress on this module has not been as much as I had expected on Monday. -- Chris Lilley mailto:chris@w3.org Technical Director, Interaction Domain W3C Graphics Activity Lead Co-Chair, W3C Hypertext CG
Received on Thursday, 26 March 2009 19:21:22 UTC