 |
 |
 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Elliotte Harold writes:
> More to the point, HTML5 is not XML. It is not well-formed, and in
> general an HTML5 document cannot be made well-formed without crippling
> it by removing quite a few elements. Therefore XML schema languages
> really don't fit it at all.
So I've been trying to get my head around this, and reading the HTML5
parsing spec. [1]. I don't by any means understand it all as yet, but
I don't see any basis for what you say above. Could you give an
example HTML5 document where repair requires removing elements? All
the fixups I see in the parsing spec. are insertions (or ignoring of
unexpected end tags). . .
Thanks,
ht
[1] http://www.whatwg.org/specs/web-apps/current-work/#parsing
- --
Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
Half-time member of W3C Team
2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: ht@i...
URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged spam]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
iD8DBQFFdaZykjnJixAXWBoRAlGjAKCC9y+ZYI2fY9uz+JNE7TSqiXUYEQCeJx0R
z/zhv6JO1YmvoDbZpGsk+Nc=
=ZORq
-----END PGP SIGNATURE-----
|
 | 

|  |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
|  |
| |
 |
 |
 |