Prepare for CRS

[nigelmegitt]

PLEASE DO NOT MERGE until CR has been published

---

Closes #268.

• set specStatus to CR
• reference implementation report
• set crEnd
• Update SoTD to point to implementation report and include exit criteria
• add acknowledgments

---

Preview | Diff

[himorin]

just an idea, how about to have a link to WG/CGs?

[css-meeting-bot]

The Timed Text Working Group just discussed Prepare for CRS w3c/dapt#269, and agreed to the following:

• SUMMARY: Rebase as needed and use as the basis of the CRS transition request

The full IRC log of that discussion

<nigel> Subtopic: Prepare for CRS #269
<nigel> github: https://github.com//pull/269
<cpn> Nigel: I used the draft PR feature for this, similar to how Pierre does it with IMSC
<cpn> ... Once everything is merged, I'll rebase this, and that will be the bases for the CRS
<cpn> ... No action needed. It changes the spec status, refers to implementation report, etc. End date says 1 January for Proposed Recommendation, may need to adjust
<cpn> ... CR exit criteria us almost the same wording as for IMSC
<cpn> ... I cross-checked the wording against the charter. AFAICT it's compatible with that
<cpn> ... Unless there are comments, I'll assume it's ok
<cpn> (nothing)
<cpn> ... Please LMK if anyone should be added to Acknowledgements
<nigel> SUMMARY: Rebase as needed and use as the basis of the CRS transition request

[nigelmegitt]

As discussed in yesterday's TTWG call, I plan to rebase this when other PRs get merged so that the version we put out as CR is as up to date as possible. #278 is currently the only substantive (class 3) PR - currently all the others are class 1 or 2 changes.