W3C home > Mailing lists > Public > public-fx@w3.org > January to March 2011

Re: Some practical issues integrating the SVG transform attribute with CSS transform properties

From: Dr. Olaf Hoffmann <Dr.O.Hoffmann@gmx.de>
Date: Sat, 26 Mar 2011 14:49:29 +0100
To: public-fx@w3.org
Message-Id: <201103261449.29712.Dr.O.Hoffmann@gmx.de>
Robert O'Callahan:
>We should not introduce version-dependent behavior to SVG, that would be a

SVG has already a few version-dependent features (or profile-dependent). 
With the second edition of SVG 1.1 there will one or two more (with the open 
question how authors can indicate that they write a new document following 
the second edition and not providing an old document, that existed before the 
work on the second edition begun.

But similar things apply for some features of the current CSS2.1 draft 
compared to CSS2.0 (used by SVG 1.1) - and of course there are even more
version-dependent features in HTML ;o)

Obviously, every time a newer version is not consistent with the an older
version of a recommendation, a feature becomes version-dependent.
Of course, several of such inconsistencies are not very relevant for authors,
because they never did work in any viewer due to bugs. As long as they
are able to indicate the version they mean, there is no problem to identify
later, what the intention of a document was, independent from the 
interpretation of specific viewer versions.

SVG transformations are often used in current SVG documents, therefore either
future recommendations are compatible with current SVG recommendations,
or version-dependent and profile-dependent viewer behaviour is necessary
for a huge amount of documents. 

Received on Saturday, 26 March 2011 13:50:05 UTC

This archive was generated by hypermail 2.3.1 : Monday, 22 June 2015 03:33:45 UTC