https://github.com/servo/servo/wiki/Meeting-2014-10-13
kmc: [...] I was just reading about XML5 which uses an HTML parsing
algorithm; possibly we could use for XML that instead of wiring up a
proper XML parser.
There are two different things.
XML5 is a new parsing algorithm for XML that uses permissive error
handling (like HTML) instead of draconian (the yellow screen of death).
It is designed to be backward-compatible and relatively sane, without
all the weird behavior that HTML parsing has for compatibility with
existing content. There is a spec and a Python implementation, both made
in 2007, and a Ruby port made in 2011. Neither look like they’ve been
used much beyond the "interesting experiment" phase. I don’t know how
much code an XML5 parser would be able to share with an HTML parser, but
it’s a separate algorithm.
I also heard some noises about Blink wanting to use their HTML parser (I
suppose with some tweaks such as starting in a different mode) for
image/svg+xml, in order to get permissive error handling, and the SVG
Working Group being receptive to the idea. This is not XML5. It might
involve less engineering effort than XML5.
Is there anything other than SVG that might require an XML parser?
zwarich: On the web, is validity-checking for XML input required?
I don’t have evidence either way (and the only way to find out might be
to try it), but it sounds unlikely that real content relies on an entire
document failing to parse.
XML5 is entirely based on the assumption that we can give any meaning we
want to input sequences that used to fail to parse.
--
Simon Sapin
_______________________________________________
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
