Re: CfC: Approve overview of testing in view of permissive CR exit criteria

Hi Glenn,

On 14/06/2013 06:55 , Glenn Adams wrote:
> CoxCom would like to see 4.8.9 and 4.8.10.12 marked "at risk" or at
> maximum, indicate only that some preliminary implementation work exists.
>
> Our primary reason for suggesting an at risk marking is because of the
> substantive changes being proposed to the text track and cue APIs and
> functions, and the uncertain status of the VTT related specification
> material.

What is listed as "at risk" in the document corresponds to what was 
listed as at risk when the CR was published. So we can't add anything to 
it at this point; but we can however do so later if there are still 
issues that justify doing so.

-- 
Robin Berjon - http://berjon.com/ - @robinberjon