On 2/18/09 12:13 PM, rubys wrote:

I am concerned that the milestone dates given are unrealistic for any
specification that has relatively complete test suites. From what I've seen,
there are currently very few tests other than some parser tests associated
with hsivonen's references implementation.

Overall, I think it's better to have no new specification than a
specification without significant test coverage.

It's important to get the parsing and DOM specification complete enough that
it can specify correct and useful behavior for elements and attributes which
aren't currently specified. Thus, if <video> or <canvas> or <whatever> is
not included in the spec, the spec should at least be very specific about
the parsing of those unknown elements and the DOM tree that is constructed,
so that future specifications don't have to break the current specification.

Without a diff of sayrer's doc versus the large HTML5 spec, it's hard to
give detailed feedback, but I tend to agree that it's possible and prudent
to produce a specification in stages, by rolling out certain sections such
as parsing and error handling, and then dealing with new features as the
specification of those features matures and tests become available.

--BDS