Re: CR exit criteria and features at risk for HTML5

On Thu, Aug 16, 2012 at 4:35 PM, Glenn Adams <glenn@skynav.com> wrote:
> There are a number of formal standards organizations waiting on HTML5 to
> reach REC (in any form whatsoever) so that they may publish standards
> documents that formally reference HTML5.

Formally reference it for what purpose?

> From this perspective the goal is to get to REC ASAP regardless of the
> quality level (spec correctness, testing, etc), though of course the hope is
> that quality level will be as high as possible given other constraints. But
> nobody expects a spec this size to be bug free.

What will happen when downstream specifications you mention reference
an HTML spec that is incorrect: i.e. does not describe how web content
is best consumed? Mightn't this lead to a downstream spec requiring
documents to be produced that are not compatible with how browsers
have to operate to consume the web corpus?

What are the other constraints here? If correctness isn't what the
downstream specifications need, what is the content they do need? A
feature list? A markup vocabulary? IDL?

--
Benjamin Hawkes-Lewis

Received on Thursday, 16 August 2012 16:31:48 UTC