12:25:29 RRSAgent has joined #eo 12:25:29 logging to http://www.w3.org/2011/06/24-eo-irc 12:25:50 Zakim has joined #eo 12:26:01 zakim, this will be eowg 12:26:01 ok, Sharron, I see WAI_EOWG()8:30AM already started 12:26:19 rrsagent, make logs public 12:26:42 Chair: Shawn 12:27:04 Scribe: Sharron 12:27:15 zakim, who is here/\ 12:27:15 I don't understand 'who is here/\', shawn 12:27:17 zakim, who is here? 12:27:17 On the phone I see ??P2, +1.781.598.aaaa 12:27:19 On IRC I see RRSAgent, judy, Sharron, suzette, shawn, IanPouncey 12:27:28 +Shawn 12:27:50 zakim, 781 is Char? 12:27:50 sorry, shawn, I do not understand your question 12:27:57 zakim, aaaa is Char? 12:27:57 +Char?; got it 12:28:13 Char has joined #eo 12:28:23 zakim, who is here? 12:28:23 On the phone I see ??P2, Char?, Shawn 12:28:24 On IRC I see Char, Zakim, RRSAgent, judy, Sharron, suzette, shawn, IanPouncey 12:28:34 zakim, Char? is really Char 12:28:34 +Char; got it 12:28:48 Regrets: Shadi, Alan, Emmanuelle, Liam, Helle 12:29:06 AndrewA has joined #eo 12:29:45 +Sharron 12:29:46 suzette2 has joined #eo 12:29:56 +Cliff 12:30:27 +Judy 12:31:35 Topic: Harmonization Document 12:32:08 Judy: Thanks for the comments, have been editing and have posted new version with a few notes in email. 12:32:18 + +1.443.517.aabb 12:33:06 ...from that I have a few things that we could discuss rather than take the whole docuemtn from the top again. I will queue up the comments I've received and if there's time at the end of today's meeting to take general comments. 12:33:32 zakim, aabb is Karl 12:33:32 +Karl; got it 12:33:39 zakim, who is here? 12:33:39 On the phone I see ??P2, Char, Shawn, Sharron, Cliff (muted), Judy, Karl 12:33:42 On IRC I see suzette2, AndrewA, Char, Zakim, RRSAgent, judy, Sharron, shawn 12:33:52 Sylvie has joined #eo 12:33:57 + +61.4.473.8.aacc 12:34:06 zakim, aacc is Andrew 12:34:06 +Andrew; got it 12:34:32 questions in e-mail: http://lists.w3.org/Archives/Public/w3c-wai-eo/2011AprJun/0123.html 12:34:48 +Sylvie_Duchateau\Tanguy_Lohéac 12:35:02 Judy: Looking at comments here, I wanted to check in with revisions to section headings. Do the new headings seem OK to folks? work with the flow? 12:35:08 zakim, mute me 12:35:08 Sylvie_DuchateauTanguy_Lohéac should now be muted 12:35:22 Shawn: The last one is a bit complex, could it be simplified? 12:35:32 +jennifer 12:36:04 Judy: The marked up document, I was not able to incorporate yet, but thanks for sending and I will get to it soon. 12:36:37 Shawn: simplify the heading to just "Using W3C standards and educational resources'? 12:36:43 last heading - just "Using W3C/WAI Materials" ? 12:36:46 KarlGroves has joined #eo 12:37:11 +??P12 12:37:14 Judy: Found a high misread of "resources" to mean the expectation of funding. 12:37:19 IanPouncey has joined #eo 12:37:29 +Wayne 12:37:43 Cliff: What if we say educational materials, that makes even clearer that we don't mean funding. 12:38:02 Judy: Does that couse any other problems? 12:38:42 Zakim, ??P12 is Ian 12:38:42 +Ian; got it 12:38:43 Shawn: No strong feeling either way. 12:39:22 Wayne: agree 12:39:31 All: yes no strong feelings 12:39:31 Zakim, ??P2 is Suzette 12:39:31 +Suzette; got it 12:39:39 zakim, who is here? 12:39:39 On the phone I see Suzette, Char, Shawn, Sharron, Cliff (muted), Judy, Karl, Andrew, Sylvie_DuchateauTanguy_Lohéac (muted), jennifer, Ian, Wayne 12:39:42 On IRC I see IanPouncey, KarlGroves, Sylvie, suzette2, AndrewA, Char, Zakim, RRSAgent, judy, Sharron, shawn 12:39:56 sinarmaya has joined #eo 12:39:57 Jennifer: My impression is that we don't use the word materials very often. 12:40:07 Wayne has joined #eo 12:41:30 Judy: a few people raised the issue of guidelines, standards, singular or plural when referring. I want to increase emphasis on other two standards as well, thought it can't be done uniformly. Is there one document that has standard use of the singular vs plural. 12:41:31 + +975903aadd 12:41:49 good morning :) 12:41:59 zakim, aadd is Emmanuelle 12:41:59 +Emmanuelle; got it 12:42:02 zakim, aadd is Emmanuelle 12:42:02 sorry, AndrewA, I do not recognize a party named 'aadd' 12:42:14 zakim, 975903aadd is Emmanuelle 12:42:14 sorry, Sharron, I do not recognize a party named '975903aadd' 12:42:51 Andrew: In the Exec Summ we say widely held standards, but only mention WCAG 12:43:27 Judy: so adding in others there and not worry about it being everywhere in the document 12:44:13 ...may be a copyediting issue, but wanted to bring it up for discussion. Whether standards should be referred to in singular or plural. 12:44:34 Shawn: Yes, we can do that as copyediting discussion rather than general EO. 12:45:12 Judy: Suggestion made to substitute for "principles" have made an alternative version... 12:45:17 http://www.w3.org/WAI/EO/Drafts/standards/standards_harmon_alt.html alt version with At a Glance 12:46:01 copy-editing suggestion "... worldwide standards, in particular WCAG" in open para of exec summary 12:46:11 Shawn: Could change the visual so its tighter and not distracting 12:47:12 suzette has joined #eo 12:47:27 Shawn: Can you say what the motives are for the two versions? 12:48:43 Judy: We had a good discussion but I could not figure out from the minutes where we landed from Wayne's suggestion regarding the inclusion of"At a Glance" verbiage. 12:50:00 zakim, mute me 12:50:00 Shawn should now be muted 12:50:10 ...when plugging it in, as is shown in the alt version, I think it flows better and makes more sense, but it is a pretty big piece of material to plunk into the middle. Is it distracting? Is there a risk that they will zero in on just that section? Policy makers may use as policy foundation and it is not for that. 12:50:43 Wayne: Even though it was my suggestion, now that I see it there, it is probably too much. 12:50:59 q+ 12:51:08 ack me 12:51:10 Judy: Any other reactions on this question. 12:51:33 Shawn: What is the goal for having it in there at all, to help us figure out what it is supposed to do. 12:52:14 Sylvie has joined #eo 12:52:37 Judy: For people who unlike you, do not live and breathe this, we need more context. For people who are just getting acquainted with these issues, they need more. 12:53:12 ...maybe examples should be stated within paragraphs rather than a list. 12:53:54 q+ to say in this case, I support not including the principles & examples here. point to http://www.w3.org/standards/webdesign/accessibility#examples & WCAg at a Glance instead 12:53:57 Cliff: I struggled a lot with that section. Once mentioned, it calls for far too much detail. The principles stated alone, especially operable and robust are ambiguous. 12:54:21 ...when they are introduced they require far too much explanation. 12:55:41 Judy: My experince when interacting with policy makers is that they want a map of some sort. The question then is what to provide. The principles, even with their problematic nature, may be better than the alternatives. 12:55:45 q+ to agree tat POUR is useful, but provisions are too selective 12:56:00 ack a 12:56:00 AndrewA, you wanted to agree tat POUR is useful, but provisions are too selective 12:56:07 ack me 12:56:07 shawn, you wanted to say in this case, I support not including the principles & examples here. point to http://www.w3.org/standards/webdesign/accessibility#examples & WCAg at a 12:56:11 ... Glance instead 12:56:43 Shawn: I would say that in this case, I would prefer not to include the principles and examples here. 12:57:10 IanP: agree 12:57:22 I agree with Shawn and Cliff 12:57:31 Andrew: I can see value in having the principles there, although I understand Cliff's point. I am less convinced about the need for the provisions as listed. 12:57:39 [shawn think including principles is not a showstopper for the draft] 12:58:25 [shawn thinks the principles won't help clarification that's needed] 12:58:27 Judy: My sense then is that with the difficulty of some of these examples and how lost people get in these materials...I would like to find a way to keep the principles in but point people off to more detailed examples. 12:58:39 q+ 12:58:49 ack me 12:59:08 Sandi has joined #eo 12:59:42 Shawn: I don't theing the principles would help that clarification. What about trying the listing of the words alone and then elaborating with some carefully chosen wording from WCAG at a Glance for each one? 12:59:47 +1 to shawn - could work 13:00:40 Judy: Let me play with that over the weekend. Moving on, let's look at the length and redundancy within the Executive Summary. 13:01:45 From http://www.w3.org/2002/09/wbs/35532/StdsHarmon201106June/results: I think the Exe Sum should be pared down quite a bit and significantly simplified. The document feels really repetitive in an uncomfortable way – because the Exe Sum is so detailed. The current version of the document is easy to skim, and I think future edits will make it even more highly skimmable. This relieves the some of 13:01:45 the burden from the Executive Summary. 13:01:45 The target audience for the Exe Sum is people who will only read a tiny bit (at least at first, we hope they’ll go back and read the rest later) – e.g., on their way into a meeting on accessibility policies. How about making it even more quickly consumable. For example, like a presentation has short bullets projected on screen but the speaker expounds on them – make the Exe Sum really direct, 13:01:48 very succinct, and a lot shorter, and then the rest of the doc expounds on the points for those who have the time or need to understand more. 13:02:25 q+ 13:02:31 ...I got strong feedback that it is important to have an ES, but suggestions to trim it down quite a bit. I would like feedback on current length and specific suggestions for tightening and making it more useful. 13:02:38 ack a 13:03:16 +??P18 13:03:37 Andrew: Nearly two pages out of seven when printed, too long. In terms of specific feedback, could bullets be reduced to bolded parts and expalnation within the body of document. 13:03:53 zakim, ??P18 is Sandi&Jason 13:03:53 +Sandi&Jason; got it 13:03:54 zakim: ??P18 is Sandi 13:04:28 s/expalnation within/explanation moved to within/ 13:05:04 Judy: What do people think about that suggestion? 13:05:26 suzette2 has joined #eo 13:05:31 ...There is some text that could be moved. 13:05:40 Judy: others? 13:06:01 Sharron: Exe Summ is really, really too long 13:06:02 clifftyllick has joined #eo 13:06:29 ... now it's trying to do more than an Exe Sum should do 13:06:45 Sharron: Think Ex Summ should be called something else or reformatted 13:07:32 Judy: If exec Summary were half the length, would it be acceptable? 13:07:49 ...anyone object? 13:07:54 q+ to say short bullet points for all sections. simplify paragraphs. 13:07:59 Wayne: Maybe 150 to 200 words 13:08:04 apologies that mibbit keeps dropping my irc connection 13:08:11 Ian: No that's too short. 13:08:30 Judy: Orignally we had a short Abstract and it seemed pointless 13:09:12 ...is there a good reason to have a succint version to give people quick grab at it. Does that purpose work for people? 13:09:37 yes 13:09:46 Cliff: Yes and just becasue we had a poorly written abstract is no reason not to have a well written Exec Summ of comparable length. 13:10:28 Judy: What other opportunities are there to tighten this up considerably while still maintaining greater length than 200 words. 13:10:44 Cliff: I could give a draft. 13:11:10 Judy: I am worried about reducing it to that length, but interested in what you can come up with. 13:11:30 ack me 13:11:30 shawn, you wanted to say short bullet points for all sections. simplify paragraphs. 13:11:34 -Cliff 13:12:30 Shawn: I was one who answered yes, we still need something. I imagine someone reading while rushing down a hallway. Thought about the slide version. Do an excercise and pretend you are making a slide presentation and see what's in there? 13:12:52 I''m sorry; I just broke a tooth as I was eating breakfast. Gotta leave... 13:13:18 ouch 13:13:28 ack me 13:13:48 clifftyllick has left #eo 13:13:51 ...not that you could read the Exec Sum and expect to understand everything, but I will get the points outlined for me. Short, succint, kind of punchy, grab and go. Elaboration within the document for anyone needing further understanding of the points. 13:14:12 s/I''m sorry; I just broke a tooth as I was eating breakfast. Gotta leave.../ / 13:14:20 s/ ouch/ / 13:15:13 Judy: May be a bit tricky to do at this point and also raises the issue of style. It combines bullets, parapgraphs. So I am not sure I am getting a picture of how the Exec Summary will look. Hesitate to return to dry paragraph. 13:15:44 ...discouraged about the need to change this so much. Any thoughts from anyone who has not spoken. 13:17:20 Sharron: You have some straightforward points abotu harmonizatin is good, fragmentation is bad, there are some specific reasons, here's what's in this doc. If the Exe Sum were the way you talk about it when you introduce it. 13:17:34 ... something that brings people in. 13:18:40 Judy: I have been doing that for years and it doesn't work. What works is when people see the detail of what benefits are brought to them through harmonization is much more effective. 13:19:43 ...could perhaps take the spirit of what you suggested and make one more pass at mapping that to soemthing that takes on the aspect of an Exec Sum. When I have watched people react to the high level message, it is not what we want. 13:20:39 ...so I don't want to lose what I have learned from experience and the experince of working with an editor who knew nothing about the topic. 13:22:11 Judy: Let's consider the clarity of the message around harmonization. There was aphrase in the Exec Sum "in developing policies ... widely recognized international standards..." 13:23:04 ...Helle said she did not understand that sentence. Wonder if phrase "taking advantage of..." makes it more difficult to understand. it is in the lead, don't want it to be a mystery. 13:24:17 Jennifer: what about maximize? I think I suggested "taking advantage of..." 13:24:43 Judy: I will try to get more specific suggestion and detail from Helle. 13:25:05 leveraged off the widely accepted standards 13:25:13 Sharron: benefitted 13:25:21 Shwn: benefitted from using 13:25:51 Andrew: yes, used and benefitted from 13:26:07 benefited from adopting? 13:26:14 Wayne: negaive connotation of taking advantage of 13:26:23 s/Shwn/Shawn/ 13:26:30 Wayne: profit by 13:27:01 Judy: will take those suggestion and move on to a logistical thing. Contents of the content box. 13:27:26 ...use of h2 It is a lot of words, uneven length to be in headings 13:27:39 ...what is the problem with mini-index 13:27:58 Shawn: Not informed well enough about what is in the document 13:28:28 ...need more than the one word description of each 13:28:50 ...should do the full section title as in other documents 13:29:23 Judy: Maybe the third one could be "Fragmentation Concerns," "Why Harmonization Helps" 13:29:38 Andrew: That's right 13:30:08 Judy: I will probably be going with an intermediate version, if acceptable. 13:30:22 Andrew: Yes, provides better picture of what is found. 13:30:54 shawn has left #eo 13:31:42 Judy: let's focus on use of bold face. Now it is inconsistant within the document. Have tried in some cases dropping bold face entirely. Like the idea if we can make it work to have bolded lead-in phrases to bring readers in. 13:31:50 suzette has joined #eo 13:31:53 ...what is general reaction. 13:32:36 shawn has joined #eo 13:33:21 ack j 13:33:21 Judy: Assuming we have a shorter, sweeter Ex Sum, advise on use of bold 13:34:06 Sharron: use bold. but way it is now is not consistent, and is distracting. 13:34:35 ... short phrases 13:34:44 +1 to sharron 13:35:04 Judy: So one of big problems is lack of consistancy? 13:35:13 Wayne: +1 13:35:25 +1 13:35:33 [Shawn had said that in her Survey comments] 13:36:05 Ian: One think I don't like about it is that it should stand alone. Put full stop at end of bolded part. of 13:36:15 [Shawn thinks nice practice, but not a hard requirement.] 13:36:36 Judy: May be difficult to fully avoid, but will take into consideration and avoid it more. 13:36:38 s/but not a hard requirement./but not a strict requirement./ 13:38:12 Judy: The bit about policies, suggested to use the longer phrase "local, regional,... etc" at first and then shorten to just "policies". Do people like the general direction of that? 13:38:16 Wayne: Yes 13:38:34 Judy: No objections? 13:38:38 All: none 13:39:32 Judy: Got feedback on using educational resources instead of educational and training resources. Wanted to ask about the distinction. Training programs seem to be a high priority and are part of planned costs. 13:40:16 ...can we mention three or four things in first mention and develop a shorter 'nickname' for the subsequent references. 13:40:41 q+ to say maybe try same thing - a long list of different categories first time in section. then a short term, e.g., "supporintg resources" 13:41:00 ...policy makers seem to be thinking of this in all those ways, how can we capture that? 13:41:14 ack me 13:41:14 shawn, you wanted to say maybe try same thing - a long list of different categories first time in section. then a short term, e.g., "supporintg resources" 13:42:12 Shawn: Yes, to do the same thing...technical, reference material, training materials, educationl resources. After that use the phrase "supporting resources" 13:42:24 good as all encompasing 13:42:38 Judy: OK, how does the phrase "supporting resources" work for all? 13:43:14 technical reference material, training curriculia, educational somethihng, and other supporting resources. 13:44:05 [Shawn ran out of steam Thursday night before reviewing the last section. Need a fresh brain to think about it] 13:45:02 Judy: Looks like we are getting to the bottom of the list, could people please look at last section of document. Let's double check ourselves. The history is that the first couple of reviews were labeled too much of a draft to even review. We read it and thought - yikes! really needs work. Have reorg-ed and restructured. Had "Step 1, Step 2..." which has been removed, but as of now, does it say 13:45:40 ...the right stuff? Seems to not match the rest of the document structure. Let's consider content first and structure second. Open to comment 13:46:46 Ian: Do we need the numbers? 13:47:43 Judy: It is only section with heading 3, so we left numbers to make distinction 13:48:19 q+ to say (after others talk) Content needs work -- but sorry, I ran out of steam late Thursday night and brain not fresh now. 13:48:26 Sharron: was in response to phrase "follow these steps" maybe should remove that reference in lead in paragraph 13:48:42 Judy: yes, remove steps reference and remove numbers 13:48:59 ...should they still be h3? 13:49:10 All: Sure 13:49:27 Jusy: But looks odd. Will experiment with style. 13:49:43 s/Jusy/Judy 13:49:57 ack me 13:49:57 shawn, you wanted to say (after others talk) Content needs work -- but sorry, I ran out of steam late Thursday night and brain not fresh now. 13:50:06 q+ 13:50:21 Judy: The content comes from years of experience but want to be sure it is complete. 13:51:06 ack Ian 13:51:06 Shawn: Need to step back. There is good stuff here, but not quite jelling. Need to step back and just one rewrite away from final. 13:51:40 Ian: May just be my preference but this many inline links is hard to read. 13:52:07 q+ to say keep links, just put at end of phrasw 13:52:11 Judy: density of links, good point. 13:53:46 ...styling will fix some of that. Look at fourth bullet in second section. Suggestions? 13:54:20 ...any other suggestions on content? 13:54:48 Ian: The last section I would like to see some of the resources brought into the main document. 13:55:01 ack me 13:55:01 shawn, you wanted to say keep links, just put at end of phrasw 13:55:56 Shawn: we want to show these good resources, just don't want to interrupt the flow 13:56:15 agenda+ Introduction 13:56:24 Judy: So let's consider how to do the links to resources and also note that we need to pick up a footnote or two. 13:58:18 ...proposal is to have very few, very selective links in Ex Sum, then no other external links until the last section "Using Resources". Set up that section so that it is more clearly a list of resources and some narrative. Kind of an introduced, terse suggestion about what to do with a full list of resources. 13:58:27 Andrew: would you do that as a list? 13:58:59 Judy: Then would give the impression of "Wow, these are alot of useful reosurces" rather than drwoning in inline links. 14:00:28 suzette has joined #eo 14:00:48 Judy: Relationship in talking about WCAG2 and talking about other Guidelines and ARIA. Aiming for soething a bit tricky. Most statements about WCAG2 can not be made about the others, which are not done yet and are not targets of policy adoption. 14:01:17 ...but we have found that some governments have seen the need for documents like these, but unaware that they exist. 14:01:45 ...what would be particularly helpful are places to mention these, but keep in right balance. 14:02:54 Shawn: This is a detailed, editing level task. Maybe first statements are very broad but narrow into WCAG discussion then come back out. Also, remove numbers and just reference ATAG and UUAG. 14:03:20 Judy: Yes but if any places hit you where it could be mentioned, let me know 14:04:04 Jennifer: Different numbers are assigned to the guidelines now, and so if you remove the numbers, it will be more easily maintained and consistant. 14:04:31 Shawn: Opneing statement talks about WCAG only and must change. 14:04:47 Judy: Then must rip apart opening statement of Exec Sum 14:04:53 Shawn: Then we must do it. 14:05:30 ...can benefit from using the widely accepted standards from W3C Web Accessibility Initiative. 14:06:34 Judy: Saying you can take advantage is different than praising those who already have, which was suggested by the group. 14:07:29 Andrew: It's WCAG in particular that we don't want to get fragmented, that we want harmonized. The content that governments are most concerned about is WCAG. 14:07:43 Judy: but we want the others to be considered 14:08:02 Andrew: benn impressed with how much ATAG has come up in discussion. 14:08:33 Judy: May be that there is a missing theme that will help pull in the others. 14:09:11 Wayne: We have heard your point about the robust needs of Exec Sum 14:10:01 zakim, take up agenda 1 14:10:01 agendum 1. "Introduction" taken up [from shawn] 14:10:30 Judy: Feedback has been useful, shaped the doc. Skimmed additional comments, Andrew yours can be handled editorially. So to talk now about status of introduction 14:11:30 Shawn: Many people reading this document will have an experince much higher that the 28% web use that is cited. 14:12:06 Judy: May need to recognize gap between mobile use and stat cited. 14:12:18 s/higher that/higher for their country than/ 14:12:42 Shawn: when considering the introduction, maybe the wording from the Exec Summary needs to be brought down into the document itself. 14:13:47 Judy: Jennifer's suggestion about reshaping and polishing first paragraph of Intro 14:14:29 ...during the day today if people could make suggestions for the intro, would be appreciated. 14:15:18 Jennifer: In terms of facts, I remind us to cite source of facts even if in footnote. 14:17:48 Judy: Hope to have new version by Saturday. Interested that comments seem to trend toward do-able changes needed, document taking shape, looking good etc 14:18:48 ...but at same time, we have had suggestions for significant changes to parts that I thought were done. It's possible that I will introduce elements that people object to. Have a time constraint with a limited time offer for translation. 14:19:13 ...the offer ends at end-of-day Monday. 14:20:35 ...One suggestion is that I will do my best to version it up by Saturday, hope for your comments by mid-day Monday, then could roll those into what will be submitted to translator byt Monday. 14:21:00 ...then we need EO to confirm willingness to publish as Draft for public review. 14:21:34 ...is that timeline OK for anyone? 14:22:33 Wayne: can be available 14:22:39 Jennifer +1 14:22:42 Ian: +1 14:23:29 Sharron +1 14:24:13 ack m 14:24:35 http://www.w3.org/2002/09/wbs/35532/StdsHarmon201106June/results 14:24:41 Shawn: Two people are on vacation. 14:26:18 Judy: Will let process take its course, but to the extent that people are able to read and comment, before noon Monday will be most useful. 14:26:29 -Sandi&Jason 14:26:30 -Karl 14:26:56 Topic: Business Case Slides 14:27:47 Shawn: If you have been following the recent changes, are we ready for approval? 14:27:58 Yes for two weeks 14:28:11 ...if I put out survey for two weeks, is that good? 14:28:38 Sharron +1 14:28:58 Jennifer: would be great to get this wrapped. 14:29:05 Sandi has left #eo 14:29:09 Shawn: Will also send list of what has changed 14:29:18 Wayne: much appreciated 14:30:29 Shawn: It's taken quite a bit of back-and-forth 14:30:47 Ian: can you send email of what still needs doing on web version of slides? 14:31:00 Jennifer: we are meeting next Friday? 14:31:14 Shawn: depends on Harmonization document and Judy. 14:31:29 Jennifer; wondering becasue of holiday weekend and such 14:32:58 Shawn: yes, 16 people can meet, so we should tentatively plan on meeting. Will discuss Biz slides on July the 8th. Thanks all, adjourned 14:33:07 rrsagent, draft minutes 14:33:07 I have made the request to generate http://www.w3.org/2011/06/24-eo-minutes.html Sharron 14:33:32 -Ian 14:33:35 zakim, who was here? 14:33:35 I don't understand your question, AndrewA. 14:34:03 bye! 14:34:10 -Sylvie_DuchateauTanguy_Lohéac 14:34:54 http://blog.knowbility.org/ 14:36:01 -Judy 14:36:23 IanPouncey has joined #eo 14:37:57 -Char 14:38:03 zakim, who i shere? 14:38:03 I don't understand your question, shawn. 14:38:07 zakim, who is here? 14:38:07 On the phone I see Suzette, Shawn, Sharron, Andrew, jennifer, Wayne, Emmanuelle (muted) 14:38:10 On IRC I see IanPouncey, shawn, Sylvie, Wayne, sinarmaya, AndrewA, Char, Zakim, RRSAgent, judy, Sharron 14:38:31 -Emmanuelle 14:38:34 sinarmaya has left #eo 14:38:49 -Sharron 14:38:50 -jennifer 14:38:50 -Andrew 14:38:52 -Wayne 14:38:54 -Shawn 14:43:43 Sharron has left #eo 14:43:53 disconnecting the lone participant, Suzette, in WAI_EOWG()8:30AM 14:43:57 WAI_EOWG()8:30AM has ended 14:43:58 Attendees were +1.781.598.aaaa, Shawn, Char, Sharron, Cliff, Judy, +1.443.517.aabb, Karl, +61.4.473.8.aacc, Andrew, Sylvie_Duchateau\Tanguy_Lohéac, jennifer, Wayne, Ian, Suzette, 14:44:01 ... +975903aadd, Emmanuelle, Sandi&Jason 14:45:44 Thanks shawn, got the emai. 14:46:06 great 14:46:29 IanPouncey1 has joined #eo 14:47:26 IanPouncey1 - If any questions, I'll be around for a little bit now, possibly a little on Sat, but totally offline during the week w/o e-mail access 14:50:33 Meeting: EOWG 14:53:15 np, I'm back to work now, so I'll have to look at it properly later. 14:54:27 Present: Sylvie, IanP, Suzette, Shawn, Sharron, Andrew, Jennifer, Wayne, Emmanuelle, Judy, Karl, Cliff(firstpart), Sandi(secondpart), Jason(secondpart) 14:54:35 rrsagent, draft minutes 14:54:35 I have made the request to generate http://www.w3.org/2011/06/24-eo-minutes.html shawn