Re: version attribute of svg element

Tab Atkins Jr.:
> 
> More correctly: it doesn't matter what version you indicate, because
> user agents don't contain multiple rendering engines to support
> different versions.  Whatever you put there (or if you omit it),
> you'll get the latest version of SVG.
> 
> ~TJ

Versions of user agents change almost every month now.
But the meaning of a SVG document with some version indication
does not change at all, no matter, how they are currently interpreted or 
presented.
Their meaning is not time dependent.
Current viewers still have many gaps and bugs, therefore their 
presentation is often/typically a wrong interpretation of non trivial SVG 
documents using features they get wrong or  they do not interpret at all.
Therefore what current user agents do or not, is not a measure.
But of course, without a version indication no interpretation can be really 
wrong, just because the document is only arbitrary tag soup - exaggerated
of course, for those features, defined exactly in the same way in all 
recommendation versions, there is no conflict and the interpretation is still 
defined.
If the document is simple enough, the version indication does not matter, as 
long as new SVG versions do not create new conflicts in the future.
But how knows the future?
In practice we know - new versions will create new conflicts with older 
versions, not just new features.

Olaf

Received on Friday, 8 April 2016 20:24:45 UTC