Skip to content

Conversation

@nigelmegitt
Copy link
Contributor

@nigelmegitt nigelmegitt commented Dec 4, 2025

Closes #622

  • Explain use of multiple values in ttp:contentProfiles
  • Add DAPT to the list of compatible specifications in the overview
  • Add a DAPT interoperability section to appendix I including constraints and compatibility notes
  • Describe how DAPT metadata can be used in an IMSC context

Can be improved later to use definitions exported from DAPT, but directly cites non-exported definitions for the time being.

@css-meeting-bot
Copy link
Member

The Timed Text Working Group just discussed Add DAPT conformance signaling w3c/imsc#625, and agreed to the following:

  • SUMMARY: Group to review
The full IRC log of that discussion <nigel> Subtopic: Add DAPT conformance signaling #625
<nigel> github: https://github.com//pull/625
<nigel> Discussed in the context of w3c/dapt#333
<nigel> SUMMARY: Group to review

@palemieux
Copy link
Contributor

@nigelmegitt Do you want to edit this directly, or would you rather do so?

Does this also close #524?

@nigelmegitt
Copy link
Contributor Author

@nigelmegitt Do you want to edit this directly, or would you rather do so?

I'll take a swing at this.

Does this also close #524?

Good question. Unclear, I think, because the requirements on presentation implementations are undefined.

<p><a href="#resources-constraints"></a> prohibits embedded audio
within <a>Document Instances</a>.
A <a data-cite="dapt#dfn-dapt-document">DAPT document</a> that uses this feature
can therefore not be a conformant <a>Document Instance</a>.</p>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
can therefore not be a conformant <a>Document Instance</a>.</p>
are therefore not a conformant <a>Document Instance</a>.</p>

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done in 7c5d17f, but with "is" instead of "are" because it is in the singular.

* Explain use of multiple values in `ttp:contentProfiles`
* Add DAPT to the list of compatible specifications in the overview
* Add a DAPT interoperability section to appendix I including constraints and compatibility notes
* Describe how DAPT metadata can be used in an IMSC context
so it can be used in DAPT
Allows Respec to find links to things defined in DAPT even if they've not been exported yet.
@nigelmegitt nigelmegitt force-pushed the issue-0622/dapt-compat branch from 7c5d17f to ab1a27f Compare January 19, 2026 15:10
@nigelmegitt nigelmegitt requested a review from palemieux January 19, 2026 15:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add note about compatibility with DAPT

4 participants