HTML5-warnings - request to publish as next heartbeat WD

I took some time this weekend to go through the HTML5 specification and
write warning language for features that are currently either
controversial or have long-standing bugs logged against them. It is
important that we draw attention to the least stable sections of the
HTML5 draft in order to align public expectation as we move towards Last

The only difference between this draft and Ian's latest draft are the
warnings - there are no new technical additions or deletions. Since
there are no new technical changes, there is no need to trigger a FPWD.

I am requesting three things of the HTML WG:

1. That this version is published as the next heartbeat
   Working Draft. Specifically, this is not a FPWD since there are no
   technical changes and thus there are no additional patent concerns.

2. Two other independent voices to support the publishing of this draft.
   Without those voices, this proposal cannot be considered for

3. A poll is created with two options:
   [ ] Publish Ian's latest draft to address the heartbeat requirement.
   [ ] Publish Ian's latest draft with Manu's warning language to
       address the heartbeat requirement.

   Whichever option that receives more than 50% of the vote will be
   published. A tie will result in Ian's latest draft being published.

Here is the complete diff-marked version:

Here is a link to every warning that was added to the HTML5
specification (this is the easiest way to review the changes):

If Ian updates his spec, I can regenerate and republish an
updated version of this document within an hour or two. The
non-diff-marked specification can be found here:

This version of the specification will be checked into W3C CVS when
Mike(tm) clears its addition to the repository.

-- manu

Manu Sporny (skype: msporny, twitter: manusporny)
President/CEO - Digital Bazaar, Inc.
blog: Bitmunk 3.1 Released - Browser-based P2P Commerce

Received on Sunday, 9 August 2009 13:33:18 UTC