- From: Shane McCarron <shane@aptest.com>
- Date: Thu, 03 Sep 2009 15:42:34 -0500
- To: Boris Zbarsky <bzbarsky@MIT.EDU>
- CC: Sam Ruby <rubys@intertwingly.net>, Anne van Kesteren <annevk@opera.com>, Manu Sporny <msporny@digitalbazaar.com>, HTML WG <public-html@w3.org>, RDFa Developers <public-rdf-in-xhtml-tf@w3.org>
Boris Zbarsky wrote: > > >> And I cannot use SVG elements that are namespace qualified and in the >> non-default namespace (e.g. xmlns:svg="...") > > Correct. > >> And if I omit the xmlns="..." it is still valid and meaningful >> because the parser magically knows it is an SVG element? > > Yes. Thanks. Okay, now for the obvious question. How does the system deal with conflicts between SVG element names and HTML element names (e.g., there is an 'a' element in SVG and an 'a' element in HTML)? In the future when SVG evolves and new elements are added, how will parsers know that the elements are from SVG as opposed from HTML or just gibberish? If there is HTML content embedded in an SVG block, how does the system know that? I assume the answer is "the parser deals with it", but doesn't this seem needlessly brittle to anyone else? -- Shane P. McCarron Phone: +1 763 786-8160 x120 Managing Director Fax: +1 763 786-8180 ApTest Minnesota Inet: shane@aptest.com
Received on Thursday, 3 September 2009 20:43:50 UTC