- From: Chris Lilley <chris@w3.org>
- Date: Fri, 21 Apr 2006 13:37:52 +0200
- To: "Anne van Kesteren" <annevk@opera.com>
- Cc: www-svg@w3.org
On Friday, April 21, 2006, 1:11:38 PM, Anne wrote: AvK> On Fri, 21 Apr 2006 13:06:29 +0200, Chris Lilley <chris@w3.org> wrote: >> As you say its out of scope for SVGT12 so I altered the subject line. AvK> Thanks. >> Ian posted some helpful comments about the lexical space and the value >> space. Could you rephrase your question for Full and clearly separating >> the lexical and value spaces? AvK> I can't find that e-mail unfortunately. He made the point several times,but this email expresses it well http://lists.w3.org/Archives/Public/www-svg/2006Feb/0105.html > Property computation has _nothing_ to do with the lexical space. It > doesn't make the slightest difference if the computed value is an RGB > colour or a hex colour or has three digits or six; a computed value is > a value without a canonical representation. > The computed value for 'fill' and 'stroke' should be an RGB triplet if > the specified value was a color or the 'currentColor' keyword, an > absolute IRI if the specified value was an IRI, or 'none' if the > specified value was 'none'. You may wish to also say something about > 'inherit' if you are ignoring the CSS model (which makes 'inherit' a > globally defined part of the syntax instead of a per-property value). AvK> What I'd like to know if the value AvK> of 'fill' (in CSS context) needs to be parsed as <color> or parsed as AvK> <SVGColor> or some such. The latter seems not really desirably... Are you taking the <color> definition from CSS1, CSS2, CSS 2.1 or CSS3: Color? -- Chris Lilley mailto:chris@w3.org Interaction Domain Leader Chair, W3C SVG Working Group W3C Graphics Activity Lead Co-Chair, W3C Hypertext CG
Received on Friday, 21 April 2006 11:37:50 UTC