14:45:28 RRSAgent has joined #silver 14:45:33 logging to https://www.w3.org/2023/02/24-silver-irc 14:45:33 RRSAgent, make logs Public 14:45:34 Meeting: Silver Task Force & Community Group 14:45:46 agenda+ Next week in AG 14:45:54 zakim, clear agenda 14:45:54 agenda cleared 14:46:02 agenda+ next week in AG 14:46:21 agenda+ review suggestions from COGA task force to the Writing Process document 14:46:34 agenda+ Start the Exploratory section 14:48:15 present: 14:48:21 present+ jeanne 14:48:27 chair: jeanne 14:48:36 regrets+ Shawn 14:50:25 Azlan has joined #silver 14:56:09 kirkwood has joined #silver 14:57:09 Azlan has joined #silver 14:59:05 Chuck_ has joined #silver 14:59:38 Azlan has joined #silver 15:00:35 ToddL has joined #silver 15:00:48 Lauriat has joined #silver 15:00:48 uxjennifer has joined #silver 15:00:55 present+ 15:01:02 Present+ 15:01:34 present+ 15:02:39 chair: jeanne & Shawn 15:02:57 luis has joined #silver 15:03:21 Makoto has joined #silver 15:03:32 present+ 15:04:56 zakim, take up item 1 15:04:56 agendum 1 -- next week in AG -- taken up [from jeanne] 15:05:11 jeanne: next week in AGWG. three things WCAG3 related 15:05:14 * CSUN Face to Face meeting attendance Survey: https://www.w3.org/2002/09/wbs/35422/CSUN-Face-To-Face/ 15:05:14 * Guideline Grouping Survey: https://www.w3.org/2002/09/wbs/35422/guideline-org/ 15:05:14 * Discussion about Requiring vs. Encouraging 15:06:34 .. any of the chairs want to add anything to this? 15:06:48 Wilco_ has joined #silver 15:06:51 present+ 15:06:56 Surveys opening this week closing next week: 15:06:56 * Questions on Editor's Draft Survey: https://www.w3.org/2002/09/wbs/35422/draft-revew-Feb-23/ 15:07:02 .. there's another survey opening soon 15:07:27 .. Michelle has been taking the comments from two weeks ago and updating the draft. This is the survey for the new work 15:07:31 .. any questions? 15:07:35 zakim, take up next 15:07:35 agendum 2 -- review suggestions from COGA task force to the Writing Process document -- taken up [from jeanne] 15:08:44 ... I had a meeting with members of COGA. They're also working on a guideline for error prevention. And they're working on one for clear language. 15:08:57 ... here's the main document 15:09:06 Writing Process with Maturity Levels -> 15:09:11 https://docs.google.com/document/d/1zW-UubALQOCokCoLnIuQrnGNKLm2uHi36S8yhAojrIE/edit# 15:09:55 ... the first thing that they asked is that we change "efficient" in the goals section because it has different meanings in different contexts. They wanted us to clarify it. Any ideas? 15:10:39 ...I think the context of this was "easy to implement" but we don't want to say "easy" because it's not easy. Maybe "clear" would work better. 15:10:55 q+ to ask about evolving technology 15:11:04 "Define guidance and methods that are clear and efficient to implement" 15:11:14 Azlan has joined #silver 15:11:53 lauriat: one of the considerations for evolving technologies was difficulty and barrier to implementation. For some of those, they have become easier over time. I think not "efficient" or "easy" but maybe something on the "understandable" spectrum might work. 15:11:54 prudent? 15:12:02 effort 15:12:06 q+ 15:12:06 q+ 15:12:11 jeanne: what about "reduce barriers to implementation?" 15:12:16 ack lau 15:12:16 Lauriat, you wanted to ask about evolving technology 15:12:16 ack me 15:12:19 ack laur 15:12:20 ack ToddL 15:12:21 ack todd 15:12:44 toddl: a couple of ideas...maybe "adequate" or "appropriate" instead of "efficient" 15:13:30 ack ch 15:13:38 present+ 15:13:50 chuck_: I like jeans "reduce the barriers." I think that's closest to what we had in mind at the time. 15:14:41 jeanne: I think we were looking at problems identified that said the SC were difficult to understand and translate into other languages. 15:15:01 ... maybe it's not about implementation, but about clear and understandable in multiple languages 15:15:02 q+ 15:15:04 q+ 15:15:10 Ack ch 15:15:30 q+ 15:15:35 q+ 15:15:51 chuck_: I don't want to get rid of the implementing. I recall that being a big part of the topic. I want to keep implementing in there. 15:16:42 lauriat: I think one of the reasons implementation doesn't necessarily belong is because it's more guidance on user needs and usability as opposed to implementation itself. We will have things that will help that. 15:16:56 +1 with Jeanne and Shawn, I'm convinced 15:17:08 ... as an example we'll have guidance where there isn't clear implementation as far as "content authors" but there may be other opportunities for AT or other technologies to fill that gap 15:17:11 ack me 15:17:13 ack ToddL 15:17:37 toddl: if we're leaving "implement" in, maybe "suitable" or "sufficient?" 15:18:11 ack Makoto 15:18:35 q+ to echo that i'm now agreeing that we can focus less on "implementation", that the user needs are the primary focus 15:19:05 janina has joined #silver 15:19:13 makoto: we've had challenges translating the other SCs because those documents and techniques are harder to translate into Japanese. So "easy to understand" is a point we should emphasize as a goal 15:19:17 present+ 15:19:18 +1 15:19:23 ack Chuck_ 15:19:23 Chuck_, you wanted to echo that i'm now agreeing that we can focus less on "implementation", that the user needs are the primary focus 15:19:47 chuck_: agreed 15:20:07 qv? 15:20:37 q+ to note where to specify implementation 15:21:46 +1 15:21:50 ack me 15:21:50 Lauriat, you wanted to note where to specify implementation 15:21:55 lauriat: I don't think we need to get rid of it entirely, but it should be specific to the guidance which should be clear and understandable. And the methods should be clear and understandable and also easier to understand and meet the guidance. 15:21:58 +1 with Makoto, Chuck_ & Lauriat 15:22:25 +1 to Shawn 15:23:49 q+ 15:24:11 janina: maybe work in that techniques are technology specific 15:24:19 lauriat: that's not necessariliy always the case 15:24:34 jeanne: and there is a push in AGWG to include some that are generic 15:24:37 ack ToddL 15:26:19 zakim, take up next 15:26:19 agendum 3 -- Start the Exploratory section -- taken up [from jeanne] 15:27:06 The remainder of the meeting is a working session, and does not require scribing. 15:27:06 jeanne: the rest of the meeting is going to be working in the error prevention document 15:27:25 Error Prevention Draft -> https://docs.google.com/document/d/1jtZaUzLi-jgmGdAypRUeJPzVz_ZUpMO0wdOrORiuO7w/edit#heading=h.fbuc9jpnkck2 15:34:39 q+ 15:34:51 q+ 15:34:58 q+ 15:35:32 ack me 15:35:42 ack Chuck_ 15:36:11 ack ToddL 15:37:20 q+ to note outreach to stakeholders & partners for this kind of work 15:38:22 +1 15:39:13 ack me 15:39:13 Lauriat, you wanted to note outreach to stakeholders & partners for this kind of work 15:42:18 q+ to note the illustrative aspect 15:44:01 ack me 15:44:01 Lauriat, you wanted to note the illustrative aspect 15:45:44 Errors User Needs Summary -> https://docs.google.com/document/d/1mTrr0hSsQrApmC4N0tF4fQOF-PiLsK-FNZproi7WQcA/edit# 15:50:27 changing to only “notification” gets rid of the “guidance” part, no? i guess it was eliminated? 15:52:47 q+ 15:52:57 q+ to ask about redundancy, severity, etc. of errors 15:53:05 ack Chuck_ 15:53:22 makes sense 15:53:59 q+ 15:54:46 ack me 15:54:46 Lauriat, you wanted to ask about redundancy, severity, etc. of errors 15:54:47 q+ 15:55:14 regrets+ Mary Jo Mueller 15:55:18 ack ToddL 15:55:57 ack Chuck_ 15:56:27 +1 to Chuck_, maybe a good question of where to note things as they come to mind? 15:57:49 +1, incredibly well thought out! 15:59:51 rrsagent, make minutes 15:59:52 I have made the request to generate https://www.w3.org/2023/02/24-silver-minutes.html jeanne 16:01:15 janina has left #silver 18:21:27 kirkwood has joined #silver 21:23:02 kirkwood has joined #silver 21:58:51 kirkwood has joined #silver