W3C home > Mailing lists > Public > www-svg@w3.org > October 2005

Re: [SVGMobile12] Missing namespace puts document in error

From: Andrew Shellshear <Andrew.Shellshear@cisra.canon.com.au>
Date: Tue, 25 Oct 2005 11:28:39 +1000
Message-ID: <435D8A47.7090800@cisra.canon.com.au>
To: www-svg@w3.org
CC: SVG WG <w3c-svg-wg@w3.org>

On Fri, 20 May 2005 13:32:15 +0000 (UTC), Ian wrote:
> According to section C.4:
> # The outermost <svg> element must be defined in the SVG namespace (e.g., 
> # <svg xmlns="http://www.w3.org/2000/svg">); otherwise the document is in 
> # error.
> This seems like a bogus requirement. If the outermost <svg> element 
> _isn't_ in the SVG namespace, then it isn't an <svg> element, and is out 
> of the scope of this specification, surely.

The WG fully agrees with your statement about how (ideally) it should be 
unnecessary to say that the outermost svg:svg element must be defined in 
the SVG namespace. In fact, earlier SVG specifications indeed did not 
say this. However, an industry interoperability issue has developed 
where an early version of a leading implementation supported 'svg' 
elements without a proper namespace declaration, which caused a good 
amount of SVG content to be created that did not declare its namespace, 
which caused revisions of that implementation and other implementations 
to also support this (incorrectly formed) content.

Because of the history, the SVG WG feels it is necessary to explicitly 
say that the namespace declaration must be provided. If it were not for 
this history, we would not include the sentence you dislike.

Please let us know within two weeks if this does not satisfy your comment.
Received on Tuesday, 25 October 2005 01:29:15 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:47:04 UTC