W3C home > Mailing lists > Public > public-svg-wg@w3.org > October to December 2008

HTML5 and SVG

From: Erik Dahlström <ed@opera.com>
Date: Fri, 05 Dec 2008 11:24:21 +0100
To: "public-svg-wg@w3.org" <public-svg-wg@w3.org>
Message-ID: <op.ulopuvdxdhsuf5@gnorps.linkoping.osa>

Hello svg-wg,

To get HTML5<->SVG coordination going again after all the work done on 1.2T...
See the TPAC2008 minutes[1] for the joint discussion on SVG in HTML.

Extracting the goals from the SVG WG proposal[2]:

= SVG should remain XML when inline in HTML =

  Possibly we should rephrase this based on the discussion at TPAC. How about: Non-wellformed SVG markup may be error-corrected according to standard HTML parsing rules, but shouldn't validate (or in other words any fixups should be marked as parse errors).

= Should be able to take a conforming SVG document and paste its contents into an HTML document and have it be the same DOM. =

  There was consensus on this goal at TPAC[1].

= Should be able to take a conforming HTML document and copy the SVG fragment from it and paste it into a new file and that would be a conforming SVG document. =

  Hixie disagrees with this goal[3].

= Should be able to provide some sort of fallback mechanism for the SVG-in-HTML so that UAs that don’t know how to handle these SVG fragments will display the fallback. =

  I agree with Hixie that if there's an alternative way of providing fallback content then new syntax wouldn't be necessary. It is an important goal nontheless, and we should have it on the list.

= Should allow for unrestricted growth of the SVG language by the SVG specifications (though those specifications should also take into account the idea that SVG will, going forward, be used more commonly in concert with HTML). This means that there would be no "white list" of allowed SVG elements in HTML. It also means that the SVG spec should be more careful about element and attribute names going forward. =

  This is a fundamental goal that should definitely be high on the list. Hixie thinks it's not in conflict with the other goals.

= Should allow for SVG Fonts to be included in HTML, and ideally to be usable in HTML text. =

  Not discussed yet AFAIK, but should be on the goals list.

= Should attempt to avoid breaking existing text/html pages. However, this must be balanced with the need for a clean, sustainable architecture. =

  There's disagreement on the balance. Do we still want to push this goal? I think that having a clean sustainable architecture is good, but it's also a rather fuzzy goal.

= Should specify a tolerant error handling model for the SVG content =

  It may sound as if this goal is superseeded by the first goal above, so we might rephrase it: "Should require a tolerant error handling model for the rendering of the SVG content".

Please read and comment, we'll have this topic on the agenda for Monday next week.

/Erik

[1] http://www.w3.org/2008/10/24-html-wg-minutes.html#item05
[2] http://dev.w3.org/SVG/proposals/svg-html/svg-html-proposal.html
[3] http://lists.w3.org/Archives/Public/www-svg/2008Aug/0069.html

-- 
Erik Dahlstrom, Core Technology Developer, Opera Software
Co-Chair, W3C SVG Working Group
Personal blog: http://my.opera.com/macdev_ed
Received on Friday, 5 December 2008 10:27:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 5 December 2008 10:27:16 GMT