- From: Gregg Vanderheiden <gv@trace.wisc.edu>
- Date: Thu, 21 Mar 2013 21:49:40 -0500
- To: Peter Korn <peter.korn@oracle.com>, Michael Pluke <Mike.Pluke@castle-consult.com>, "public-wcag2ict-tf@w3.org Force" <public-wcag2ict-tf@w3.org>
- Message-id: <300529F9-431B-496B-83E1-45BECB3311C8@trace.wisc.edu>
I am getting a bit uncomfortable with us creating what is becoming a back-door document for communicating from this committee to the M376 committee. https://sites.google.com/site/wcag2ict/cross-cutting-issues-and-notes/comparison-to-m376 I think the idea of comparing language to see where we should change our text is a great idea -- and something we should do - and have been doing. I think recognizing that M376 and Access Board might look at this page -- so we are careful what language we put on the page is also a good idea. To that end we said we should remove personal opinions and comments that seem to be making comment on M376. But now we are talking about adding text specifically for viewing by other regulatory bodies -- and I think this is now outside of our bounds. The committee has no authority to communicate messages to M376 or to post documents intended for outside consumption other than the WCAG2ICT document (except for exposing our work for the purpose of public scrutiny of our process). We include M376 personnel and Access Board personnel in the committee so that they would have the benefit of both understanding and, as they are comfortable, contributing to our consensus WCAG2ICT document. But the task force as a whole is not authorized to create other documents, including this comparison page, with the intent of communicating or submitting our opinions to M376 or the Access Board. The language being added to this page is not language for our own use -- or needed for us to use this working page. It is clearly meant to convey information to outside bodies -- and thus begins to turn this page from a Task force working page -- into a task force communication page with outside bodies. This text and all of the text in column 5 that includes text like "Suggestion: the rest of Note 1 is helpful, and should be added to M376." should be removed from the page as I thought we decided earlier, since it is clearly of our scope for the task force to be suggesting edits to M376. Also note that these are not decisions from the working group but just suggestions submitted by one member. I think we should proceed with these edits tomorrow and bring the page back into line - by having it just be a working page of the committee without additional information or intended uses. Gregg -------------------------------------------------------- On Mar 21, 2013, at 6:23 PM, Peter Korn <peter.korn@oracle.com> wrote: > Mike, gang, > > While it wasn't on the survey, if we have time we might consider a discussion (and later survey) on the three paragraphs of text introducing the Closed table. > > Since we have recognized that this wiki page may be used by the M376 STF and the Access Board to help them consider their own text in places (and modifications to existing text), we have taken great care to craft the text of the final columns of these tables, requiring TF consensus for that final column final text. We took some of the introductory text of the Software table and put it into its own initial row of that table, with TF consensus. I think we should consider doing something similar here. > > Also, looking forward to the eventual cleanup of this page (stripping out some of the text that is very clearly a single individual's opinion), I added a section near the top titled "What parts of this wiki have TF consensus". > > > Finally, on a related topic, I have finished the updated comparisons of those "set of" SCs where (a) there was M376 language, and (b) where our language had been updated since 13Dec12. You can find that in both the Documents and Software tables. I'm working now on a survey for that. Related to that, in an(other) attempt to work toward language that captures some of our feelings about the "set of" SCs and where/how they differ from M376 language, I introduced another section/paragraph near the top titled 'General thoughts on "set of" SCs', which lays out in more broad detail what and why there are differences in these between WCAG2ICT & M376. I've highlighted this text in yellow which is the color code for "not yet dealt with", to further indicate that this is something we should discuss and perhaps become TF consensus text on this wiki page. I will include that in the survey I'm working on. > > > Regards, > > Peter > > On 3/21/2013 9:42 AM, Michael Pluke wrote: >> >> ** MEETING TIME >> >> The WCAG2ICT Task Force will meet Friday, March 22nd, at our regularly scheduled time for 90 minutes: >> >> 10a.m. US EDT for 90 Minutes >> 7:00 AM PDT; 10:00 AM EDT; 14:00 UTC/Z; 3:00 PM BST; 16:00 CET >> Please confirm meeting time in your time zone using the Fixed Time Clock [1]. >> >> ** TELECONFERENCE INFO >> >> +1.617.761.6200 (in U.S.) >> Conference Code: 2428# (2ICT#) >> >> SIP: zakim@voip.w3.org CODE: 2428# (2ICT#) >> Direct SIP: 002119@voip.w3.org >> (Instructions below for SIP and VoIP in REFERENCES below) >> ** AGENDA >> >> agenda+ Discuss the 'Closed Functionality - compare/contrast with M376' survey [2] >> agenda+ priorities for remaining sections to address >> agenda+ confirming next meetings, including holiday break >> adjourn >> >> ** IRC INFO >> IRC server: irc.w3.org, port: 6665, channel: #wcag2ict. >> Zakim phone commands: 61# to mute; 60# to unMute; 41# to raise your hand (enter speaking queue); 40# to lower your hand (exit speaking queue). The system acknowledges commands with a three-tone confirmation. >> IRC Commands: "zakim, mute me" to mute; "zakim, unmute me" to unMute; "q+" to enter speaking queue; "q-" to exit speaking queue >> >> >> ** REFERENCES >> >> [1] http://www.timeanddate.com/worldclock/fixedtime.html?iso=20130322T09&p1=24&ah=1 >> >> [2] https://www.w3.org/2002/09/wbs/55145/20130321/results >> >> Previous meeting minutes: http://www.w3.org/2013/03/15-wcag2ict-minutes.html >> >> >> SIP Instructions: http://www.w3.org/2006/tools/wiki/Zakim-SIP >> Additional VoIP tips: http://www.w3.org/2006/tools/wiki/Zakim-SIP-tips >> IRC setup, agenda robots, speaker queuing, and posting the log to the web: http://www.w3.org/2001/12/zakim-irc-bot.html >> W3C use of IRC: http://www.w3.org/Project/IRC/ >> Web gateway to IRC in case your network administrators forbid IRC: http://www.w3.org/2001/01/cgi-irc >> RRSAgent that captures and posts log with action items: http://www.w3.org/2002/03/RRSAgent >> IRC interface to phone bridge manager that maintains speaker and agenda queues: http://www.w3.org/2001/12/zakim-irc-bot >> >> Mike and Andi >> WCAG2ICT TF Co-Facilitators >> >> > > -- > <oracle_sig_logo.gif> > Peter Korn | Accessibility Principal > Phone: +1 650 5069522 > 500 Oracle Parkway | Redwood City, CA 94065 > <green-for-email-sig_0.gif> Oracle is committed to developing practices and products that help protect the environment
Received on Friday, 22 March 2013 02:50:15 UTC