W3C home > Mailing lists > Public > www-svg@w3.org > November 2005

Re: SVG12: animation of path data

From: Nandini Ramani <Nandini.Ramani@Sun.COM>
Date: Wed, 02 Nov 2005 01:54:33 -0800
To: derhoermi@gmx.net
Cc: www-svg@w3.org
Message-id: <43688CD9.9060606@sun.com>

Dear Bjoern,

Thank you for your comments on the SVG 1.2 draft::
http://lists.w3.org/Archives/Public/www-svg/2005Jul/0028.html

This was discussed by the WG and below are responses to your comments:

> It is not clear whether this is meant to prohibe discrete animation of
> different paths (e.g., set M...L... to M...C...), please change the
> draft such that this is clear; note that existing implementations fail
> to implement this restriction.
>
Discrete animation is *prohibited *and the wording in the spec. reflects 
this.

> It is not clear what it means for two instances of path data to have the
> same list of path data commands, may there be differnces with respect to
> absolete versus relative commands, implied commands, command parameters,
> etc. please change the draft such that equivalence is well-defined.
>
The spec has be reworded to say:

"Path data animation is only possible when each normalized path data
specification within an animation specification has exactly the same
list of path data commands as the d attribute after normalization."

And then normalization is defined as follows:

"This means that each path data specification and the d attribute would
have the exact same list of commands if normalized as defined in the
SVGPath interface."

Then the SVGPath interface defines how path data is normalized:

--------
The native implementations must support the following simplifications or
canonicalization of path segments. Any simplifications should be
lossless.

   * Relative commands (c, h, l, m, q, s, t, and v) must be converted
to their absolute counterparts.
   * Horizontal and Vertical lines (H, h, V, and v) must be converted
to general lines (L and l).
   * Translate command S to command C.
   * Translate command T to command Q
--------

> It is not clear what the note about "flags" and "booleans" is trying to
> cover, SVG Tiny 1.2 does not allow elliptical arcs where flags would be
> relevant, and booleans do not seem to exist in path data. Please remove
> this note or change the draft such that it is obvious why it is needed.
>
Since elliptical arcs are not a part of the SVG Tiny 1.2 spec, the WG 
agrees that the references to "flags" and "booleans" should be removed 
from the spec.

Please respond within two weeks if you are not satisfied.

Best Regards,
Nandini Ramani
Received on Wednesday, 2 November 2005 10:20:35 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:32 GMT