Input on the agenda

As per Sam's request, this e-mail is a report of the status of issues on 
the agenda that have actions due before 2009-03-19 (11 days from now), 
from the persective of the spec.


ISSUE-72 (WF2-superseded-by-HTML5): Need to make it publicly clear that 
http://www.w3.org/TR/web-forms-2/ is obsoleted by HTML5

   This seems done.


ISSUE-54 (doctype-legacy-compat): tools that can't generate <!DOCTYPE 
html>

ISSUE-31 (missing-alt): What to do when a reasonable text equivalent is 
unknown/unavailable?

ISSUE-20 (table-headers): Improvements to the table-headers algorithm in 
the HTML 5 spec

ISSUE-55 (head-profile): head/@profile missing, but used in other 
specifications/formats

ISSUE-60 (html5-xhtml-namespace): Reuse of 1999 XHTML namespace is 
potentially misleading/wrong

ISSUE-4 (html-versioning): HTML Versioning and DOCTYPEs

ISSUE-32 (table-summary): how to provide a summary of a table, e.g. for 
unsighted navigation?

ISSUE-13 (handling-http-401-status): Handling HTTP status 401 responses / 
User Agent Authentication Forms

   It's not clear to me what needs changing in the spec for these issues. 
   As far as I am aware all feedback has been taken into account. I am not 
   aware of any proposals that address any more of the use cases detailed 
   for these issues than the current text in the spec without causing 
   more harm than the spec as it stands today.


ISSUE-59 (normative-language-reference): Should the HTML WG produce a 
separate document that is a normative language reference and if so what 
are the requirements

   I am working on autogenerating such a document from the spec. I'm about 
   40% done.


ISSUE-37 (html-svg-mathml): Integration of SVG and MathML into text/html

   This is pending on a response from the SVG group. Implementation work 
   has been occurring in browsers, though, and this may become a moot 
   point if those ship.


ISSUE-56 (urls-webarch): Assess whether "URLs" section/definition 
conflicts with Web architecture

   This is pending work by DanC to split the controversial part out into 
   an I-D for RFC standards track.


ISSUE-63 (origin-req-scope): Origin header: in scope? required for this 
release?

   This is pending work by Adam Barth to create an I-D for RFC standards 
   track that defines what HTML5 has to do.

HTH,
-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

Received on Monday, 9 March 2009 06:53:59 UTC