Re: Wide Review request for DAPT

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.

My $0.02 FWIW

JF

On Mon, Jul 17, 2023 at 12:48 PM Nigel Megitt <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 ?
>    - Or are you referring to WAI-Adapt https://www.w3.org/WAI/adapt/ ?
>
>
>
> 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>
> *Date: *Monday, 17 July 2023 at 17:14
> *To: *David Fazio <dfazio@helixopp.com>
> *Cc: *Nigel Megitt <nigel.megitt@bbc.co.uk>, "public-apa@w3.org" <
> public-apa@w3.org>, Atsushi Shimono <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> 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> wrote:
>
> Dear Accessible Platform Architectures Working Group,
>
> The W3C Timed Text Working Group (TTWG) (Charter
> <https://www.w3.org/2023/04/timed-text-wg-charter.html#coordination>)
> 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/ .
>
> 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/ , 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"