Closing out old and "bogus" issues

I've been keeping Dan's guidance on issues vs. actions in the back of my head:
http://lists.w3.org/Archives/Public/public-html-wg-issue-tracking/2007Dec/0002.html

Several of our issues are better suited towards actions (or nothing at
all) given that email:

* Handling HTTP status 401 responses / User Agent Authentication Forms
- http://www.w3.org/html/wg/tracker/issues/13
* Vertical tab preprocessing for media queries -
http://www.w3.org/html/wg/tracker/issues/17
* Space in pseudo-BNF for accept attribute for file upload controls -
http://www.w3.org/html/wg/tracker/issues/21
* Web Forms 2 File Upload type & subtype RFC Reference should refer to
RFC 2616 - http://www.w3.org/html/wg/tracker/issues/22
* "External conformance dependency in forms" -
http://www.w3.org/html/wg/tracker/issues/23
* "spec requires non-compliant Referer header" -
http://www.w3.org/html/wg/tracker/issues/33

You can blame me for a few of these. :(

Should I go ahead and close these out? Ian's done a damn good job of
filing away emails concerning spec minutia and addressing them at
later time when he's revisited the relevant portion of the
specification.

I do feel like there are larger issues one could glean from some of
the ones listed above... they tend to involve grey areas that define
the boundaries of the HTML5 spec though. (HTML5 and relation to other
specifications... where one begins and the other takes over... though
it is rarely that black & white.)

Shawn

Received on Friday, 23 May 2008 02:21:27 UTC