- From: Kevin White <kevin@w3.org>
- Date: Mon, 28 Aug 2023 17:10:29 +0100
- To: WAI Coordination Call <public-wai-cc@w3.org>
- Message-Id: <5816830B-5792-4F81-8EBD-C386D72237C6@w3.org>
Hi All, Minutes are available at: https://www.w3.org/2023/08/28-waicc-minutes.html <https://www.w3.org/2023/08/28-waicc-minutes.html> Text below, Thanks Kevin — [1]W3C [1] http://www.w3.org/ - DRAFT - WAI Coordination Call Teleconference 28 Aug 2023 [2]Agenda [2] https://lists.w3.org/Archives/Public/public-wai-cc/2023Aug/0023.html Attendees Present kersc, kevin, shawn, janina, JaeunJemmaKu, Daniel, Lionel_Wolberger_ Regrets tzviya Chair kevin Scribe George Contents * [3]Topics 1. [4]Update on WCAG 2.2 publication 2. [5]Infoshare and coordination checks 3. [6]Publication checks 4. [7]WAI Vision * [8]Summary of Action Items * [9]Summary of Resolutions __________________________________________________________ <agendabot> clear agenda <scribe> scribe: George Take up first item Update on WCAG 2.2 publication Kevin: Update on 2.2 One member is comfortable and has withedrawn the objection. The other objections have not yet been resolved, but we are working on it. The issue around 2.1 seems like it will be resolved and we expect the objection to be withdrawn. Infoshare and coordination checks <janina> [10]https://en.wikipedia.org/wiki/Well-known_URI [10] https://en.wikipedia.org/wiki/Well-known_URI Janina: about unique URI. There is an IETF and here is the link. Shawn: I sent W3C staff information. We did get a message. I sent message from two staff; yes we received it. Publication checks <shawn> [11]https://www.w3.org/WAI/cc/wiki/WAI_Announcement_Drafts#Upco ming_Publications [11] https://www.w3.org/WAI/cc/wiki/WAI_Announcement_Drafts#Upcoming_Publications Kevin: Moritorium on publications will be startin September 8 through 18. WAI Vision Kevin: WAI Vision; we have been working on it and presented to the WAI Steering Council. Next step is for this group to review. <Jem> what is the WAI Steering Council? It is my first time to hear the council <shawn> [12]https://docs.google.com/document/d/1UI9cIjQYonGfKNHvB2rFhpw mW06QEl2r0xBObkHOWZs/edit [12] https://docs.google.com/document/d/1UI9cIjQYonGfKNHvB2rFhpwmW06QEl2r0xBObkHOWZs/edit Shawn: Here is a link to a Google Doc with a link to the document on Vision and Mission: Kevin: The Steering COuncil was sent up many years ago and have advised Judy. It was a sounding board. It continues to give us advice. We will doing more about this. They give another perspective. Shawn: We want to do more about formalizing the SC, but it is not a priority and we will work on it in the future. ... With staff leaving, we wnat to be betterat defining our vision, mission, goals. We want to be realistic on priorities for 2023. If there is something missing, feel free to speak up. We are working on this with a view to have a strategic plan for 2024. There are many opportunities, but because of limitations we want to pick the most important. We will be having a breakout at TPAC. For now, if therre is something missing, let us know. Please feel free to make comments on this. Take a minute to look at the 2023 priorities. Jem: Clarification on some priorities. Shawn: Feel free to have people use the current course for now. <jamesn> s/jamesen/Jem/ Kevin: Please take the time to look through this and make comments. George: Can they comment or edit? Shawn: Only comments are allowed by this group. James: Do we more formally with Open UI. We do not have any set up right now and it is missing: <matatk> +1 to jamesn's suggestion of a formal liaison with OpenUI Shawn: We do not have a mechanism. James: I will add that. Shawn: I will add that. James: We do not have influence over thir direction. There needs to be a little more. It works because we have embedded people there. James: Important to improve the relationship. Shawn: This has come up in other meeting. Important to have strong communications. James: We should have a list and track if things are working. <Jem> [13]https://www.w3.org/community/open-ui/ [13] https://www.w3.org/community/open-ui/ Shawn: Those relationships should be on APA's radar. <kevin> Scibe: kevin <kevin> George: Embedded accessibility experts is really important <kevin> ... Many people in the publishing standards means that we don't need to put specific people in there <kevin> ... Important for tracking Community Group activity James: We need multiple experts in these groups to ensure consistency. Summary of Action Items Summary of Resolutions [End of minutes] __________________________________________________________ Minutes manually created (not a transcript), formatted by David Booth's [14]scribe.perl version 1.200 ([15]CVS log) $Date: 2023/08/28 16:02:58 $ __________________________________________________________ [14] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm [15] http://dev.w3.org/cvsweb/2002/scribe/ Scribe.perl diagnostic output [Delete this section before finalizing the minutes.] This is scribe.perl Revision VERSION of 2020-12-31 Check for newer version at [16]http://dev.w3.org/cvsweb/~checkout~/2002/ scribe/ [16] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) FAILED: s/jamesen/Jem/ Succeeded: s/Jamesen/Jem/ Succeeded: s/Shwawn/Shawn/ Default Present: kersc, kevin, shawn, janina, JaeunJemmaKu, Daniel, Lion el_Wolberger_ Present: kersc, kevin, shawn, janina, JaeunJemmaKu, Daniel, Lionel_Wolbe rger_ Regrets: tzviya Found Scribe: George Inferring ScribeNick: George Agenda: [17]https://lists.w3.org/Archives/Public/public-wai-cc/2023Aug/0 023.html [17] https://lists.w3.org/Archives/Public/public-wai-cc/2023Aug/0023.html WARNING: No date found! Assuming today. (Hint: Specify the W3C IRC log URL, and the date will be determined from that.) Or specify the date like this: <dbooth> Date: 12 Sep 2002 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 [18]scribe.perl diagnostic output] [18] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
Received on Monday, 28 August 2023 16:10:34 UTC