RE: CR of Remote Playback API, review by 23 Aug

+1 to publish the Remote Playback API as a Candidate Recommendation.

However, and with apologies for reacting a bit late on this, I think we need to address i18n related issues, either with editorial notes or by closing issues with a comment indicating the reason for closure:
- #66 https://github.com/w3c/remote-playback/issues/66
- #70 https://github.com/w3c/remote-playback/issues/70

Issue #70 was identified as an issue to fix before moving to CR, but somehow fell through the cracks:
https://github.com/w3c/remote-playback/issues/73#issuecomment-300219580

Francois.

-----Original Message-----
From: Kostiainen, Anssi [mailto:anssi.kostiainen@intel.com] 
Sent: Wednesday, August 16, 2017 12:35 PM
To: public-secondscreen@w3.org
Subject: CfC: CR of Remote Playback API, review by 23 Aug

Hi All,

This is a Call for Consensus (CfC) to request publication of a Candidate Recommendation (CR) of the Remote Playback API at earliest 24 August 2017, with a 6-week CR review period ending 5 October 2017.

The staged CR snapshot is at:

https://w3c.github.io/remote-playback/?specStatus=CR;previousMaturity=WD;previousPublishDate=2016-11-07;crEnd=2017-10-05;publishDate=2017-08-24

No feature has been identified as being at risk.

For this specification to advance to Proposed Recommendation, two independent, interoperable implementations of each feature must be demonstrated, as detailed in the Candidate Recommendation exit criteria section.

Please let us know if you have any concerns by next Wed 23 August 2017. Silence is considered consent.

Thanks,

-Anssi (Second Screen WG Chair)

Received on Wednesday, 23 August 2017 19:48:12 UTC