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

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.

Regards,
Glenn


On Fri, Jun 14, 2013 at 9:56 AM, Paul Cotton <Paul.Cotton@microsoft.com>wrote:

>  This is a Call for Consensus (CfC) to approve the parts of the following
> document that indicate which parts of the HTML5 specification can be
> considered interoperable as per the permissive CR exit criteria [1].  The
> items subject to this CfC are marked "Considered interoperable" and color
> coded in green in the document:****
>
> ****
>
> http://www.w3.org/html/wg/tests-cr-exit.html****
>
> ** **
>
> Silence will be taken to mean there is no objection, but positive
> responses are encouraged.   Objections should be made to specific entries
> in the document.  Objections of the form "features in 2.8.2.1
> HTMLAllCollection are not currently interoperable" MUST be accompanied with
> specific evidence of non-interoperability, otherwise such objections will
> not be accepted by the Chairs.****
>
> ** **
>
> If there are no objections by Monday July 15, this resolution will carry.
> ****
>
> ** **
>
> /paulc****
>
> HTML WG co-chair****
>
> ** **
>
> [1]
> http://dev.w3.org/html5/decision-policy/public-permissive-exit-criteria.html
> ** **
>
> ** **
>
> Paul Cotton, Microsoft Canada****
>
> 17 Eleanor Drive, Ottawa, Ontario K2E 6A3****
>
> Tel: (425) 705-9596 Fax: (425) 936-7329****
>
> ** **
>