- From: Ola Andersson <Ola.Andersson@ikivo.com>
- Date: Fri, 10 Mar 2006 14:05:58 +0100
- To: <www-svg@w3.org>, <ian@hixie.ch>
Hi Ian, With backwards compatible we mean that conformant SVG Tiny 1.1 content will render the same in conformant SVG Tiny 1.2 User Agents as it did in conformant SVG Tiny 1.1 User Agents. We have clarified this in section 1.3. Thanks for your thorough review, please let us know shortly if this does not address your concerns. /The SVG WG ------- From: Ian Hickson <ian@hixie.ch> Date: Wed, 28 Dec 2005 21:33:53 +0000 (UTC) To: www-svg@w3.org Message-ID: <Pine.LNX.4.62.0512282133160.7669@dhalsim.dreamhost.com> It is not clear what is meant by "backwards compatible" in section 1.3's first sentence. * Does it mean old SVG 1.1 content is going to render in SVG 1.2 UAs as it did in SVG 1.1 UAs? * Does it mean new SVG 1.2 content is going to mostly render in SVG 1.1 UAs, with graceful fallback available when new features are used? * Does it mean old SVG 1.1 content updated to have the new SVG 1.2 version number is going to render in SVG 1.1 UAs without any user notifications? * Does it mean you can add new SVG 1.2 features to old SVG 1.1 documents (without updating the version number) and have the content be usable without user notifications in both old SVG 1.1 UAs and new SVG 1.2 UAs? Please clarify your use of the term "backwards compatible". -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Friday, 10 March 2006 13:05:34 UTC