14:00:13 <RRSAgent> RRSAgent has joined #adapt
14:00:17 <RRSAgent> logging to https://www.w3.org/2024/05/21-adapt-irc
14:00:17 <Zakim> RRSAgent, make logs Public
14:00:18 <Zakim> please title this meeting ("meeting: ..."), janina
14:00:24 <janina> Meeting: WAI-Adapt Teleconference
14:00:31 <janina> Chair: Lionel
14:00:34 <janina> present+
14:00:40 <janina> Date: 21 May 2024
14:00:41 <matatk> matatk has joined #adapt
14:02:25 <matatk6> matatk6 has joined #adapt
14:06:04 <Abhinav> Abhinav has joined #adapt
14:08:49 <matatk> agenda?
14:09:33 <janina> zakim, who's here?
14:09:33 <Zakim> Present: janina
14:09:35 <Zakim> On IRC I see Abhinav, matatk, RRSAgent, Zakim, janina, Roy, gb, dmontalvo
14:09:41 <matatk> topic: Well-known destinations
14:09:43 <Abhinav> present+
14:09:44 <matatk> gb, off
14:09:44 <gb> matatk, OK.
14:09:48 <matatk> scribe+
14:09:52 <janina> present+
14:10:00 <matatk> present+
14:10:02 <matatk> scribe+
14:10:31 <matatk> matatk: janina and I suggest we could use new gh issues each week as the basis for our agenda.
14:10:58 <matatk> matatk: This will require us to (a) encourage new issues [get a draft out] and (b) use gh for specific issues [like we used to]
14:11:45 <janina> scribe+
14:11:47 <matatk> rrsagent, make minutes
14:11:48 <RRSAgent> I have made the request to generate https://www.w3.org/2024/05/21-adapt-minutes.html matatk
14:11:58 <Lionel_Wolberger> Lionel_Wolberger has joined #adapt
14:12:02 <Lionel_Wolberger> present+
14:12:04 <Lionel_Wolberger> agenda?
14:12:27 <Lionel_Wolberger> zakim, who is here?
14:12:27 <Zakim> Present: janina, Abhinav, matatk, Lionel_Wolberger
14:12:29 <Zakim> On IRC I see Lionel_Wolberger, Abhinav, matatk, RRSAgent, Zakim, janina, Roy, gb, dmontalvo
14:12:42 <janina> matatk: Since AC mtg have been reaching out for followup
14:12:57 <janina> matatk: Have response from one, waiting for a the additional ones
14:13:16 <janina> matatk: No tech feedback yet, but working on communications for that
14:14:59 <Lionel_Wolberger> rrsagent, make minutes
14:15:00 <RRSAgent> I have made the request to generate https://www.w3.org/2024/05/21-adapt-minutes.html Lionel_Wolberger
14:15:32 <matatk> topic: Logistics
14:15:38 <matatk> matatk: I'm away next Tuesday
14:15:45 <matatk> matatk: Janina is away on the 11th
14:15:53 <matatk> janina: I propose we skip next week's call
14:15:56 <matatk> Abhinav: +1
14:16:40 <matatk> janina: Proposal is the next Adapt call is the 4th of June. Let's give ourselves clear actions for next time.
14:17:07 <matatk> Lionel_Wolberger: +1
14:17:39 <matatk> RESOLVED: Next Adapt call will be the 4th of June
14:17:44 <matatk> rrsagent, make minutes
14:17:45 <RRSAgent> I have made the request to generate https://www.w3.org/2024/05/21-adapt-minutes.html matatk
14:18:24 <matatk> topic: Well-known actions :-)
14:19:10 <matatk> Abhinav: What are we going to put out as a proposal? Will we incorporate updates?
14:20:25 <janina> matatk: Key things: 1. Follow up with AC participants who had opinions; 2. Update docs esp explainer and early spec draft that reflects Explainer
14:20:42 <janina> matatk: Hopefully, AC people with opinions will join a future call with us
14:20:48 <janina> s/explainer/Explainer/
14:21:21 <janina> matatk: We need a "straw doc" to have something to discuss
14:21:35 <janina> matatk: Shortly thereafter we can decide whether that's FPWD ready
14:22:16 <janina> matatk: Hopes to have drafts by next mtg
14:23:00 <janina> Abhinav: Are we clear what we want from the people we're contacting?
14:23:29 <janina> Abhinav: Various tech approaches?
14:23:50 <janina> matatk: Both and all--We have use case validation from our COGA conversation ...
14:24:16 <janina> matatk: The AC participants are interested in what's appropriate for solving our needs/reqs
14:24:44 <janina> matatk: That's why it's appropriate for us to have documentation that supports our approach
14:25:03 <janina> matatk: Specifically, the AC people I'm contacting were interested in participating
14:25:18 <janina> matatk: One is the actual author of the IETF WKU
14:26:21 <janina> Abhinav: Should we limit Explainer to one tech approach? Or do we need to publish other approaches and why we accept or reject them?
14:26:42 <janina> matatk: It's a bit different now because it's early work
14:27:12 <janina> matatk: Generally, an Explainer explains the decided approach. But, the alternatives considered are always important in an Explainer
14:28:33 <janina> matatk: Even though we're not yet locked in on it, we do have a leading candidate and we should draft the Explainer as what we've decided because that's what was presented to the AC
14:29:06 <janina> matatk: Use cases go first in the Explainer, and they're very important to a successful effort
14:30:08 <janina> Abhinav: Concerned to have open questions addressed
14:30:27 <janina> Abhinav: Or that we're aware and plan to take it up later
14:30:35 <janina> matatk: Definitely need an Open Questions section
14:31:59 <matatk> janina: We're engaging the people we need who can help us solve for the use cases we have for WKD. So we don't need to address this all ourselves.
14:32:47 <matatk> janina: The AC is the body of people who will have a vote, and need to agree, on what approach we are taking. We have to convince the wider W3C that what we're proposing makes sense. This includes use cases, as well as other approaches considered.
14:33:18 <matatk> q+
14:34:34 <Lionel_Wolberger> scribe+
14:34:57 <janina> Abhinav: Just concerned to capture our open questions and get them into the Explainer, even if we don't have full content for them
14:35:13 <janina> matatk: First draft is something we aready have--it's on github
14:35:26 <janina> matatk: What I'm talking is what I expect to have for our next mtg
14:35:45 <janina> matatk: We will have open questions without much detail
14:36:16 <janina> matatk: We will be showing the specifically interested AC people our solutions approaches
14:36:35 <janina> matatk: Phps that includes a request that IETF version up their WKU
14:36:57 <janina> matatk: Once we're happy with our explainer and draft spec, we go to the formal FPWD
14:37:15 <janina> matatk: That's where we need to be very clear and reasonably complete
14:37:36 <janina> matatk: That's where we ask for wide review, FPWD means "First Public Working Draft"
14:37:54 <janina> matatk: If FPWD has enough detail for implementation, it may be implemented
14:38:17 <janina> matatk: Too much detail now could well be wasted work, because it can change; and likely will change
14:39:21 <janina> W3C Process Bible: https://www.w3.org/Consortium/Process/
14:40:33 <matatk> Recommendation Track info: https://www.w3.org/2023/Process-20231103/#rec-track
14:44:21 <Lionel_Wolberger> Lionel_Wolberger has joined #adapt
14:44:28 <Lionel_Wolberger> rrsagent, make minutes
14:44:30 <RRSAgent> I have made the request to generate https://www.w3.org/2024/05/21-adapt-minutes.html Lionel_Wolberger
14:44:36 <Lionel_Wolberger> q?
14:44:39 <Lionel_Wolberger> ack matatk
14:47:28 <matatk> Abhinav: https://datatracker.ietf.org/doc/rfc8615/
14:47:33 <janina> Abhinav: Have we read RFC 8615 for a complete understanding
14:48:20 <janina> Abhinav: URL needs to be registered and what it's for, but the spec doesn't define what's returned; could be json, text, etc
14:48:58 <janina> Abhinav: Seems to support complex responses to facilitat our more nuanced needs
14:49:40 <janina> matatk: Suggest a gh issue to make sure we all come up to speed!
14:50:43 <janina> topic: Symbols
14:50:53 <matatk> rrsagent, make minutes
14:50:54 <RRSAgent> I have made the request to generate https://www.w3.org/2024/05/21-adapt-minutes.html matatk
14:51:59 <janina> Lionel_Wolberger: Puts up AAC approach for form fields
14:53:28 <Lionel_Wolberger> Lionel_Wolberger: I was trying to recruit, and found that the Task Fore landing page is out of date
14:53:36 <Lionel_Wolberger> ... https://www.w3.org/WAI/APA/task-forces/adapt/
14:53:51 <Lionel_Wolberger> ... we need links to the former Content draft, etc
14:54:01 <Lionel_Wolberger> ... Janina suggests that we take this up in June
14:54:26 <matatk> subtopic: Issue 240
14:54:41 <matatk> janina: Russell sent back a corrected graphic. I propose that means matatk can post on issue 240 now. Agree?
14:55:21 <matatk> janina: Does anyone object to using the corrected graphic, and response to 240 we previously discussed?
14:55:49 <matatk> RESOLVED: matatk to respond on issue 240 as discussed
14:56:12 <matatk> rrsagent, make minutes
14:56:13 <RRSAgent> I have made the request to generate https://www.w3.org/2024/05/21-adapt-minutes.html matatk
14:57:10 <janina> rrsagent, make minutes
14:57:11 <RRSAgent> I have made the request to generate https://www.w3.org/2024/05/21-adapt-minutes.html janina
14:57:21 <janina> zakim, end meeting
14:57:21 <Zakim> As of this point the attendees have been janina, Abhinav, matatk, Lionel_Wolberger
14:57:23 <Zakim> RRSAgent, please draft minutes
14:57:24 <RRSAgent> I have made the request to generate https://www.w3.org/2024/05/21-adapt-minutes.html Zakim
14:57:29 <Zakim> I am happy to have been of service, janina; please remember to excuse RRSAgent.  Goodbye
14:57:30 <Zakim> Zakim has left #adapt
14:57:37 <janina> rrsagent, bye
14:57:37 <RRSAgent> I see no action items