I'm worried about having two parallel processes (confusing and management issues, and how to measure/demonstrate "equivalence"?). Why not consider one process that would work for any technique no matter who develops it? There would be one set of quality and other criteria that the submitter would have to satisfy. Such an approach would promote uniformity and consistency.. (Background - in the related realm of testing/test suites, WG members develop tests "in-house" but contributions from outside are encouraged, there is one set of process/requirements, and one test suite, with tests from various contributors all meeting the same requirements..) Best, Tim Boland NIST -----Original Message----- From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On Behalf Of Loretta Guarino Reid Sent: Friday, February 13, 2009 2:22 PM To: WCAG Subject: Policy on Third Party Techniques When last we visited this topic, our draft proposal was <http://trace.wisc.edu/wcag_wiki/index.php?title=Externally_Submitted_Techni ques_Proposal> or <http://tinyurl.com/cea9zd> Let's use this as a starting point for our discussion. Is this still the policy we want to propose? Do we want to consider any modifications? LorettaReceived on Friday, 13 February 2009 21:05:38 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 22 March 2009 02:51:44 GMT