W3C home > Mailing lists > Public > www-svg@w3.org > January 2006

Re: Request For Feedback: Traits

From: Anne van Kesteren <fora@annevankesteren.nl>
Date: Thu, 19 Jan 2006 18:36:32 +0100
Message-ID: <20060119183632.w22fl3hromsgcos8@webmail.annevankesteren.nl>
To: Robin Berjon <robin.berjon@expway.fr>
Cc: Jeff Schiller <codedread@gmail.com>, www-svg@w3.org

Quoting Robin Berjon <robin.berjon@expway.fr>:
> Strawman (not necessarily representing my opinion):
> ===================================================
> Maybe there's a mid-point whereby we can drop Traits in Tiny 1.2, and 
>  just leave it as an advantage of the folks who use JSR-226. Of  
> course, we don't lift anything from the full SVG DOM either, as that  
> would be too heavy. Instead, we stick to getAttributeNS and  
> setAttributeNS but specify require (or very strongly recommended)  
> normalisation of the values so that what is returned is easiest to  
> process and scripts don't have to handle the endless variety of  
> options that may be available to them. That, and perhaps a few  
> helpers, e.g. to parse a colour into an SVGColor. This sort of meets  
> the requirement for typed access midways (data is normalised and can  
> be upgraded to type easily) while reusing mostly what already exists. 
>  It has the default of inefficiency (you'll be converting to and from 
>  string every other line of code).

This sounds interesting. (Given that DOM Level 3 Core really allows
normalization.) Especially as the whole traits is not really that 
useful as has
been pointed out on the list. Personally I hope the SVG WG can address what is
needed here together with the CSS WG and possibly the Web APIs WG so we get
something that works across document languages...[1]




Anne van Kesteren
Received on Thursday, 19 January 2006 17:36:32 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:47:06 UTC