progressing to CR for HTML Media Capture, Ambient Light Events, and Vibration API

I suggest we can soon start a CfC to progress HTML Media Capture, Ambient Light Events, and Vibration API to CR, as the LC period has ended.

This assumes  we agree on the resolution for the Vibration API comment [1] (or an alternative simple resolution), which I anticipate is not a problem.

In the case of HTML Media Capture and Ambient Light Events, I am not aware of any needed changes, apart from changing the status section to indicate that there have been no changes since
the Last Call publication and recording CR specific information as noted below. 

For the Vibration API the CR draft will need the resolution of the cancellation clarification and a status section update to note the editorial clarification [1] as well as a link to a new diff.

All drafts will need to include the following in the status section:

“The CR exit criterion is two interoperable deployed implementations of each feature, with no features marked as 'at-risk'. The group will create an Implementation Report (link).” (with appropriate link for each)

and (assuming a 2 week CfC starting this Thursday and ending 21 Aug, with publication 28 August)

" This document is intended to become a W3C Recommendation. 
...
 This Candidate Recommendation is expected to advance to Proposed Recommendation no earlier than 1 November 2014. All comments are welcome.
"

Please note that this is a ‘no-earlier than’ publication date.

Comments or suggestions? Does this work for the editors? (if not please suggest alternative)

I’d like to agree on Thursday both to the Vibration resolution and to start a CfC, so please comment on the list.

Thanks

regards, Frederick

Frederick Hirsch, Nokia
Chair DAP
@fjhirsch

[1] http://lists.w3.org/Archives/Public/public-device-apis/2014Aug/0000.html

Received on Monday, 4 August 2014 16:35:07 UTC