- From: Atsushi Shimono (W3C Team) <atsushi@w3.org>
- Date: Tue, 30 Jan 2024 16:34:50 +0900
- To: "public-tt@w3.org" <public-tt@w3.org>
- Message-ID: <abfeab68-9095-4a95-b21c-26f851e52f4a@w3.org>
hi, just fyi on related procedure. On 2024/01/29 23:58, Nigel Megitt wrote: > TTWG, > > I noticed from the transition request <https://github.com/w3c/transitions/issues/590> to take IMSC-HRM out of CR that we did not apply the change needed to make it a Recommendation to which additional features can be added post-publication, using the streamlined process at https://www.w3.org/2020/Process-20200915/#revised-rec-features <https://www.w3.org/2020/Process-20200915/#revised-rec-features> Actual procedure is defined at following subsection of above link at: https://www.w3.org/2020/Process-20200915/#change-review Main requirements are: - Call review on list of changes/additions, for both AC review and IPR, over 60 days - limited to once per six month - implementation experience So, no need to pass / go through FPWD->CR, but need similar procedure as PR->REC. > Unfortunately this requires a change to the SOTD, and it /must/ be done before publication as a Rec. I have raised issue 78 <https://github.com/w3c/imsc-hrm/issues/78> on IMSC-HRM regarding this. > > Apologies for this oversight. If anyone has any objections to making the necessary change please let me know as soon as possible. > > Please consider this email a *Call for Consensus to make IMSC-HRM an updateable recommendation*. I will open a corresponding pull request shortly. > > As per our normal review process the review period for this CfC will end in 10 working days, on 2024-02-12. > > If I receive objections earlier, and there’s no prospect of resolving them other than by staying with the current draft, I will close the CfC without consensus and then allow the transition request to continue. > > Kind regards, > > Nigel >
Received on Tuesday, 30 January 2024 07:34:55 UTC