This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 7379 - HTML5 should reference SVG1.1 as well as SVG1.2T
Summary: HTML5 should reference SVG1.1 as well as SVG1.2T
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Keywords: NE
Depends on:
Reported: 2009-08-20 06:39 UTC by Maciej Stachowiak
Modified: 2010-10-04 14:48 UTC (History)
3 users (show)

See Also:


Description Maciej Stachowiak 2009-08-20 06:39:36 UTC
HTML5 has a reference to SVG 1.2T, but browsers are implementing most if not all of SVG 1.1, and the parsing spec is meant to cover it, so it seems an additional SVG 1.1 reference would be appropriate.
Comment 1 Ian 'Hixie' Hickson 2009-09-17 22:31:48 UTC
The only reason I reference 1.2 Tiny specifically and not an unversioned URL is that the definition of how to process <svg:script> wasn't included in SVG until SVG Tiny 1.2, and the general unversioned /TR/SVG URL is still 1.1.

If it wasn't for that, I wouldn't be referencing any version at all. HTML5 doesn't require any particular version of SVG, and I don't think coupling them together is a good idea, since it means that updating one implies updating the other (we had that problem with SVG and CSS2, if you recall).
Comment 2 Maciej Stachowiak 2010-03-14 14:49:48 UTC
This bug predates the HTML Working Group Decision Policy.

If you are satisfied with the resolution of this bug, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:

This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment.