-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PR Request for IMSC Hypothetical Render Model (imsc-hrm) #590
Comments
/cc @nigelmegitt @gkatsev |
Sorry for the late notice, I think I'm going to have to ask you to hold this while we return to the question of if this is an updateable rec or not - I only noticed from this transition request that it is not but I see now that we did not put the right text into the SOTD. I would like to return this question to the TTWG and check if we have consensus to change it before we publish as a Rec. Issue raised as w3c/imsc-hrm#78. |
Cfc concluded at https://lists.w3.org/Archives/Public/public-tt/2024Feb/0002.html with no objections. @himorin please could you adjust this transition request to change "Will new features be allowed to be incorporated in the Recommendation?" to "Yes" and then proceed, i.e. take this off "hold"? |
changed with adding a link to the resolution. |
The Working Group reported using around 28,502 documents against one of the validating implementation (as discussed with the Council). This was done in addition to using 2 validating implementations against the hand-crafted test suite. Approved, but we'd like to see the final SOTD before publication (@himorin , pleaqse cc @ylafon and me on the publication request). |
@plehegar I don't think we're expecting to make any particular changes to the SOTD relative to w3c/imsc-hrm#77 - is there something you are hoping to be present in that text, or removed from it? For example the addition of some description of how the CR exit criteria were met? |
Nope. Just wanted to make sure the SOTD is finalized porperly. |
Late change to the SotD agreed, confirmed at https://lists.w3.org/Archives/Public/public-tt/2024Feb/0007.html - removes the CR exit criteria, which were left in by oversight. I think this means we can continue with the transition, @himorin @plehegar as per w3c/imsc-hrm#77. |
@nigelmegitt @plehegar A package installed at I'll send out publication request shortly. |
Document title, URLs, estimated publication date
IMSC Hypothetical Render Model
TR: https://www.w3.org/TR/imsc-hrm/
ED: https://w3c.github.io/imsc-hrm/spec/imsc-hrm.html
Abstract
https://w3c.github.io/imsc-hrm/spec/imsc-hrm.html#abstract
Status
https://w3c.github.io/imsc-hrm/spec/imsc-hrm.html#sotd
Will new features be allowed to be incorporated in the Recommendation?
Yes.
(Resolution of CfC: https://lists.w3.org/Archives/Public/public-tt/2024Feb/0002.html)
Link to group's decision to request transition
CfC: https://lists.w3.org/Archives/Public/public-tt/2024Jan/0000.html
Resolution: https://lists.w3.org/Archives/Public/public-tt/2024Jan/0005.html
Changes
https://w3c.github.io/imsc-hrm/spec/imsc-hrm.html#changes-since-the-first-candidate-recommendation
Requirements satisfied
IMSC-HRM was initially developed as a part of IMSC recommendation, so requirements are satisfied during IMSC development.
Dependencies met (or not)
yes
Wide Review
before 1st CRS
tag: w3ctag/design-reviews#788
a11y: w3c/a11y-request#19
i18n: w3c/i18n-request#167
privacy: w3cping/privacy-request#65
security: w3c/security-request#18 (no action taken)
No new feature added, one at-risk feature removed, after 1st CRS.
Issues addressed
https://github.com/w3c/imsc-hrm/issues?q=is%3Aissue+is%3Aclosed
Formal Objections
none
Implementation
https://www.w3.org/wiki/TimedText/IMSC-HRM-1ED-Implementation-Report
lists both:
Patent disclosures
https://www.w3.org/groups/wg/timed-text/ipr/#current-disclosures
The text was updated successfully, but these errors were encountered: