<Roy> https://www.w3.org/community/covid-19/
Irfan: Roy has sent email but we can't view portal for announcement
<Roy> https://www.w3.org/WAI/cc/wiki/WAI_Announcement_Drafts#Pronunciation_Announcements
Roy: Announcement is in the Wiki page, it will be posted to website news; we can follow-up for status
Janina: hopefully soon our
announcement will be posted as we are probably cued up;
typically takes 5 days
... you will be able to see it on w3c.org
Irfan: Last week we were surprised to see this document; subsequent conversations revealed that Leonie Watson may be editing this document
Roy: CSS working group discussed specifications and that Leonie was interested in this document; can we get more details from APA working group
Janina: All news to me
Irfan: Will we revise this document? Is any vendor driving this?
John: Rather than trying to guess on what is happening, let's invite her to discuss
Janina: this may only be a rumor,
let's not jump to any conclusions. Let's verify first before we
take any actions
... The document was originally published in 2012, then retired
in 2015? And now it appeared in CSS last week. This came as a
surprise for everyone. Will plan on bringing this up in the
coordination call
... Verify info first and then we will proceed
accordingly.
... This managed to by pass certain requirements and hurdles;
supports our gap analysis which we can add to our draft, if
needed.
Irfan: Will ask Leonie Watson on the APA call
<paul_grenier> (topic of discussion: https://www.w3.org/TR/css-speech-1/)
Paul: Do we need to go back to gap analysis to edit?
Janina: Mark reviewed and determined that we don't need to make any edits, at this time, as there are no substantive differences
<Irfan> to check the difference - http://services.w3.org/htmldiff
Paul: I think the analysis stands, and won't need any updates until and if we see the review comments
Should we reference the CSS document in our analysis
Janina: We should wait until we get the feedback and then we can reference after we have closed the time for reviews/feedback.
Irfan: Should someone join the CSS working group?
Janina: Yes, we are definitely interested in doing that, so that we can track and stay on top
Irfan: How to proceed further; what's next?
Janina: The announcements to come out and then we circulate to our communities. Then we look for comments and deal with them formally. The other path is that we all go to the web incubator community group and present our specifications
Irfan: One of teh vendors have already implemented our approach, should we include this
Janina: Not sure if we add this to the specifications; we need to do outreach with web incubator community group; we will eventually need implementation for each normative feature
Irfan: How can we get involved?
Janina: after announcements go
out, we individually join the WICG (web incubation community
group)
... start socializing it with WICG, but only after the
announcement
... we continue to meet as normal but we socialize our approach
thru participation in WICG
<Roy> https://wicg.io/
See URL posted above by Roy
<Roy> https://www.w3.org/community/wicg/
Irfan: Any other business for all to report?
Janina: we are in a holding pattern
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) Default Present: Irfan, Roy, Christine, PaulB, Dee, SteveNoble, janina, mhakkinen, paul_grenier, JF Present: Irfan Roy Christine PaulB Dee SteveNoble janina mhakkinen paul_grenier JF No ScribeNick specified. Guessing ScribeNick: Christine Inferring Scribes: Christine Found Date: 18 Mar 2020 People with action items: 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]