Note to editors - updating "status of CR" to reflect interoperability testing/date of estimated PR entrance

During the CR transition call, the Director felt we were not explicitly
clear enough about the status of the "browser profile", although he was
happy to resolved the issue. I will thus have to link to one of the
editorial notes in the spec's status with the proposed criteria below
and a reference to the fact all "algorithms" are non-normative. The goal
is to make sure implementers know right now that all algorithms are not
supported cross browser, but should know after PR.

In particular, the proposal was that we have two interoperable
implementations for every algorithm listed in the spec body. However,
the director is happy with algorithms being non-normative as long as
there is a clear browser profile of interoperable algorithms.
Interoperability will be determined by the test-suite. That is in line
with WG discussions. However, if folks in the WG have an objection,
please mention now.

We also estimated  to the WG that we exit PR at estimated date of "March
12 2015". Again, usually 3 months is the minimum to get a unified
test-suite together, and we're working in the fact that there is
Christmas vacation soon.

   cheers,
      harry

Received on Wednesday, 10 December 2014 14:25:22 UTC