20:01:17 RRSAgent has joined #wai-wcag 20:01:17 logging to http://www.w3.org/2005/04/14-wai-wcag-irc 20:01:24 RRSAgent, make log world 20:01:28 +??P8 20:01:33 zakim, ??P8 is Makoto 20:01:33 +Makoto; got it 20:01:38 -Bengt_Farre 20:01:42 mcmay has joined #wai-wcag 20:02:08 +Matt 20:02:10 agenda? 20:02:13 +Sebastiano_Nutarelli 20:02:19 Agenda: http://lists.w3.org/Archives/Public/w3c-wai-gl/2005AprJun/0122.html 20:02:23 agenda+ TTF summary 20:02:26 -Makoto 20:02:31 agenda+ Agenda overview 20:02:34 +[Microsoft] 20:02:37 agenda+ Guide Doc and Structure proposals 20:02:43 agenda+ Update on 4.2 and conformance 20:02:48 zakim, Sebastiano_Nutarelli is Bengt_Farre 20:02:48 +Bengt_Farre; got it 20:02:49 agenda+ Looking ahead: Work Plan and scheduling next F2F 20:02:50 zakim, who's on the phone? 20:02:51 On the phone I see Mike, Yvette_Hoitink, John_Slatin, Gregg_and_Ben, Wendy, Loretta_Guarino_Reid, Becky_Gibson, Christophe_Strobe, Matt, Bengt_Farre, [Microsoft] 20:02:53 zakim, I am Bengt_Farre 20:02:53 ok, bengt, I now associate you with Bengt_Farre 20:03:03 agenda+ review of baseline issues and attempt to close those that seem ready to close 20:03:15 +??P9 20:03:16 zakim, ??P9 is Makoto 20:03:16 +Makoto; got it 20:04:04 zakim, mute me. 20:04:04 sorry, Makoto, I do not see a party named 'me.' 20:05:14 Regrets: Sebastiano Nutarelli, Roberto Ellero, Roberto Castaldo, Roberto Scano, WATANABE Takayuki, Andi Snow-Weaver, Neil Soiffer, Tim Boland 20:05:23 Chair: John and Gregg 20:05:37 zakim, take up item 2 20:05:37 agendum 2. "Agenda overview" taken up [from wendy] 20:06:30 zakim, close item 2 20:06:30 agendum 2 closed 20:06:31 I see 5 items remaining on the agenda; the next one is 20:06:32 zakim, take up item 1 20:06:33 1. TTF summary [from wendy] 20:06:34 agendum 1. "TTF summary" taken up [from wendy] 20:06:39 http://www.w3.org/2005/04/13-wai-wcag-minutes 20:06:50 zakim, mute me 20:06:50 Yvette_Hoitink should now be muted 20:06:51 +JasonWhite 20:06:55 -JasonWhite 20:07:14 WHO's TAKING MINUTES? 20:07:16 TTF looked at proposal from UAAG and PF 20:07:21 a, ok :-) 20:07:37 prototyping how to use rel and link for in page navigation 20:07:52 scribe: Becky_Gibson 20:08:15 discussed our concerns; Wendy has action item to bring this to xtech group 20:08:47 looked at DM's review of object test files; action for WC, CR, DM, MC to look at object test files 20:09:15 BG and DM tooked at some test files with respect to baseline and determining UA support 20:09:42 JA took action to update UA matrix; JS will be looking at different AT support - and see what info they can provide 20:09:52 +JasonWhite 20:09:56 JS will raise issue about object support with PF group 20:10:17 JS had an idea about dividing techs into chapters and has sent summary 20:10:37 CR took action item to review test files 20:11:25 john's email: http://lists.w3.org/Archives/Public/w3c-wai-gl/2005AprJun/0129.html 20:12:53 js: MC had suggested talking about req. documents - but decided to wait until today's guide doc discussion for more input 20:12:59 becky? please type a colon after the speaker's initials (the clean-up script then can pick that out as the speaker) 20:13:03 ya - like that. ;) 20:13:14 zakim, close this item 20:13:14 agendum 1 closed 20:13:15 I see 4 items remaining on the agenda; the next one is 20:13:17 3. Guide Doc and Structure proposals [from wendy] 20:13:34 zakim, take up item 3 20:13:34 agendum 3. "Guide Doc and Structure proposals" taken up [from wendy] 20:14:11 js: want feedback on Guide Doc draft - questions, concerns, info to help us clarify and determine how to move forward 20:14:36 js: at LA F2F attendees decided need a doc to provide stronger bridge betwn guidelines and techs 20:14:46 http://lists.w3.org/Archives/Public/w3c-wai-gl/2005AprJun/0121.html 20:14:53 js: want to provide more info than envisiones for techs doc 20:15:30 js: provide rationale for SC; so understand what it says and why; statements of benefits of SC; plus gen techs 20:15:42 JS: and links to specific techs 20:16:03 js: JS mocked up sample outline and sent to subgroup for comments on the outline 20:16:31 js: once outline agreed upon sent it to folks in group to work on specific SC 20:16:56 js: also sent outline to non-WCAG members to see if headings and descriptions made sense 20:17:49 js: group members filled in the outline for specific SC - these have been sent to the list 20:18:50 q+ 20:18:59 js: each group member took a slightly different track - and raised diff. issues 20:19:27 js: how to define terms, do the Guide docs do what we need to do? what do we say in certain sections 20:19:56 js: consistent feedback from group that received sample outline 20:20:21 js: every user had a completely diff. notion of what would fit under "Technology Independent Techniques" 20:20:36 js: and all were diff. from this group's notion of general techs 20:20:44 -Makoto 20:20:59 js: intent and benefits sections also caused confusion; also diff. between techs and samples 20:21:10 q? 20:21:10 rscano has joined #wai-wcag 20:21:15 ack y 20:21:38 +[IPcaller] 20:21:47 yh: devil's advocate: understand by Guide docs prepared but worried that we are throwing more work at the problem 20:22:25 yh: we seem to solve problems by trying to get more info; concerned readers of WCAG will contain too much information 20:22:34 yh: and people won't find info they really need 20:22:44 q+ 20:22:52 zakim, IPcaller is Makoto 20:22:52 +Makoto; got it 20:22:55 ack gregg 20:23:31 gv: as we write we need to not repeat things that have already been said/written 20:23:45 gv: need to focus on consiceness (sp?) 20:24:03 +Dave_MacDonald 20:24:25 gv: don't try to make a tutorial; should help people knowledgable in the area understand our intent 20:25:02 gv: wants to put in a vote for modularity idea - cite general techs by name that can be expanded as needed 20:25:20 gv: worried that whole doc is getting very big - too big to comprehend or look at 20:25:26 ack j 20:25:30 zakim, mute me 20:25:30 Yvette_Hoitink should now be muted 20:26:05 js: surprised to hear you say we are addressing this to audience that already has some understanding 20:26:23 David has joined #wai-wcag 20:26:24 js: from F2F thought it was to help people understand better than don't already have knowledge? 20:26:32 was me who joined late 20:26:46 js: if trying to provide overview for people who aren't familiar than think this is helpful 20:27:00 js: we need to clarify the audience served by the guide doc 20:27:40 gv: need info for those not familiar with WCAG 2.0 but need to assume audience is familiar with web tech 20:27:49 gv: don't want to repeat what EO is doing 20:28:11 gv: but don't repeat info that is already in the techs 20:28:28 there are other working groups that has done similar initiatice? 20:28:40 gv: audience should be able to read and understand techs without it being tutorial 20:29:01 gv: want to cover broad range of audiences but don't want too verbose and overlap with EO 20:29:23 js: that is why we wrote the drafts so we have something to look at and discuss 20:29:55 js: another idea discussed at F2F was that this doc would swallow up the gen. techs doc 20:30:40 js: for 1.1 L3 SC 1 - BC took existing content from gen. techs and put it into the guide doc; 20:31:12 js: then gen techs doc wouldn't need to exist separately OR guide doc would contain links to general techs 20:31:28 js: guide doc begins to act as traffic cop for navigation 20:31:57 js: also discussed if benefits should be in GL or be moved to the Guide doc? 20:32:15 js: hope the examples will help us understand the issues and resolve these questions 20:32:37 js: do Examples and benefits belong in GL? in Guide Doc? is it an either or? 20:33:07 js: GL can have brief benefits that get expanded in GD (guide doc) 20:33:21 js: do gen techs get subsummed into the GD? 20:33:37 js: looking for feedback from the group...... 20:33:43 q+ 20:34:16 dm: like the distinction of not overlapping with EO - imp. issue I hadn't thought of 20:34:36 dm: like techs to be in a separate document - think the audience will be different 20:34:55 dm: policy makers looking more at guide doc; devs and techs 20:35:02 ack dav 20:35:04 ack john 20:35:19 dm: scribe correction: devs looking at techs 20:36:05 js: no one outside of WCAG seems to think of gen. techs as a place to look for how to write good alt text 20:36:05 q+ 20:36:30 js: think of techs as code samples then get confused betwn gen and tech specific 20:36:57 q+ 20:37:04 js: still looking for a good name for general techs to make distincion clearer 20:37:05 ack gregg 20:37:50 gv: what if we list techniques by a single sentence name 20:38:11 gv: writing alt text so it is x y z.... 20:38:55 gv: each sentence has "ing" action word - each is a link to the specific technique document 20:39:29 q+ to say "What about other technologies?" 20:39:32 wc: BC suggested links to all techniques without specifying general or specific 20:39:45 wc: which is what I did in my mock up 20:40:15 q+ 20:40:15 gv: goal is to read document and if don't understand can click on a link for more information 20:41:33 wac reads the text from: http://lists.w3.org/Archives/Public/w3c-wai-gl/2005AprJun/att-0121/guide_to_G1.1L1SC2.html 20:41:41 ack wendy 20:42:00 ack ja 20:42:30 jw: if believe need benefits, examples, more info -then GD is a good idea; agree with JS that combine gen techs into GD 20:42:35 q+ 20:43:02 jw: imp that GL doc be as self contained as possible; user should be able to read and understand SC and purpose 20:43:08 ack y 20:43:09 Yvette_Hoitink, you wanted to say "What about other technologies?" 20:43:11 cs has joined #wai-wcag 20:43:14 jw: so don't want to see benefits and examples taken out of GL doc 20:43:46 yh: was suggested that could link from GD to tech specific techs - but have concerns because 20:44:17 q+ 20:44:22 yh: but as new techs docs for additional technologies occur then have to update GD 20:44:24 ack j 20:44:38 zakim, mute me 20:44:38 Yvette_Hoitink should now be muted 20:44:58 js: currently examples offered are just descriptions but don't link to any specific site 20:45:30 js: when asked outside group - they expected examples to be live links to examples on the web 20:46:06 js: can we do this as we move to candidate rec. since we have to prove viability with real examples 20:46:27 i think that user are usually served with guideline + techniques: more docs means more problems. why don't set guidelines + techniques with example? 20:46:44 js: much of what we write in GD might go back into GL as informative material 20:46:56 ack ben 20:47:06 (sorry only irc tonight) 20:47:53 bc: imp. to sep gen tech from GD - if include all the gen tech in the GD get too much info so other info about SC gets lost 20:48:23 bc: when look at benefits and ex. in GL it can be difficult to know which ex. goes with which SC 20:48:32 bc: GD really helps with this 20:48:38 ack gregg 20:49:27 gv: each tech in a separate doc has raised some ques. do we include gen in each technology specific doc? 20:49:42 gv: also issues when use multiple techs ex: html & css 20:50:02 gv: we understand that new techs will have to be added; that is why GD is non-normative so 20:50:10 gv: it can be refreshed as needed 20:50:59 gv: worry about issue when need multiple techs working together - worry if each of those techs are on separate pages will lose some context for problem being sovled 20:51:17 q+ 20:51:30 +??P11 20:51:50 ack js 20:51:50 gv: links for examples is good idea for GD and techs but not in GL; can't have links to real sites in normative GL 20:52:31 js: maybe that is one way for GD to differentiate itself; try to make short ex. descriptions in GL related to real ex. links in GD 20:53:11 q+ 20:53:14 js: suggest group working on these examples get back together to review the issues raised today 20:53:42 zakim, ??P11 is Joe 20:53:42 +Joe; got it 20:53:47 js: would like to hear from others not as closely involved in the GD 20:53:47 ack dav 20:54:05 dm: have GL 1.0 open and it does link to techniques 20:54:24 js: can link to our own docs but not outside of our doc 20:54:52 gv: any more comments? 20:55:18 action: js, bc, wac, et al, continue work on guide doc 20:55:22 zakim, close this item 20:55:22 agendum 3 closed 20:55:23 I see 3 items remaining on the agenda; the next one is 20:55:24 4. Update on 4.2 and conformance [from wendy] 20:55:26 zakim, take up item 4 20:55:26 agendum 4. "Update on 4.2 and conformance" taken up [from wendy] 20:56:10 js: LG, JC, WC and DM? on call yesterday about 4.2; Loretta please update us on 4.2 20:56:25 lg: trying to understand web apps and what is role of UUAG and ATAG relative to them 20:56:43 lr: wc wrote up a summary to try and define UA and web app 20:57:04 lg: looks like we will need to selectively ref. parts of ATAG and perhaps UAAG 20:57:52 gv: you are seeing the need for a 4.2 and would apply to interface delivered as content? 20:58:19 lg: not sure we need 4.2 but maybe more specifcs in other GL. ex. GL 1.3 would require that 20:58:28 lg: state info should be exposed 20:58:47 q+ 20:58:54 zakim, who's making noise? 20:59:04 wendy, listening for 10 seconds I heard sound from the following: John_Slatin (2%), Gregg_and_Ben (15%), Christophe_Strobe (19%) 20:59:15 zakim, must Christophe 20:59:15 I don't understand 'must Christophe', wendy 20:59:23 zakim, mute Christophe 20:59:23 Christophe_Strobe should now be muted 20:59:27 js: issues of struct and func. lead to discussion of what is diff. between UA and web app 20:59:44 q+ to make a quickie clarification 21:00:02 q+ 21:00:05 js: result from yesterday was better understanding of questions that need to be asked 21:00:28 js: for ex. what do authors need to do to allow UA to render info in a more accessible way 21:00:29 -Mike 21:00:54 ack joe 21:00:54 joeclark, you wanted to make a quickie clarification 21:00:57 js: action to map GL to checkpoints in UA - not sure anyone has taken it up 21:01:34 jc: GL 1.3 does say .....separable from presentation; should be structure, presentation and behavior 21:01:44 zakim, unmute me 21:01:44 Yvette_Hoitink should no longer be muted 21:02:04 jc: structure==html; presentation==css; behavior==javascript (as exmaples) should use this format 21:02:11 gv: where is information? 21:02:33 jc: no one will create empty document with just

