Re: SVG in HTML Review Comments

Jeff Schiller: 

>a) In reference to adjusting foreign attributes [1], does the algorithm
>depend on authors using the 'xlink:' prefix and not something else?  I think
>I've seen stray content around that uses 'xl:' for instance...

I think, in SVG1.1 this is only limited to xlink: due to the limitations of
the DTD, without DTD and therefore expecially in SVGT1.2 any prefix 
can be used and the behaviour must depend on the prefix defined 
by the author.


>b) Is attributeName missing from [2] ?

>c) Can you please add the textArea element [3] from SVGT 1.2?  Opera already
>supports this and it is a useful element to have.

Aren't all elements to be supposed to be useful somehow? Else there
would be no specification for them at all ;o) 
The list seems to contain only a few attributes with case sensitive names,
no elements at all. 

>d) Can you please add the solidColor element [4] from SVGT 1.2?

Aren't there some more in SVG1.1 or SVGT1.2?
The list seems to be taken from the Appendix M of SVG 1.1, but this list
seems to be incomplete itself, unfortunately...

Is it useful at all to list it in HTML 5, while this is specified anyway in
the related SVG recommendation?
And why to have specific HTML5 attributes with lowercase names with
some relations to some SVG attributes with case sensitive names?
Are they only applied to HTML5 elements? 
The SVG versions themselves have already defined rules how to 
process unknown attributes like 'calcmode' - there is no additional work 
required. Especially SVGT1.2 has rules for this without creating an error,
conforming user-agent have to follow. Therefore it will be never necessary
for SVG content to 'adjust' something.
Is it required to have something like 'calcmode' for any HTML5 element,
if no SMIL animation is currently defined in HTML5 and therefore authors
might use timesheets anyway?

Received on Friday, 11 April 2008 09:43:32 UTC