http references in an OT font's SVG docs (xmlns, dtd)

Cam, Chris, Vlad, others:

1.
Does the requirement to ignore external references when processing SVG docs in an SVG-in-OT font include the dtd and xmlns http references in the header? Here's an example glyph from GeckoEmoji.ttf (http://people.mozilla.org/~jkew/opentype-svg/GeckoEmoji.html):

<![CDATA[<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE svg  PUBLIC '-//W3C//DTD SVG 1.1//EN'
'http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd'>   ### <== dtd
<svg ...
xmlns="http://www.w3.org/2000/svg"         ### <=== xmlns
xmlns:xlink="http://www.w3.org/1999/xlink" ### <=== xmlns
> ...

2.
Also, since https://www.microsoft.com/typography/otspec/svg.htm says the required UA stylesheet must have:

   @namespace svg url(http://www.w3.org/2000/svg)

there should be no need for the SVG doc in the font itself to have an xmlns (as in the above example), right (unless, presumably, it’s different from the UA stylesheet namespace)?

3.
Also, is a dtd needed at all in the font's SVG doc? Hin-Tak Leung (who's working on the Microsoft Font Validator's SVG-in-OT support) brought this up a couple of days ago on the OT list. He said, re. the dtd in Gecko Emoji:

<<<
this causes the XML
parser to go online to fetch the dtd from www.w3.org to actually validate
the XML against the dtd. I know this behavior is technically correct,
and XML parsers are supposed to validate whenever possible - and
possibly cache the DTD whenever possible. But mono's XML parser
happens not to do that, and hammering www.w3.org repeatedly for each
glyph (or each run at least, it seems and it chokes on alternative runs
when failing to fetch) seems stupid so I turn the validation feature off
mono's parser manually.
>>>

Thanks,

Sairus