> Speaking of migration paths, if we could define "subsets" of HTML+ and
> MIME types for them we could phase-in HTML+ by providing HTML & HTML+
> pages for things and letting the HTTP server & client decide which to
> fetch...
Sounds good to me. We could use a parameter on the content type, e.g.
Content-Type: text/html; level=2
Where level=0 (the default) is plain old HTML.
Thanks for the other comments. I will fix things up for the next revision
to the discussion document.
Dave