Consolidated issues that may qualify as "controversial"

Based on my review of issues 1-45.

ISSUE-1: PINGPOST - hyperlink auditing requires use of unsafe HTTP  
ISSUE-2: PINGUI - Practicability of UI requirements for hyperlink  
ISSUE-4: html-versioning - HTML Versioning and DOCTYPEs
ISSUE-7: video-codecs - codec support and the <video> element
ISSUE-27:  rel-ownership - @rel value ownership, registry consideration
ISSUE-30: longdesc - Should HTML 5 include a longdesc attribute for  
ISSUE-31: missing-alt - What to do when a reasonable text equivalent  
is unknown/unavailable?
ISSUE-32: table-summary - how to provide a summary of a table, e.g.  
for unsighted navigation?

There is also a special case around ARIA:
ISSUE-14: aria-role - Integration of WAI-ARIA roles into HTML5
ISSUE-35: aria-processing - Need to define processing requirements for  
aria states and properties when used in html

I believe everyone agrees that the correct resolution is to integrate  
ARIA, but that is currently blocked on decisions by the PFWG. I don't  
think it would be meaningful or productive to label this issue as  
"controversial", rather, the HTML WG should make a formal request to  
PFWG to expedite the resolution of their pending issue.

I will put this growing list on the Wiki at some point soon. Once I  
get into issues that are less than 4 months old, I will start  
searching mailing list archives to see if they qualify.


Received on Wednesday, 12 August 2009 07:12:08 UTC