– DRAFT –
Spoken Pronunciation Task Force Teleconference

Agenda Review & Announcements

janina: we have new APA chair

Action Items

PaulG: summary from last week- discussion from ARIA working group and response. They have own proposal and we had to update our gap-analysis document based upon that. Markku have updated our gap-analysis documents.

https://w3c.github.io/pronunciation/gap-analysis_and_use-case/#gap-analysis

<janina> https://www.canofworms.com/triple-homonyms.html

http://htmlpreview.github.io/?https://github.com/mhakkinen/pronounce/main/pro-gap-update.html

janina: just to challenge ARIA, I found this page of triple-homonyms

janina: I will keep looking for more examples

PaulG: We discussed the recent alternative, dictionary-based, proposal by some of the UA vendors [1] and that this doesn't address some of the key areas highlighted in the gap analysis [2]. We talked about ways that the TF hopes to productively continue this discussion including

janina: one of the thing that we are exposing here that aria is focus too much on the user-agent but meanwhile they are complicating the process. we already talked about multiple 'lang' which doesn't help very much

janina: they are looking for easy win to get this rolling which is a sensible approach but then what? It could be far more complicated process because extensibility is important for long journey.

PaulG: our roadmap is where ARIA need to focus and understand why are we doing this.

janina: may be we can ask them to go ahead with implementing part of it and not all of once.

mhakkinen: I have updated gap-analysis document. I want clear whether it can also play a substitution role.

PaulG: it can be little hacky though

mhakkinen: I think sub only goes to synthesizer

PaulG: but it is an improvement with the section 3.

mhakkinen: in the proposed document, I have added new column called aria-pronounce.

mhakkinen: I did not want to edit the main 'gap-analysis' document so I kept it separate stand alone document. If we bring it to main document then we have to provide the old document link.

mhakkinen: we have some examples in this document

<PaulG> https://github.com/w3c/pronunciation

<PaulG> https://w3c.github.io/pronunciation/gap-analysis/#gap-analysis

mhakkinen: I excerpted the table from the published Pronunciation Gap Analysis and Use Cases draft and created a standalone document

Github Issues

PaulG: we have one new issue from michael-roe. https://github.com/w3c/pronunciation/issues/103

<PaulG> https://github.com/w3c/pronunciation/issues/103

PaulG: The current spec isn't clear if data-ssml-say-as-format="cardinal" can be applied to Roman numerals, or if we need a new format to handle Roman numerals.

PaulG: I think sub, say-as, pronounce is the way to address this. we still owe response to some tickets.

<janina> Trying again: https://people.sc.fsu.edu/~jburkardt/fun/wordplay/multinyms.html

Dee: the term is heteronym to identify the right use cases

SteveNoble_: some times homograph is also used for the same definition

<PaulG> https://github.com/w3c/pronunciation/issues/100

Other Business

mhakkinen: ATIA conference is still on and at this point I am going in person with Peter Ramsdel from textHelp.

mhakkinen: as soon as we have some more details, will share this with the group. we have done this presentation number of times.

rssagent, make minutes