Well, with some compromises HTML5 sounds feasible. My only concern is
maintaining such a library. In the ideal world I would have an
automated system that generates the library from a formal HTML
specification. Then ideally changes to the specification require a
simple rebuild. Unfortunately, looking at HTML 5 draft [1] I don't
really see a schema-like description that could be consumed by a
machine..
For this purpose XHTML wins by having a schema.
I have looked at WingBeats but have not figured out how much
validation if any does it do statically. Would be interesting to know.
Of course performing dynamic validation is a no-brainer, just using
the .NET schema validation code..
[1] http://www.w3.org/TR/html5/
--
Kind Regards,
Anton Tayanovskyy
WebSharper™ - type-safe JavaScript in F#
http://intellifactory.com