Does the W3C DAPT dubbing/audio-description script format (a public standard) have a performance-intent field, and how does it keep that apart from timing and from mix/M&E handling?
At W3C DAPT Candidate Recommendation Draft 26 June 2026, timing, free-text script-event annotation, character/text, and mixing instructions are four separate data-model areas. There is no dedicated emotion, effort or breath field: the closest slots are the free-text Script Event Description (ttm:desc), its small provisional descType registry (pronunciationNote, scene, plotSignificance) and x- user-defined types, plus Rate/Pitch for synthesized speech. No M&E or stem concept appears in the document; mixing is gain/pan. So an agent can use DAPT to keep three kinds of data apart, but must define its own performance-intent convention.
At W3C DAPT Candidate Recommendation Draft 26 June 2026, timing, free-text script-event annotation, character/text, and mixing instructions are four separate data-model areas. There is no dedicated emotion, effort or breath field: the closest slots are the free-text Script Event Description (ttm:desc), its small provisional descType registry (pronunciationNote, scene, plotSignificance) and x- user-defined types, plus Rate/Pitch for synthesized speech. No M&E or stem concept appears in the document; mixing is gain/pan. So an agent can use DAPT to keep three kinds of data apart, but must define its own performance-intent convention.
Curator qualifications: W3C DAPT CRD (2026-06-26) keeps timing, free-text script-event description (ttm:desc with descType: pronunciationNote, scene, plotSignificance, x- types), character/text and mixing instructions as separate areas; no dedicated emotion/effort/breath field.
Evidence status: statements located in the cited sources by a correlated desk review (Claude); not executed; not independently reviewed.
Structured fields
{
"citations": [
{
"url": "https://www.w3.org/TR/dapt/",
"note": "candidate evidence excerpts"
}
]
}Evidence claims
- [sourced_fact] At W3C DAPT Candidate Recommendation Draft 26 June 2026, timing, free-text script-event annotation, character/text, and mixing instructions are four separate data-model areas. There is no dedicated emotion, effort or breath field: the closest slots are the free-text Script Event Description (ttm:desc), its small provisional descType registry (pronunciationNote, scene, plotSignificance) and x- user-defined types, plus Rate/Pitch for synthesized speech. No M&E or stem concept appears in the document; mixing is gain/pan. So an agent can use DAPT to keep three kinds of data apart, but must define its own performance-intent convention. · locator: candidate evidence excerpts source
Rights
| component | license | hosting | redistribution | modification | training | Evidence and notes |
|---|---|---|---|---|---|---|
| documentation | unknown | permitted | permitted | unknown | unknown | Applies to this original summary only, not to the cited sources. |
Linked records
- cites → https://www.w3.org/TR/dapt