Re: Wide Review request for DAPT

I don't recall that WAI-Adapt stood for anything. Working with E-O and
the wider WAI Coordination Call, it was believed to be more descriptive,
and much more accurate than the older "Personalization."

There's also the old conundrum of "audio description" or "video
description." In the Media Accessibility User Requirements (MAUR) we
went with the latter, because we were describing video, sometimes using
audio and sometimes using text to convey the description.

I believe Apple uses some more elaborate phrase such as "audio
description of video," or similar.

More recently there has been complaint of some providers using TTS to
provide descriptions, which amuses me a bit as that's audio generated
from a text script. But, so is a human narration, I suppose.

I will confess that the more accepted term is "audio description," and I
believe APA and AG still clash over that. We'll get to revisit this in
the update now planned for MAUR.

What to use as a monocre, I often come up with ideas, but I haven't a
good one just now.

Janina


David Fazio writes:
> The Personalization Task Force, I believe it was, was renamed to ADAPT. The actual meaning of the acronym escapes me at the moment. The meaning of either acronym is irrelevant. It is the acronym itself that causes confusion, not what it stands for.
> 
> Sent from my iPhone
> 
> On Jul 17, 2023, at 4:11 PM, John Foliot <john@foliot.ca> wrote:
> 
> 
> Hi Nigel, WAI-ADAPT - like you, most folks are looking for an "easy to say/remember" name, and as in most instances, people drop the WAI (as in WAI-ARIA vs. ARIA). Since both are emerging fr
> External (john@foliot.ca<mailto:john@foliot.ca>)
>   Report This Email<https://protection.inkyphishfence.com/report?id=bmV0b3JnZnQ4NDM0NDAvZGZhemlvQGhlbGl4b3BwLmNvbS8wNTZjM2ZhM2Q0MmVkZDkzN2MzNjFmYWFiNTRkNWY1OS8xNjg5NjI4Mjc1LjI2#key=783437c06ee763a3e1898734d34ed29c>  FAQ<https://www.godaddy.com/help/report-email-with-advanced-email-security-40813>  GoDaddy Advanced Email Security, Powered by INKY<https://www.inky.com/protection-by-inky>
> 
> Hi Nigel,
> 
> WAI-ADAPT - like you, most folks are looking for an "easy to say/remember" name, and as in most instances, people drop the WAI (as in WAI-ARIA vs. ARIA). Since both are emerging from the W3C, I think that that would be the concern.
> 
> And yes, I was referring to WAI-ADAPT
> 
> My $0.02 FWIW
> 
> JF
> 
> On Mon, Jul 17, 2023 at 12:48 PM Nigel Megitt <nigel.megitt@bbc.co.uk<mailto:nigel.megitt@bbc.co.uk>> wrote:
> Thanks both, I’ll feed this back to TTWG.
> 
> For what it’s worth, we spent quite a while trying to find a good name that did not clash with existing names that occupy a similar space, and DAPT appeared to be unused. Since we pronounce it as dee-ay-pee-tee rather than as “adapt” without the leading “a” I don’t think it ever occurred to us that there could be a name clash with a different thing called ADAPT – I can see how others might instinctively voice it differently though, and run into this.
> 
> Can I ask though: since a web search for ADAPT in relation to audio description and dubbing shows no results on the two search engines I tried, in the first 4 pages of results, can you spell out what the ADAPT is that could cause unintended confusion here?
> 
> Two sort-of-related things I found, neither of which is explicitly about dubbing or audio description:
> 
>   *   Is it the grassroots disability organisation described at https://en.wikipedia.org/wiki/ADAPT<https://shared.outlook.inky.com/link?domain=en.wikipedia.org&t=h.eJxFjEsOwiAURbfSMDa8ll8_ozZxAQ7cAPLAYrGQitFo3LsycnjPPTlvct8CGSoy55xuA4Bd6cMvPln0msbtDGXBtJ8OR7KryFLc1ebf43InuBA1oNMvH8fZBv-MKVETr1BLZbjTHAWziD1vDVeN0_okBUone2hU1yvWsVZSpkrZlvIlzuvoYvAxU6MLxoL_5PMFYK013A.MEUCIQC_nd-WHYC6fhZGw2ivfE4aNlRZAjPXYSM4Ev9eqn3n2gIgeT6dWpNBLyGhgJ0YV7-ORektrI3YwnjrMvX3N602I9w> ?
>   *   Or are you referring to WAI-Adapt https://www.w3.org/WAI/adapt/<https://shared.outlook.inky.com/link?domain=www.w3.org&t=h.eJxFzDsOwjAQRdGtRK6RJ_EvnyqUrIDaeGwSCBkrGBmB2Du4oj3v6b7ZY1vYULEppXgfAHLOPEtO2xmO-wNYtDEB21XsWl6rT78lpE5JpWrAYF8zjZNf5ifFyB3doNbGyWAlKuERe9k6aZpg7Ukr1EH30JiuN6ITrebClLIv5QtN6xhomSlxZwtj4b98vrdZM10.MEYCIQCIUIJJQ7xz6t9UFZdpj4-9U1rruZ2psGCO0Y4xW_5RUAIhAO8vx0w35ATEZUXhFhAvIjz0vqA6XJL3NbO6cDelH43L> ?
> 
> Thanks for the suggestion of DADPT. I don’t personally like it because I think it’s hard to say, and some degree of “trips off the tongue” is generally a good thing, if it means people can discuss it more easily.
> 
> Kind regards,
> 
> Nigel
> 
> 
> From: John Foliot <john@foliot.ca<mailto:john@foliot.ca>>
> Date: Monday, 17 July 2023 at 17:14
> To: David Fazio <dfazio@helixopp.com<mailto:dfazio@helixopp.com>>
> Cc: Nigel Megitt <nigel.megitt@bbc.co.uk<mailto:nigel.megitt@bbc.co.uk>>, "public-apa@w3.org<mailto:public-apa@w3.org>" <public-apa@w3.org<mailto:public-apa@w3.org>>, Atsushi Shimono <atsushi@w3.org<mailto:atsushi@w3.org>>
> Subject: Re: Wide Review request for DAPT
> 
> I sadly concur with David Fazio - the naming issue here is problematic.
> 
> Nigel, would the TT WG consider renaming this to DADPT (highling the D in Description:  Dubbing and Audio Description Profiles of TTML2)
> 
> JF
> 
> On Mon, Jul 17, 2023 at 10:16 AM David Fazio <dfazio@helixopp.com<mailto:dfazio@helixopp.com>> wrote:
> I would seriously consider renaming this document. It’s confusing for those of us that are familiar with “ADAPT”.
> 
> 1. DAPT looks like a typo, as if it should be ADAPT
> 
> 2. The very first sentence begins with A DAPT document. Again, it looks like a typo where a space was included, after the A, by autocorrect. It looks too much like ADAPT.
> This message was Sent from my iPhone. Please excuse any typographic errors.
> 
> 
> On Jul 17, 2023, at 9:04 AM, Nigel Megitt <nigel.megitt@bbc.co.uk<mailto:nigel.megitt@bbc.co.uk>> wrote:
> 
> Dear Accessible Platform Architectures Working Group,
> 
> The W3C Timed Text Working Group (TTWG) (Charter<https://shared.outlook.inky.com/link?domain=www.w3.org&t=h.eJxFzEsOwiAUQNGtGJxaqPxsO-pWkI-gLa_BZzAa966MnJ7k3jd5lIVMOxIRt_vEWK2VVkGhXBjvuWC9ZJhW7zr0T-zqpbPRFPSFRlyXvQUoLmWDCTI57MitrbLHXx5wkELKnrlgXgnm6Jf0hG2jFlbWK21FMMJJ7p0bxckKfQzGnJV0KqiRHfUwaj7wk6Jct7Nv5yvEPAdYEiC1prFr_JfPF2i7QNI.MEUCIDDKniySRNRcW93lF5iAfDV4n3ffn72KrEC8vp7FOnyHAiEAy88VQSrF2_nT8pZzhGu9YAoNu6i4HIeor74OFT_Sy30>) wishes to inform the Accessible Platform Architectures Working Group of the Working Draft of the Dubbing and Audio description Profiles of TTML2 (DAPT) Recommendation at https://www.w3.org/TR/dapt/<https://shared.outlook.inky.com/link?domain=www.w3.org&t=h.eJxFzEsOgjAUQNGtkI5NH_THZ8QajBuofa2gwGuwpkbj3rUjpyc3980e-8KGik0pxfsAkHPmWXLaL3A6AtqYgB0qdivN5tPPQ-qUVKoGDPY10zj5ZX5SjNzRCrU2TgYrUQmP2MvWSdMEa89aoQ66h8Z0vRGdaDUXppx9OV9p2sZAy0yJO1sYC__l8wVORzLB.MEUCIHApAE9YyRqRCVOVHh07n8HXY9QecmpZzIbzJ-RwNQ3zAiEA-4SeCI2p_jepKcsZWbTCvMTG8Q2IQbRRMsoW4fMgj3c> .
> 
> DAPT is a TTML-based format for the exchange of transcripts and scripts among authoring, prompting and playback tools in the localization and audio description pipelines. A DAPT document is designed to carry pertinent information for dubbing or audio description such as type of script, dialogue, descriptions, timing, metadata, original language transcribed text, translated text, language information, and audio mixing instructions, and to be extensible to allow user-defined annotations or additional future features.
> 
> The TTWG invites feedback on DAPT and seeks input on the questions raised as issues within the Working Draft, for example on whether it is important to support direct embedding or external referencing of recorded audio.
> 
> If you have feedback, we welcome it either in response to this message, or as issues raised against the DAPT repository, at https://github.com/w3c/dapt/issues/<https://shared.outlook.inky.com/link?domain=github.com&t=h.eJxFzEsOwiAUheGtNIxNb8urj1G3QrlQ0FpIgWg07t3gxOmXc_43KedO5oa4nGOaATafXVlbHe7wYBpQxQw-pWISkEtDbnV7mBzOzeaRM847QKtePizO7P4ZYvx9OyE1s4ohpwZxYoNmsrdKrYKjsGKCXo6TpCMdREtlLZtavgZ3LDbsPuRWq8pY-S-fL4sqNjA.MEQCID0TQgUDbow98DFAqADVNUYlAnKx-LgpeJDyXbUS3V0iAiBDlPmL2BM265phLJMLm1rtlXzImdXYX3eTxS4P-JvckA> , and request that any feedback is provided by September 10th 2023.
> 
> Please note that we will be making a separate Horizontal Review request to APA WG as required by the Process in due course.
> 
> Looking forward to hearing from you.
> 
> Kind regards,
> 
> Nigel Megitt, co-Chair W3C TTWG
> 
> 
> 
> --
> John Foliot |
> Senior Industry Specialist, Digital Accessibility |
> W3C Accessibility Standards Contributor |
> "I made this so long because I did not have time to make it shorter." - Pascal "links go places, buttons do things"
> 
> 
> --
> John Foliot |
> Senior Industry Specialist, Digital Accessibility |
> W3C Accessibility Standards Contributor |
> 
> "I made this so long because I did not have time to make it shorter." - Pascal "links go places, buttons do things"

-- 

Janina Sajka (she/her/hers)
Accessibility Consultant https://linkedin.com/in/jsajka

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures http://www.w3.org/wai/apa

Linux Foundation Fellow
https://www.linuxfoundation.org/board-of-directors-2/

Received on Tuesday, 18 July 2023 18:49:50 UTC