CR Request for Dubbing and Audio description Profiles of TTML2 - dapt

[himorin]

Document title, URLs, estimated publication date

Dubbing and Audio description Profiles of TTML2
https://www.w3.org/TR/dapt/
will pick earliest, 2025-02-18 or something

Abstract

https://www.w3.org/TR/dapt/#abstract

Status

https://www.w3.org/TR/dapt/#sotd

Link to group's decision to request transition

CfC: https://lists.w3.org/Archives/Public/public-tt/2024Oct/0001.html
resolution: https://www.w3.org/2024/11/21-tt-minutes.html#ffff

Changes

https://w3c.github.io/dapt/substantive-changes-summary.txt
at /TR/: https://www.w3.org/TR/dapt/substantive-changes-summary.txt

Requirements satisfied

https://www.w3.org/TR/dapt-reqs/
yes

Dependencies met (or not)

no in radar

Wide Review

• initial around FPWD
  • DAPT 2023-07-18 a11y-request#66
  • Tag review request for the "Dubbing and Audio description Profiles of TTML2" w3ctag/design-reviews#897
  • DAPT 2023-09-13 i18n-request#217
  • DAPT 2023-07-31 w3cping/privacy-request#122
  • DAPT 2023-07-31 / 2024-11-07 > 2025-01-07 security-request#59
• delta for changes since FPWD
  • DAPT 2023-07-31 / 2024-11-07 > 2025-01-07 security-request#59 (one security-needs-resolution has been filed with non-blocking for this CRS)
  • DAPT 2023-09-13 i18n-request#217

Issues addressed

https://github.com/w3c/dapt/issues?q=is%3Aissue%20state%3Aclosed

Formal Objections

no

Implementation

under preparation, to be implemented at https://www.w3.org/wiki/TimedText/DAPT_Implementation_Report

Patent disclosures

https://www.w3.org/groups/wg/timed-text/ipr/

[himorin]

/cc @nigelmegitt @cconcolato @gkatsev

[plehegar]

Latest i18n review is from 2024-11.

[plehegar]

Noted w3c/dapt#281

[plehegar]

We see that APA indicated to wait for a review request in September 2024. It's not clear if the loop with APA was entirely closed or not.

cc @ruoxiran @matatk

[plehegar]

We note that there are several features at-risk noted in the draft status. But, what are the CR exit criteria ? and what's the CR review deadline?

[nigelmegitt]

Latest i18n review is from 2024-11.

All the changes merged since then were either editorial or just formalised features already in the specification.

[nigelmegitt]

We note that there are several features at-risk noted in the draft status. But, what are the CR exit criteria ? and what's the CR review deadline?

See w3c/dapt#269 - we have not updated the CR exit date again because we didn't know when publication would happen. I would suggest setting it as early as the Process allows since it is a "not before" date, minimum one month I think. I would not make it more than 2 months after publication date, because that seems needlessly restrictive.

The CR exit criteria in that pull request's SOTD are:

For this specification to exit the CR stage, at least 2 independent implementations of every feature defined in this specification but not already present in [TTML2] need to be documented in the implementation report. The Working Group does not require that implementations are publicly available but encourages them to be so.

[nigelmegitt]

We see that APA indicated to wait for a review request in September 2024. It's not clear if the loop with APA was entirely closed or not.

cc @ruoxiran @matatk

I believe the action was on APA not TTWG.

[plehegar]

We note that there are several features at-risk noted in the draft status. But, what are the CR exit criteria ? and what's the CR review deadline?

See w3c/dapt#269 - we have not updated the CR exit date again because we didn't know when publication would happen. I would suggest setting it as early as the Process allows since it is a "not before" date, minimum one month I think. I would not make it more than 2 months after publication date, because that seems needlessly restrictive.

Thanks. We interpret "need to be documented" as documenting that it passes the test :).

[plehegar]

besides hearing from APA, this transition seems fine.

[nigelmegitt]

We interpret "need to be documented" as documenting that it passes the test :).

Sure. If an implementation doesn't pass the test for some feature then I wouldn't claim that it is an implementation of that feature!

Also we plan to create a test suite and use it to verify that such feature implementation.