Pronunciation Task Force Teleconference

22 Jan 2020




<paul_grenier> preset+

<Irfan> https://w3c.github.io/pronunciation/explainer/

<janina> https://www.w3.org/wiki/WAI/announcements#Upcoming_Announcements_.3C-_add_yours

<Use case document> agenda+ <Explainer DRAFT document format> Agenda+ Other Businesses

<paul_grenier> update from Schema.org: https://webschemas.org/PronounceableText published

Irfan - Spoke with Leonie Watson, web incubator community group member, where we will need to take our docs for review

Irfan - Additional feedback meeded for our docs from our task force members

Irfan - CSS speech property to be added to document

Dee & Christine to provide editorial work

<Irfan> ACTION: Dee to review the use case and gap analysis document

<trackbot> Created ACTION-13 - Review the use case and gap analysis document [on Dee Dyer - due 2020-01-29].

Deadline to complete our reviews - Jan 29th

<Irfan> https://w3c.github.io/pronunciation/gap-analysis_and_use-case/index.html

<Irfan> ACTION: Paul to add PronounceableText from schema.org in our use-case document

<trackbot> Created ACTION-14 - Add pronounceabletext from schema.org in our use-case document [on Paul Grenier - due 2020-01-29].

Paul - see above link for published pronunciation text; to be added to our docs

Irfan - Updates to be completed simultaneously on the document, and finalized by end of Jan with a final due end of Feb.

explainer document format

<Irfan> https://w3c.github.io/pronunciation/explainer/

Irfan - Abstract added to the Explainer document; may also need an introduction. If ready for vendors to review at ATIA, then will need to finalize by end of this week

Irfan - It has been advised that we present the Explainer document to the AT vendors at ATIA.

Janina - community buy-in by vendors is essential because we want our values added to the DOM

Irfan - getting browsers on board to adopt these technical specs is important for our cause

<janina> https://www.w3.org/wiki/WAI/announcements#Upcoming_Announcements_.3C-_add_yours

Janina - we want to widely publish this document for greater and broader awareness to the stakeholders

Janina - create an announcement and/or blog post to create awareness

Janina - also publish to WAI interest group to invite feedback, via GitHub issue or specific email address

Janina - wider reach can be accomplished by all of us spreading the word via social connections and social media

Irfan - do we need an official approach to follow for publishing as a specification, through a web publications group

Janina - we probably don't need to define as we have been discussing with Leonie; final group for publication review is still unfinished

other business

Janina - Explainers are important as a document and need to be published for call for consensus.

RSSAgent, make minutes

Summary of Action Items

[NEW] ACTION: Dee to review the use case and gap analysis document
[NEW] ACTION: Paul to add PronounceableText from schema.org in our use-case document

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version 1.154 (CVS log)
$Date: 2020/01/22 15:32:11 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/agenda+ <Use case document>   agenda+ <Explainer DRAFT document format>  Agenda+ Other Businesses/ agenda+ Use Case Document/
Default Present: Dee
Present: Dee

WARNING: Fewer than 3 people found for Present list!

No ScribeNick specified.  Guessing ScribeNick: Christine
Inferring Scribes: Christine

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 22 Jan 2020
People with action items: dee paul

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.

WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)

[End of scribe.perl diagnostic output]