13:15:05 <RRSAgent> RRSAgent has joined #eo
13:15:05 <RRSAgent> logging to https://www.w3.org/2021/01/08-eo-irc
13:15:07 <trackbot> RRSAgent, make logs public
13:15:07 <Zakim> Zakim has joined #eo
13:15:09 <trackbot> Meeting: Accessibility Education and Outreach Working Group (EOWG) Teleconference
13:15:09 <shawn9> present:
13:15:09 <trackbot> Date: 08 January 2021
13:15:46 <shawn_sick> present+ Shawn(first-part-only)
13:23:29 <Jade> Jade has joined #eo
13:25:46 <Jade> Jade has joined #eo
13:26:46 <brent> brent has joined #eo
13:30:42 <MarkPalmer> MarkPalmer has joined #eo
13:31:23 <Howard> Howard has joined #eo
13:31:32 <Howard> present+ Howard
13:32:26 <shawn_sick> present+ Jade, Estella, Daniel, Brent, Shadi, Jason
13:32:31 <shawn_sick> Chair: Brent
13:33:23 <shawn_sick> present+ Laura
13:33:50 <shawn> zakim, who is on the phone?
13:33:50 <Zakim> Present: Shawn(first-part-only), Howard, Jade, Estella, Daniel, Brent, Shadi, Jason, Laura
13:33:53 <dmontalvo> present+ Daniel
13:33:56 <estella> estella has joined #eo
13:34:14 <shawn> present+ Sharron
13:34:50 <Laura> Laura has joined #eo
13:34:55 <Laura> present+
13:35:07 <sharrush> sharrush has joined #eo
13:35:07 <estella> present+
13:35:15 <krisannekinney> krisannekinney has joined #eo
13:35:28 <shawn> present+KrisAnne
13:35:32 <shawn> present+ KrisAnne
13:35:35 <sharrush> present+
13:36:16 <sharrush> Topic: Introduction to new EO particiant
13:36:41 <sharrush> All: Name, role, day job, location
13:38:08 <shawn> present+ Howard, Mark
13:38:15 <shawn> zakim, who is on the phone?
13:38:15 <Zakim> Present: Shawn(first-part-only), Howard, Jade, Estella, Daniel, Brent, Shadi, Jason, Laura, Sharron, KrisAnne, sharrush, Mark
13:38:54 <shawn> present- sharrush
13:43:39 <brent> https://www.w3.org/WAI/EO/wiki/EOWG_Meetings#Agenda
13:44:02 <sharrush> Topic: Media Resource - revisions to content
13:44:47 <shawn> https://www.w3.org/WAI/EO/wiki/Accessible_Media_Resource#2021_January_Revision
13:44:50 <sharrush> Brent: There have been requireemnts created about the requirements for the needed changes. Shawn is the editor and has created a new first page and the lead in to what will be the second page.
13:45:28 <sharrush> ...we asked folks to look the the updates and today want to see how people are feeling about changes.
13:46:08 <sharrush> Shawn: Please do review the revision requirements ananlysis to be sure we are in sync about intentions and goals for this work
13:46:43 <Sylvie> Sylvie has joined #eo
13:48:15 <shawn> present+ Sylvie
13:48:29 <krisannekinney> q+
13:48:30 <Sylvie> Present+ Sylvie
13:48:53 <brent> ack kris
13:49:39 <sharrush> KrisAnne: Will the side menu eventually sync up with the actual content?
13:50:06 <sharrush> Shawn: Yes this is a preview and we will update Prev Next buttons and the side nav when the content is final.
13:52:30 <shadi> q+
13:52:32 <sharrush> Sharron: This is terrific Shawn, thanks, looking very good indeed
13:52:40 <brent> ack shadi
13:53:01 <Laura> +1 I like it.  It's clean and easy to read.
13:54:04 <sharrush> Shadi: Loving this Shawn, overall a great approach. Short and succinct first page and a good way to get to the specifics that I am looking for. In the requirements we say we want to move to an imperative language, checklist kind of presentation. Are we still working on that? It does not seem to meet that goal so far.
13:54:21 <sharrush> Shawn: I am hoping this is final.
13:55:09 <Sylvie> I agree with what Laura said, very clear page!
13:55:10 <Howard> +1 to
13:55:25 <Howard> +1 to "creating new ..."
13:55:28 <JasonMcKee> +1 ( one minor note: outsource is misspelled in summary)
13:55:51 <sharrush> Shadi: OK in that case, I think we may need verbs on all of them. For the new audio content for example, new on its own is ambiguous. May want all of them to start with verbs to meet the "imperative" requirement. Consider having each sentence begin with a verb.
13:57:34 <brent> q+
13:57:38 <sharrush> Shawn: We could pull the verb into the heading; we could bold the verb that is near the beginning of the sentence. Trying to think of other ways to address.
13:57:38 <brent> ack me
13:58:46 <Howard> q+
13:59:28 <sharrush> Brent: I completely see what Shadi is saying but to be devil's advocate, I saw those as a heading and a link. The image draws me to each heading, the heading gives me a quick look, and the paragraph expands. To me this is a clear presentation so I am torn feeling that we may not need to add those verbs.
13:59:35 <brent> ack Howard
14:00:25 <shadi> q+
14:00:35 <dmontalvo> q+ to ask about "user experiences" versus "users experience"
14:00:41 <sharrush> Howard: On thing that struck me is the heading says what to do and my attention is drawn to the link. It doesn't quite match up to the heading until I read on. So I see Shadi's point since I expect to see some kind of action.
14:00:55 <dmontalvo> +1 to verbs to better communicate the action needed
14:01:43 <shadi> q-
14:01:44 <sharrush> ...not just for the new media but all of them. Maybe rather than "What To Do" change to "Areas to Address/Cover" something like that there would be less of a mismatch.
14:01:48 <estella> +1 to Howard
14:02:03 <sharrush> KrisAnne: Or things to consider
14:02:30 <brent> ack dm
14:02:30 <Zakim> dmontalvo, you wanted to ask about "user experiences" versus "users experience"
14:02:31 <shadi> +1 to changing the heading instead of the links
14:02:33 <sharrush> Brent: If it is left as What to Do, we have a greater need for verbs. If that change is made, less so.
14:03:18 <sharrush> Daniel: Should the emphasis be on Users rather than User? I am in favor to change into verbs to better point to the needed actions.
14:03:51 <sharrush> Shadi: It might be an easier change to the Headings
14:04:20 <sharrush> Sharron +1 to "What to Consider"
14:04:20 <estella> q+
14:04:51 <brent> ack estella
14:04:52 <sharrush> Shawn: I did not have a heading there at all to begin.
14:05:13 <Howard> I like "Areas to Consider"
14:05:47 <sharrush> Estella: Putting an active verb on the bullet as Shadi suggested, it helps people understand the needed action. Using verbs will reinforce the message well.
14:06:44 <sharrush> Shawn: Reminder of previous...
14:06:50 <shawn> https://deploy-preview-149--wai-media-guide.netlify.app/media/av/quicktips/
14:06:54 <Sylvie> +1  to "things to consider" too.
14:07:41 <sharrush> Shawn: The current page has the heading and then a sentence that starts with a verb. If we put the verb fist, we are going back to something like this.
14:07:44 <estella> q+
14:07:57 <brent> ack est
14:08:02 <shadi> +1 to inline links
14:08:32 <shadi> q+
14:08:43 <sharrush> Estella: Now I see the thinking behind what you are doing. Reconsdering, I agree with the way it is now - the action is in the sub-heading
14:08:44 <brent> ack shadi
14:09:04 <sharrush> Shadi: The page you just showed works well for me.
14:09:53 <sharrush> Shawn: For me it is harder to skim, harder to find specifics. I think this is a resource people will use more than once and findability is improtant.
14:09:53 <Laura> q+
14:11:05 <brent> ack laura
14:11:07 <sharrush> Brent: I would send people to the Overview page so they get the full picture and would want to make it easy for people to find the specific point of interst (like captions)
14:11:14 <shadi> q+
14:11:42 <sharrush> Laura: I agree with you Shawn that the current version makes it easier to find information, I do not especially like the bolded verbs.
14:12:18 <sharrush> s/improtant/important
14:13:09 <sharrush> Shadi: All of the pages could quite comfotably have verbs except the audio and video content that is a bit different. The others could use a similar approach.
14:13:34 <sharrush> Shawn: But that has issues with frontloading and screen reader use.
14:13:54 <brent> ack shadi
14:13:57 <sharrush> s/comfotably/comfortably
14:14:03 <estella> q+
14:14:53 <sharrush> Shawn: Shadi's comment was mild, we have had some discussion, are we comfortable with where it is now or shall we continue the discussion.
14:14:54 <shawn> ack e
14:15:40 <shawn> now on record, even though I like bold for some things, I don't like it here :-)
14:16:18 <sharrush> Estella: For me, it is ready. I do not like the bold however. When looking at the checklist it seems more straightforward than these paragraphs, wondering if they could compliment each other?
14:16:50 <sharrush> Shawn: What if we put a checklist text box before each section?
14:17:12 <Laura> -1 to checkbox
14:17:27 <MarkPalmer> -1 to checkbox as well
14:17:28 <sharrush> ...an advantage to that would make it clear that the first is the heading and the following is what to do.
14:17:31 <brent> -1 to checkbox and bold
14:17:57 <Howard> -1 to checkbox - would make it visually confusing
14:19:06 <sharrush> Shawn: Question is to proceed with 151 as it is without the bold or continue discussion (removing "new" from audio contnet?
14:19:08 <dmontalvo> q+ to ask Will we change to "Things to consider"?
14:19:20 <brent> ack dm
14:19:20 <Zakim> dmontalvo, you wanted to ask Will we change to "Things to consider"?
14:19:48 <Howard> -1 want heading to change
14:20:08 <sharrush> s/contnet?/content?)
14:20:27 <Jade> aspects is in the intro paragraph, aspects to consider
14:20:31 <Howard> "Areas to Address"
14:21:27 <sharrush> Estella: The problem with Things to Do is that it requires a verb to answer
14:21:45 <Laura> How is Requirements for Accessible Media
14:22:19 <sharrush> Shawn: What about the idea of no heading at all?
14:22:47 <Laura> +1 to no heading also
14:22:51 <estella> how about using the same heading as in version 149 "A/V Media Accessibility at a Glance"
14:23:24 <sharrush> Shadi: The summary and What to do could be together with nonvisible heading
14:23:53 <sharrush> Shawn: What about no heading at all?
14:23:57 <Howard> -1 for no heading
14:23:57 <dmontalvo> +1 for no headings at all in that page
14:24:01 <estella> +1
14:24:18 <Howard> q+
14:24:26 <shawn> ack h
14:24:26 <brent> ack how
14:25:23 <sharrush> Howard: I think it helps to organize the page without having to read everything. If we can't come up with a heading, what is the section about?
14:25:54 <sharrush> Brent: It is a summary of the compenents of accessible media
14:26:43 <sharrush> Howard: I like componenets of Accessible Media
14:27:06 <sharrush> s/componenets/components
14:28:47 <sharrush> Brent: You made a good point - if you can't put a heading on it, what is the point?
14:29:00 <sharrush> Shawn: Here is what it would look like if it did not have headings
14:29:05 <Laura> q+
14:29:07 <Howard> -1 don't like it
14:30:10 <sharrush> Shadi: I am swinging toward having no headings. It is an overview page. The whole page is a starting paragraph and a list to the details
14:30:32 <brent> ack laura
14:30:50 <sharrush> KrisAnne: You do not need the bolding under audio content and video content.
14:31:06 <sharrush> s/KrisAnne/Laura
14:31:33 <sharrush> Shawn: Building another version with no summary box and no example
14:31:46 <brent> q+ to say reminder about bolding
14:32:42 <Sylvie> q+
14:33:15 <brent> ack sylvie
14:33:22 <shadi> +1 to no headings
14:33:28 <estella> q+
14:34:03 <sharrush> Sylvie: I am wondering why after the summary there are two paragraphs and the are links with semicolons and it seems they might better be presented as headings
14:34:51 <sharrush> Shawn: We could but right now there are eight things we want people to be aware of, each has a link and two sentences. Seems that headings might be overkill.
14:35:17 <sharrush> Sharron: Suggestion for heading: What You Should Know
14:35:32 <sharrush> Daniel: Each of the links is a list item on its own, right?
14:36:09 <Howard> q+
14:36:17 <Laura> q+
14:36:33 <brent> ack est
14:37:08 <brent> q+ later
14:37:22 <brent> q-
14:37:49 <sharrush> Estella: I like it without the headings but have a bit of a problem with the text that says it is about something that is not followed up in the parapgraph. It includes a reference to guidelines that are not then mentioned in the test below.
14:37:57 <brent> ack howard
14:39:58 <sharrush> Howard: Again if there is a configuation that others all like, I can go with it. But looking from the persepctive of someone coming to know what to do. Without some structure to the information it makes it hard to know how to proceed. Something that directs me to an action and tells me what I am looking at and to break up the information. Otherwise too hard to figure out.
14:40:06 <sharrush> ...but will go with the consensus.
14:40:29 <sharrush> s/configuation/configuration
14:40:52 <brent> ack laura
14:41:35 <sharrush> Laura: I was going to say that I don't feel strongly. I prefer it without the heading, but will go either way.
14:41:56 <krisannekinney> q+
14:42:06 <sharrush> Shawn: I am hearing lots of flexibility, which is great...
14:42:12 <brent> ack kris
14:43:08 <sharrush> KrisAnne: I have no strong feelings about headings from my perspective. The icons help break information apart. I agree with headings since it helps others. Wondering if removing them makes navigating the page more cumbersone?
14:43:27 <estella> +1 to KrisAnne
14:43:44 <dmontalvo> q+ to say that i don't see a navigation issue in this page, this would apply to longer pages with more sections than this one
14:43:57 <sharrush> Shawn: I added the heading only becasue of the example
14:44:13 <sharrush> s/becasue/because
14:44:51 <Sylvie> +1 to Daniel, because it is a short page
14:45:14 <brent> ack dm
14:45:14 <Zakim> dmontalvo, you wanted to say that i don't see a navigation issue in this page, this would apply to longer pages with more sections than this one
14:45:32 <krisannekinney> +1
14:45:40 <sharrush> Shawn: Proposal on the table, no headings, no summary box. Is everyone OK with that even if not your preference?
14:45:45 <dmontalvo> +1
14:45:45 <Laura> +1
14:45:47 <krisannekinney> +1
14:45:47 <Jade> +1
14:45:49 <shawn> +1
14:45:49 <Howard> 0 will go with consensus
14:45:52 <MarkPalmer> +1
14:45:54 <brent> +1
14:45:57 <estella> +1
14:46:15 <Sylvie> +1
14:46:29 <sharrush> Shawn: Thanks for discussion and sharing of ideas.
14:46:40 <brent> ack b
14:46:53 <sharrush> ...next is bolding in the storyboarding section. Go back to requirements.
14:47:08 <shawn> [novice video maker]   I'm recording a video presentation for a remote conference (and I'm already a bit overwhelmed about it). What do I need to do for accessibility?
14:47:34 <sharrush> ...one of the scenarios was a novice video maker and we really wanted to hone in on that scenario.
14:48:57 <Vicki> Vicki has joined #eo
14:49:09 <sharrush> ...do we want that phrase bolded or is there another way? You're a conference organizaer and people are making videos for your online conference. The resource we want to provide is that third section and we want to be sure they are led to the most useful section most easily. Do we want to leave the bolding?
14:49:14 <Laura> q+
14:49:33 <sharrush> s/organizaer/organizer
14:49:50 <krisannekinney> q+
14:50:15 <sharrush> Shadi: Do there people see themselves scripting and storyboarding?
14:50:15 <Howard> q+
14:50:19 <brent> ack laura
14:50:28 <estella> q+
14:50:51 <Howard> +1 to not bolding
14:50:57 <brent> ack kris
14:50:58 <sharrush> Laura: Do not need to bold it, it is clear what you are saying. People are looking for AV content - it would be a mystery why that it bolded.
14:51:21 <Howard> -q
14:51:25 <shadi> q+
14:51:46 <sharrush> KrisAnne: I agree with Laura. I think your use case is realistic and would try to figure out how to bring someone to this page without the bolding which is just puzzling.
14:52:15 <sharrush> ...it is a need but you are not satisfying it by bolding just a phrase within it.
14:52:25 <brent> ack est
14:52:26 <sharrush> Shawn: OK will remove the boding.
14:52:36 <sharrush> Estella: Yes I agree with removal of the bolding
14:53:35 <sharrush> ...we have recently produced remote conferences and we point to the Guidelines. You look for a resource with a checklist and bullet points to send to speakers.
14:54:33 <brent> ack shadi
14:55:28 <sharrush> Shadi: I think I understand why you have the "new" bolded after these comments. I wonder if instead you want to emphasize the "recording" aspect of it.
14:56:24 <sharrush> Shawn: Can we take that as a separate issue?
14:56:29 <sharrush> Shadi: Yes
14:56:56 <sharrush> Shawn: I will accept that as a potential future enhancement.
14:57:36 <brent> New second page:https://deploy-preview-151--wai-media-guide.netlify.app/media/av/users-orgs/
14:57:37 <sharrush> Shawn: And the final question is on page 2, the phrase user experinces
14:57:56 <sharrush> s/experinces/experiences
14:57:58 <shawn> https://deploy-preview-151--wai-media-guide.netlify.app/media/av/users-orgs/
14:59:13 <sharrush> Shawn: This takes content that was previously on the first page, breaks up the headings into one additional section. To answer your comment Daniel, 'user experince' is a well used phrase in the UX community and that is why it is used here.
15:00:43 <JasonMcKee> i have to jump to a meeting everyone. looking forward to many more in this new year!
15:01:15 <estella> q+
15:01:28 <brent> ack est
15:01:29 <shawn> ack e
15:01:59 <sharrush> Estella: I am going to Daniel's point, could we say "User experiences"?
15:03:21 <sharrush> Shawn: I had a GitHub issue for this because it is everything - user needs, user requirements, uer experiences - it is addressed Ihope in all the examples given here.
15:04:24 <sharrush> ...anyone in the UX field - and that includes me - will understand the broad range of what this page is meant to communicate. So I need your input.
15:04:45 <sharrush> s/uer/user
15:04:56 <shawn> q?
15:05:01 <sharrush> s/Ihope/I hope
15:05:14 <MarkPalmer> +1 to as it is
15:05:18 <sharrush> Howard: I like it as it is.
15:05:25 <sharrush> +1 to as it is
15:05:35 <Jade> +1
15:05:37 <Vicki> +1 as Howard
15:05:38 <Laura> +1 as is
15:05:43 <brent> +1 as is
15:05:58 <Sylvie> +1 as is
15:06:38 <Howard> +1 as is
15:06:51 <shadi> q+
15:07:03 <brent> ack sha
15:07:24 <sharrush> Shawn: Any other issues? Is it able to be published with the understanding that I am still around to make changes?
15:07:52 <sharrush> Shadi: Could we change the order of the last two sections? A thought don't feel strongly.
15:08:20 <sharrush> Shawn: Yes I actually like that idea, will take a pass at that. Is everyone OK with that or need to see it again?
15:08:27 <sharrush> OK with editor's discretion
15:08:39 <shadi> +1 to Editor's discretion
15:08:42 <Laura> +1
15:08:44 <brent> Agree with changing order. okay with editors discretion
15:08:44 <estella> +1
15:08:49 <Vicki> +1
15:08:51 <Jade> +1
15:08:52 <Howard> +1 to editor's discretion
15:08:53 <krisannekinney> +1
15:09:01 <MarkPalmer> +1
15:09:01 <Sylvie> +1 to editor's discretion
15:09:06 <dmontalvo> +1 to editor's discretion
15:09:59 <sharrush> Shadi: Mild comment to say I am bothered by the shopping cart with monetary for benefits, some benefits are not monetary.
15:10:12 <sharrush> Shawn: What if we add the inclusive icon as well?
15:10:45 <sharrush> OK with editor's discretion on the icons
15:10:52 <shadi> +1 to Editor's discretion
15:11:13 <sharrush> Shawn: OK, anyone else?
15:11:46 <sharrush> RESOLUTION: Publish the changes with the permission for editor's discretion to address a few tweaks.
15:12:11 <sharrush> Sharron: +1
15:12:12 <Howard> +1 to publish
15:12:12 <Laura> +1
15:12:12 <brent> +1
15:12:13 <Vicki> +1
15:12:15 <shawn> +1
15:12:15 <Jade> +1
15:12:17 <estella> +1
15:12:26 <Sylvie> +1
15:14:30 <sharrush> Topic: COGA Survey
15:15:19 <sharrush> Brent: It is open until Jan 11, the questions walk you through each piece of it. We will meet on Monday with the COGA group so please do take the survey.
15:15:36 <sharrush> Scribe: Brent
15:16:33 <brent> Sharron: EOWG is appreciative of the work that the COGA group has done with the Content Usable document.
15:18:00 <brent> ... We want to continue to offer support and constructive comments.
15:18:42 <brent> Sharron: Are their any more comments or recommendations that have not been put in the survey yet?
15:19:20 <Sylvie> Q+
15:19:29 <brent> ack syl
15:24:44 <sharrush> Scribe: Sharron
15:25:12 <sharrush> Topic: Work for this Week and wrap-up
15:25:46 <sharrush> Brent: Please try to complete the survey and other taks for this work.
15:25:54 <sharrush> s/work/week
15:26:06 <sharrush> Topic: Curricula (optional)
15:26:31 <dmontalvo> https://wai-curricula.netlify.app/curricula/
15:26:45 <sharrush> Daniel: Briefly, we had a survey, I am processing comments. Thank you very much for the input. There are two things I would liek to have clarification of
15:26:59 <sharrush> s/liek/like
15:28:42 <sharrush> Daniel: There was comment to shorten the summary . For example not mention each  module but just refer to them. Down below we will link to the other modules. So I would like to know how the group feels and to get other input if you ahve it.
15:28:54 <sharrush> Brent: Is this the shortened version?
15:29:09 <sharrush> s/ahve/have
15:29:23 <Laura> q+
15:30:19 <Howard> summary box too long
15:30:27 <brent> ack laura
15:30:31 <sharrush> Brent: Looking at the summary box, can we make it shorter? Do people feel this is good or needs to be shortened.
15:31:14 <sharrush> Laura: I really like this page and like the detail. I like the table. I have not specifcally focused on the summary but first impression is that it may not need to be shortened.
15:32:31 <sharrush> Daniel: And second questions is that there are use cases within the overview - is that confusing?
15:32:34 <dmontalvo> https://deploy-preview-307--wai-curricula.netlify.app/curricula/
15:32:41 <brent> q+
15:32:48 <sharrush> s/questions/question
15:33:02 <Howard> would change "Accessibility Curricula Overview" heading to "Using this Curricula" or something like that.
15:33:11 <krisannekinney> q+
15:33:31 <sharrush> Daniel: Here is the pull request with a shorter summary and has divided the overview and the use cases into separate sections.
15:34:43 <Howard> I like the original one better also.
15:34:47 <sharrush> Brent: My concern when I look at the proposed one, I like the  original one better. The proposed version seems to confuse how to use it with an overview.
15:34:58 <Howard> q+
15:35:09 <brent> ack me
15:35:35 <sharrush> Shadi: Ironically, the list was removed from the summary but then the summary actually became longer and harder to use.
15:36:18 <Howard> I prefer 307. I was confused also.
15:36:47 <sharrush> Brent: 307 is the proposed version - I was looking at it backwards. So yes, I definitly like 307 better.
15:37:31 <krisannekinney> q-
15:37:39 <krisannekinney> yes I like 307 better, I was looking at the wrong one too.
15:37:51 <brent> ack howard
15:38:17 <sharrush> Howard: I agree, 307 is the one I like better and was also confused. It is more concise and better organized.
15:38:53 <sharrush> KrisAnne: I am glad you changed "people in IT" to "People in digital tech" 307 is good.
15:39:22 <Vicki> Sorry, I need to leave.  Bon weekend!
15:39:48 <sharrush> Daniel: Good I am hearing it is going in the right direction and needs a bit more polishing. Thanks. Next question is the developer module.
15:40:14 <sharrush> ...we link only to specific foundation modules but the question is on this page
15:40:26 <brent> Developer Modules: https://deploy-preview-273--wai-curricula.netlify.app/curricula/developer-modules/
15:41:52 <sharrush> Daniel: We have a question "Prerequisites" that links to specific modules from previous. We want to communicate that students will need to have acheived learning objectives from some but not all of the previous modules.
15:42:29 <Howard> Not an issue for me.
15:42:32 <sharrush> Brent: So the issue is to let people understand that prerequisites are a subset, not all, of the Foundation modules. Is it even an issue?
15:43:11 <sharrush> Sharron: It would not hurt to clarify that it is a subset.
15:43:51 <estella> +1 to following
15:44:13 <Laura> "from these specific Foundation modules"
15:44:27 <Sylvie> What about adding: "in particular the following modules"?
15:44:30 <sharrush> KrisAnne: Maybe say "these specific Foundation modules" or use "subset" or something to indicate that.
15:44:49 <Sylvie> q+
15:44:54 <sharrush> Daniel: OK I will change that.
15:45:02 <brent> ack syl
15:45:12 <sharrush> Brent: Yes, subset is good because it indicates it is not complete.
15:45:51 <sharrush> Sylvie: You must understand concepts and these specific learning outcomes in particular.
15:46:19 <sharrush> ...instead of saying subset.
15:46:55 <sharrush> Daniel: Thanks for the input will take into consdieration, is editor's discretion OK?
15:47:07 <sharrush> Brent: Yes, just need some kind of clarification.
15:47:35 <sharrush> s/consdieration/consideration
15:47:58 <sharrush> Shadi: Reconsdier "developer modules expect" Expect is not quite right.
15:48:31 <sharrush> s/Reconsdier/Reconsider
15:50:09 <sharrush> Brent: OK thanks everyone and sorry we went late.
15:50:26 <sharrush> trackbot, end meeting
15:50:26 <trackbot> Zakim, list attendees
15:50:26 <Zakim> As of this point the attendees have been Shawn(first-part-only), Howard, Jade, Estella, Daniel, Brent, Shadi, Jason, Laura, Sharron, KrisAnne, sharrush, Mark, Sylvie
15:50:34 <trackbot> RRSAgent, please draft minutes
15:50:34 <RRSAgent> I have made the request to generate https://www.w3.org/2021/01/08-eo-minutes.html trackbot
15:50:35 <trackbot> RRSAgent, bye
15:50:35 <RRSAgent> I see no action items