Re: SVG12: Locating animation targets

* Antoine Quint wrote:
>The behavior described in section 3.6 is consistent with the animations 
>work in SVG in general. Given that, I think it is important to match 
>this functionality in sXBL integration within SVG with regards to 
>custom animation elements.

I do not really see such consistency, the proposed model seems weird and
unsound to me. Maybe you can elaborate on this? Why would you expect my
examples to work as currently proposed? Why do you think it is sound to
require interpretation of the xlink:href attribute on custom elements
that might be inconsistent with the original semantics of the attribute?

>> It further seems that implementations are not required to expose the
>> animated value of attributes on custom elements, which means one cannot
>> write script code that considers new animated values which means that
>> animating attributes on custom elements would have little effect in
>> practise.
>
>In fact, implementations are required to expose animated values of 
>attributes on custom elements via traits. There is a <traitDef/> 
>element to specify the datatype of attributes on a custom element, a 
>complete set of APIs to access the attributes, and trait mutation 
>events to be notify of changes. In my opinion all the pieces are in 
>place for providing custom animation facilities in SVG+sXBL.

Maybe you can give me a hand and cite the sections that require this and
maybe even provide an example that helps to get a better idea of how one
should author such functionality? Your claims did not really change my
current impression, even after reviewing the relevant sections again.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de
68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/

Received on Monday, 17 January 2005 11:18:22 UTC