RE: FW: ISSUE-204, ISSUE-30 and ISSUE-203 processing order

> I request that ISSUE-194 please be placed after ISSUE-30 in the Co-Chairs plan 

The Chairs do not agree with this request and are not going to change the processing order of these issues.

The Chairs do not believe that a decision on ISSUE-30, regardless of which way it came down, would be likely to materially affect any of the three ISSUE-194 transcript proposals or the final decision on that issue. 

The Chairs believe that we should only add dependencies when a decision on one issue would likely significantly change at least one of the Change Proposals for another issue, or alternately would be likely grounds for a reopen request if the issues were decided in the other order.  We don't think either applies here.

/paulc
HTML WG co-chair

Paul Cotton, Microsoft Canada
17 Eleanor Drive, Ottawa, Ontario K2E 6A3
Tel: (425) 705-9596 Fax: (425) 936-7329

-----Original Message-----
From: Laura Carlson [mailto:laura.lee.carlson@gmail.com] 
Sent: Wednesday, July 18, 2012 8:03 AM
To: Paul Cotton
Cc: HTML WG
Subject: Re: FW: ISSUE-204, ISSUE-30 and ISSUE-203 processing order

Hi Paul,

I request that ISSUE-194 please be placed after ISSUE-30 in the Co-Chairs plan and that the 194 survey be put on hold until after
ISSUE-30 is decided in LC1. This is not only because both issues have identical design decisions to adjudicate with regard to on-page IDREF verses off-page URL attribute functionality but also because one
ISSUE-194 proposal [1] specifically cites longdesc and visual presentation in its rationale.

The ISSUE-194 no change proposal makes assumptions based the ISSUE-30 outcome i.e., "If we didn't have a transcript, but a different long description document available, the transcript link would be empty and the long description link would have the link. Therefore, the transcript link does not provide any additional information and is therefore redundant."

That proposal goes further assuming that a "replacement for @longdesc is under discussion for HTML.next". This statement is prejudicial to ISSUE-30. longdesc may be expanded in LC2. [2]

A positive outcome to include longdesc in HTML5 for ISSUE-30 will remove assumptions. In any event is better not to base  decisions on assumptions [3].

Also the ISSUE-30 change proposal to include longdesc supplies spec text to HTML5's 10.6.1 rendering section which addresses visual presentation and could be added to  the @transcriptURL proposal.

Thank you for your consideration.

Best Regards,
Laura

[1] http://www.w3.org/html/wg/wiki/ISSUE-194/NoChange

[2] http://lists.w3.org/Archives/Public/public-html/2012Apr/0211.html

[3] "Errant Assumptions are the Root Cause of All Poor Decisions." - Peter Drucker

On Tue, Jul 17, 2012 at 2:14 PM, Paul Cotton <Paul.Cotton@microsoft.com> wrote:
> FYI.
>
>
>
> Paul Cotton, Microsoft Canada
>
> 17 Eleanor Drive, Ottawa, Ontario K2E 6A3
>
> Tel: (425) 705-9596 Fax: (425) 936-7329
>
>
>
> From: Paul Cotton
> Sent: Tuesday, July 17, 2012 3:14 PM
> To: public-html@w3.org
> Subject: ISSUE-204, ISSUE-30 and ISSUE-203 processing order
>
>
>
> The WG Chairs have decided that we will process the following three 
> issues in the following order:
>
>
>
> a) ISSUE-204: aria-hidden
>
> http://dev.w3.org/html5/status/issue-status.html#ISSUE-204

>
>
>
> b) ISSUE-30: longdesc
>
> http://dev.w3.org/html5/status/issue-status.html#ISSUE-030

>
>
>
> c) ISSUE-203: media-descriptions
>
> http://dev.w3.org/html5/status/issue-status.html#ISSUE-203

>
>
>
> To be clear this means we will process ISSUE-204 first, then ISSUE-30 
> and then ISSUE-203.  After processing one issue we will then determine 
> the possible impact on the change proposals for the remaining issues.
>
>
>
> Please let us know if you have any objections to this plan.
>
>
>
> /paulc
>
> HTML WG co-chair
>
>
>
> Paul Cotton, Microsoft Canada
>
> 17 Eleanor Drive, Ottawa, Ontario K2E 6A3
>
> Tel: (425) 705-9596 Fax: (425) 936-7329
>
>



--
Laura L. Carlson

Received on Thursday, 19 July 2012 15:27:32 UTC