W3C home > Mailing lists > Public > public-html@w3.org > March 2011

Re: ISSUE-9 video-accessibility: Call for Consensus to close in favor of specific issues, or Alternate/Counter-Proposals

From: Maciej Stachowiak <mjs@apple.com>
Date: Wed, 02 Mar 2011 21:48:21 -0800
Cc: 'HTML WG' <public-html@w3.org>, "'Michael(tm) Smith'" <mike@w3.org>, 'Philippe Le Hegaret' <plh@w3.org>
Message-id: <170DC602-3735-40FE-A4DA-C8116C1F330D@apple.com>
To: John Foliot <jfoliot@stanford.edu>

Hi John,

Thanks for your comprehensive reply.

On Mar 2, 2011, at 5:10 PM, John Foliot wrote:

> 
> It is thus the umbrella Issue under which all other media accessibility
> related outcomes have "lived". Along with the 2 open Issues noted above,
> there are other media accessibility bugs currently in the system that
> reference Issue 9 (#11593, possibly related to Issue 152), as well as one
> request (by me) to escalate Bug 10693 (bug first submitted 2010-09-23) to
> an Issue.
> 
> A concern surfaced in our discussion that in many instances, when an Issue
> is closed, it also closes/resolves all child Issues and bugs that
> reference that Issue. (This might be a mechanical operation done by the
> bug-tracker/Issue tracker). 

In this case, no other bugs or issues would be closed as a side effect. In particular:



"the <track> @kind attribute should include the all of the identified accessibility content types"
<http://www.w3.org/Bugs/Public/show_bug.cgi?id=11593>

 - This bug will remain open, and can be pursued individually, or assicuated with ISSUE 152.

"Need a means for navigating between related timed tracks of media elements"
<http://www.w3.org/Bugs/Public/show_bug.cgi?id=10693>

 - This bug can be pursued individually, and escalated to its own issue.


Other existing or new bugs can continue to be processed as well.

All that would be closed is ISSUE-9 itself, since the more specific bugs and issues remove the need for this placeholder umbrella issue.

I hope this answers your questions.

Regards,
Maciej


P.S. bug 10693 is in the inconsistent state of being reopened and also marked TrackerIssue. I believe one of the following would be appropriate:

(1) Remove TrackerIssue, and leave the bug open until the editor resolves it again.
(2) Put the bug back in "resolved" state and mark as TrackerRequest, to raise a new issue specifically about navigation between related timed tracks.

Please let the chairs know which of these is intended, or make the change yourself.
Received on Thursday, 3 March 2011 05:49:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:23 GMT