- no web pages with no content 21:02:58 gv: is important to say that info is separate from presentation - that is intent of the GL 21:03:20 jc: can use CSS to add content - but existing wording is problematic 21:03:36 q+ to ask "1.3 summary" 21:03:50 js: JC to take action to explain this better 21:03:50 action: joe write proposal for rewording on guideline 1.3 ala structure, presentation, behavior and explanation how it address gv's concern about separating out information. 21:04:20 gv: remember that orig inspiration of 1.3 was to maintain original information in alternate presentations 21:04:27 ack gregg 21:04:29 intent of 1.3 to ensure that info is preserved when presentation format changes 21:05:05 gv: if content acts as UA follow UAAG; if authors content follow ATAG was suggested last week 21:05:46 do we want to solve this now or is this what the group should be doing on our call tomorrow? 21:05:50 gv: sometimes UA separately, somtimes get with something else 21:06:29 gv: same rules for shipping UA separately and as part of content 21:06:43 q+ to say that content doesnt' function as a UA 21:06:56 ack y 21:06:56 Yvette_Hoitink, you wanted to ask "1.3 summary" 21:07:00 gv: also helps to cross link the guidelines 21:07:37 yh: back to 1.3 comment from JC - was going to 1.3 summary for next week - should I do 2.4 next week so can incorporate JC's proposal 21:07:57 yh: or better to do my 1.3 summary and have it to discuss with JC's 1.3 proposal 21:08:39 gv: have JC to issue summary for 1.3 as well; YH does 2.4 21:08:44 1.3 issues: http://trace.wisc.edu/bugzilla_wcag/issuereports/content-structure-separation_issues.php 21:08:55 js: can JC take on that extra work? 21:09:06 jc: yes 21:09:26 action: joe do the issue summary for 1.3 and as part of incorporate proposal for new 1.3 21:09:43 action: yvette issue summary for 2.4 by next tuesday 21:09:58 lg: suggesting GV join 4.2 group since complexity of his proposal is what is perplexing the group 21:10:01 gv: will try 21:10:15 q+ 21:11:00 gv: 4.2 has been perplexing us for awhile 21:12:06 gv: issue with sites that allow others to post 21:12:14 ack loretta 21:12:16 ack jason 21:12:37 jw: authoring tools dependency was discussed in the meeting; UA issue is more problematic- 21:13:11 q+ 21:13:12 jw: content acting as UA generally isn't something that you can't apply UAAG to 21:13:20 zakim, mute me 21:13:20 Yvette_Hoitink should now be muted 21:13:27 jw: so should add more specifics to our GL for that 21:13:51 ack wendy 21:13:51 wendy, you wanted to say that content doesnt' function as a UA 21:14:17 wc: propose that working group be given more time before we keep discussing in larger group 21:14:31 wc: then can perhaps provide a proposal 21:14:42 ack becky 21:14:50 bg: concerns about expecting embedded content to meet ATAG or UAAG - hard to do 21:14:59 bg: concerns about req. A 21:15:36 bg: meeting ATAG and UAAG for tools embedded in content - will wait for more from the group 21:15:48 zakim, close this item 21:15:48 agendum 4 closed 21:15:49 I see 2 items remaining on the agenda; the next one is 21:15:50 5. Looking ahead: Work Plan and scheduling next F2F [from wendy] 21:16:25 js: two issues - WC and others have been working to create detailed plan to get us to last call and candidate rec. etc 21:16:49 js: not ready for distrib. to list yet but lots of progress being made 21:16:59 js: will help us set the agenda for future calls 21:17:25 js:quickly need to figure out next F2F in June 21:17:44 wc: week of June 13 for F2F seems preferable 21:18:35 wc: have been dividing up GL for each week; 3 GL proposals per week with two weeks to discuss then resolve 21:19:20 wc: also scoping out techs; want to have ttf shadow the GL WG; techs would work on GL in the week following its dicussion at the WG Thursdya meeting 21:19:50 wc: F2F in Europe; 1st day open to public -then 2 days of techs and 2 days of gl 21:20:00 wc: propose techs before GL 21:20:34 wc: 13th June - public day; 14-15 - techs; 16-17 GL 21:20:40 q+ to ask "where?" 21:20:50 wc: do those dates work for people? 21:20:51 zakim, mute me 21:20:51 sorry, David, I do not see a party named 'David' 21:21:05 zakim, mute me 21:21:05 sorry, David, I do not see a party named 'David' 21:21:06 gv: would like regular WG to also participate in techs meetings 21:21:52 gv: so don't have to do a recap of everything for full WG and can help the techs groups 21:22:05 zakim, unmute me 21:22:05 Yvette_Hoitink should no longer be muted 21:22:09 gv: so if can come would be good to come for at least 4 days 21:22:44 yh: where? 21:23:05 wc: possibilities are Venice, Spain, Germany 21:23:13 yh: probably can't make unless in Germany 21:23:41 gv: any issues with the dates? silence - so assume date is ok 21:23:58 q+ to ask "levels" 21:24:27 wc: playing with different schedules; 21:25:11 wc: one shows Last call with no new Working draft; another shows sched. hit of another public Working draft 21:25:25 wc: sched. actually shows internal drafts each two weeks as issues are closed 21:25:37 wc: need to check with editors on hit of drafts every 2 weeks 21:26:25 wc: need to coordinate with people's schedules based on vacations and issues at work since we need everyone to be taking up and working on action items 21:26:43 js: heads up that you will be getting email or call from Wendy to do an issue summary by a certain date 21:27:34 js: please be honest when you commit to doing the work - it needs to get done on time 21:27:57 js: better to decline the work if you know you can't complete it; but we need everyone to take actions 21:28:02 q? 21:28:10 ack yvet 21:28:10 Yvette_Hoitink, you wanted to ask "where?" and to ask "levels" 21:28:39 q+ 21:28:45 yh: still need to address how many levels we are going to have - a year ago we picked 3 but did we ever make a firm decision 21:29:10 yh: we have assumed that no one will do everything in level 3 - need to decide what we will do with level 3 21:29:47 wc: bugzilla has 13 GL as components but also have others; conformance, etc. all of these components need issue summaries 21:30:01 wc: conformance needs to be done sooner rather than later due to baseline issues 21:30:14 zakim, mute me 21:30:14 Yvette_Hoitink should now be muted 21:30:27 ack g 21:30:28 wc: in sched. on some weeks might address 3 GL and another component 21:31:02 wc: interesting to see how missing something by one week can really affect the sched. esp in summer months when don't have as many people (due to vacation) 21:31:47 wc: need to balance getting a quality doc out and getting things done quickly 21:32:16 gv: need to mentally stay focused 21:33:01 wc: if do addn working draft before last call will add 2 months to sched 21:33:17 q? 21:33:19 gv: need to push forward as fast as we can and resolve key issues 21:34:04 jc: been making printouts of WCAG 2.0; went through each GL to find ones that do not have 21:34:44 action: joe send summary of analysis re: 2 levels of conformance 21:34:45 levels 1,2 and 3; my preference is for only 2 levels (as has been stated before) 21:35:49 js: wc, bc, and asw have already been working on conformance issues; who took conformance issue summary at dublin meeting? 21:35:53 wc: gv 21:36:02 wc: but still 18 issues open 21:36:16 js: want to see that issue summary rolled into conformance discussions 21:36:33 action: wac, bc, et al consider conformance issues issue summary in work on conformance claims 21:36:50 zakim, close this item 21:36:50 I do not know what agendum had been taken up, wendy 21:37:18 js: want to look at what issues might be candidates for closure but didn't get summary out to list on time 21:37:23 zakim, close item 5 21:37:23 agendum 5 closed 21:37:24 I see 1 item remaining on the agenda: 21:37:25 6. review of baseline issues and attempt to close those that seem ready to close [from wendy] 21:37:39 js: prospose adjourning 21:37:41 zakim, close item 6 21:37:41 agendum 6 closed 21:37:42 I see nothing remaining on the agenda 21:38:11 action: js, gv, wac go through summary of issues to determine what can be sent to list to close. 21:38:39 lg: need to coordinate 4.2 w 21:38:48 lg: working group tomorrow 21:39:52 -Yvette_Hoitink 21:39:53 -Matt 21:39:54 -[Microsoft] 21:39:55 -Wendy 21:39:56 -Becky_Gibson 21:39:58 -Joe 21:39:59 -Dave_MacDonald 21:40:00 -John_Slatin 21:40:01 -Loretta_Guarino_Reid 21:40:02 -Christophe_Strobe 21:40:04 -Gregg_and_Ben 21:40:05 -Bengt_Farre 21:40:07 -Makoto 21:40:07 later! 21:40:09 -JasonWhite 21:40:11 WAI_WCAG()4:00PM has ended 21:40:11 bye! 21:40:13 Attendees were Bengt_Farre, John_Slatin, Yvette_Hoitink, Gregg_and_Ben, Wendy, Loretta_Guarino_Reid, Becky_Gibson, Mike, Christophe_Strobe, Makoto, Matt, [Microsoft], JasonWhite, 21:40:16 ... [IPcaller], Dave_MacDonald, Joe 21:40:20 joeclark has left #wai-wcag 21:40:21 bengt has left #wai-wcag 21:40:39 cs has left #wai-wcag 21:53:23 RRSAgent, generate minutes 21:53:23 I have made the request to generate http://www.w3.org/2005/04/14-wai-wcag-minutes.html ben 21:54:11 Meeting: WCAG Weekly Telecon 21:54:21 RRSAgent, generate minutes 21:54:21 I have made the request to generate http://www.w3.org/2005/04/14-wai-wcag-minutes.html ben 21:55:27 RRSAgent, bye 21:55:27 I see 7 open action items: 21:55:27 ACTION: js, bc, wac, et al, continue work on guide doc [1] 21:55:27 recorded in http://www.w3.org/2005/04/14-wai-wcag-irc#T20-55-18 21:55:27 ACTION: joe write proposal for rewording on guideline 1.3 ala structure, presentation, behavior and explanation how it address gv's concern about separating out information. [2] 21:55:27 recorded in http://www.w3.org/2005/04/14-wai-wcag-irc#T21-03-50-1 21:55:27 ACTION: joe do the issue summary for 1.3 and as part of incorporate proposal for new 1.3 [3] 21:55:27 recorded in http://www.w3.org/2005/04/14-wai-wcag-irc#T21-09-26 21:55:27 ACTION: yvette issue summary for 2.4 by next tuesday [4] 21:55:27 recorded in http://www.w3.org/2005/04/14-wai-wcag-irc#T21-09-43 21:55:27 ACTION: joe send summary of analysis re: 2 levels of conformance [5] 21:55:27 recorded in http://www.w3.org/2005/04/14-wai-wcag-irc#T21-34-44 21:55:27 ACTION: wac, bc, et al consider conformance issues issue summary in work on conformance claims [6] 21:55:27 recorded in http://www.w3.org/2005/04/14-wai-wcag-irc#T21-36-33 21:55:27 ACTION: js, gv, wac go through summary of issues to determine what can be sent to list to close. [7] 21:55:27 recorded in http://www.w3.org/2005/04/14-wai-wcag-irc#T21-38-11 21:55:34 zakim, bye 21:55:34 Zakim has left #wai-wcag