4 ms·
From what I read, it goes back to the HTML5 vs XHTML disputes. I think the story was something like this: One of the proposed advantages of XHTML was the plan
by xg15 9y ago
From what I read, it goes back to the HTML5 vs XHTML disputes. I think the story was something like this:
One of the proposed advantages of XHTML was the plan that at some point you'd be able to embed other XML dialects into XHTML - such as SVG.
HTML5 is famously not XML or SGML but a grammar of its own - and the ability to embed other languages was consciously dropped. However, the use-case of defining SVG images inline was considered important enough that it should be kept.
How to do so if HTML5 is not even XML? Just make a special exception for SVG and declare xml-that's-a-valid-svg a part of the HTML grammar.
Because it's a special case built into the language, there is no need for generic namespace declarations like in XML - so they can be dropped.