[w3ctag/design-reviews] WG Revision: Dubbing and Audio description Profiles of TTML2 (for 2nd CRS) (Issue #1139)

himorin created an issue (w3ctag/design-reviews#1139)

### Specification

https://www.w3.org/TR/2025/CRD-dapt-20250801/

### Explainer

https://github.com/w3c/dapt/wiki/DAPT-Explained

### Links

- The WG's request for this TAG review: https://www.w3.org/2025/07/17-tt-minutes.html#efea
- TAG review of the previous version of this specification, if any: https://github.com/w3ctag/design-reviews/issues/897

####
- A description of what has changed since our previous review: https://www.w3.org/TR/dapt/substantive-changes-summary.txt (2nd part at From CRS (20250311))
- no web platform tests (not intended to be implemented by web browser), [test suites](https://github.com/w3c/dapt-tests/tree/main/dapt1) are prepared in tests' repository

- [Rename `#scriptRepresents` to `#scriptRepresents-root` for consistency (#296)](https://github.com/w3c/dapt/issues/296)
  - attribute name changed for consistency with other part of sepc
- [Remove the `#xmlId-div` feature (#297)](https://github.com/w3c/dapt/issues/297)
  - removed `xmlId-div` attribute originally introduced to specify target of script, but no longer required after spec development
- [Clarify usage of Represents and Script Represents (#262)](https://github.com/w3c/dapt/issues/262)
  - small refactor to define the inheritance on the `daptm:represents` attribute specifically
- [Allow Represents to apply to Text (#295)](https://github.com/w3c/dapt/issues/295)
  - allow using `daptm:represents` attribute to text elements (like span), with remark of splitting/duplicating these elements to match with scripts to be represented
- [Replace the `#scriptEventGrouping` extension feature with the TTML1 feature `#nested-div` (#303)](https://github.com/w3c/dapt/issues/303)
  - DAPT specific feature `scriptEventGrouping` is replaced with existing TTML feature


### The specification

- [ ] Follows the [Web Platform Design Principles](https://www.w3.org/TR/design-principles/).
- [ ] Includes Security and Privacy Considerations sections based on answers to the [Security/Privacy Questionnaire](https://www.w3.org/TR/security-privacy-questionnaire/).

### Where and by whom is the work is being done?

- GitHub repo:
- Primary contacts:
  - $name (@-mention), $organization/s, $role in developing specification
  - <!-- repeat as necessary, we recommend including group chairs and editors in this list -->
- Organization/project driving the specification:
- This work is being funded by:
- Primary standards group developing this feature:
- Incubation and standards groups that have discussed the design:
  - {{ABC CG}} <!-- Include a link to minutes or issues in this group if possible. -->
  - {{DEF WG}}


### Feedback so far

- Active horizontal reviews: https:// <!-- Link to an issue like https://github.com/webmachinelearning/webnn/issues/239, https://github.com/WebAssembly/spec/issues/1804, or https://github.com/w3c/did/issues/885, which itself links to the other horizontal reviews. If you haven't started the rest of the horizontal reviews, please consider doing so. -->
- Multi-stakeholder feedback:
  - Chromium comments:
  - Mozilla comments: https://github.com/mozilla/standards-positions/issues/NNN <!-- And/or other places they've given feedback -->
  - WebKit comments: https://github.com/WebKit/standards-positions/issues/NNN <!-- And/or other places they've given feedback -->
  - {{...include feedback/review from developers, implementers, civil society, and others}}
- Major unresolved issues with or opposition to this specification:
- Status/issue trackers for implementations: <!-- Include links to [Chrome Status](https://chromestatus.com/), [Mozilla's](https://bugzilla.mozilla.org/), [WebKit's Bugzilla](https://bugs.webkit.org/), and trackers for other implementations if those are known to you. -->


### You should also know that...

_No response_

<!-- Content below this is maintained by @w3c-tag-bot -->
---

Track conversations at https://tag-github-bot.w3.org/gh/w3ctag/design-reviews/1139


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1139
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1139@github.com>