From: Felicia Bender <kuzqrz@symphonyone.net>
Date: Oct 1, 2006 1:47 PM
Subject: tinderbox

If a test case for a particular feature is difficult to conceive, it often means that the feature is too complex, or that the prose describing the feature is too ambiguous. They highlight some common implementation issues in user agents and HTTP-based softwares. The format of the package has not yet been decided, but it has to be international then we need to understand how universities function around the world. We think there should be a tool to gather observations made on a single document by various validators and quality checkers, and summarize all of that neatly for the user.

This is officially owned by the QA IG, although the policies for writing in it aren't well defined yet. It helps create better specifications by raising and discussing technical issues, by reviewing materials, by providing fresh input. The document defines a minimal set of metadata elements that can usefully be applied to tests that are intended for publication within a test suite. It is important, not only for developers who will try to implement the language, but also as a sanity check for the specification itself. What software is secure? What software is safe? We have to define ways of organizing the QA IG and support the QA IG objectives. At the time of the publication, it was mentionned that a schema could be useful to help implementers to use it in their tools.

That would be a rare sight, but it's not a fantasy. The test metadata schema could be reused in part by EARL which is likely to make this effort even more urgent. Often the chosen criteria will be to have two interoperable implementations of each feature. Patrick Curran has proposed to take her role. And no way to have an overview of the quality checking of the web page. There are no currently regular teleconferences. Tools are developer by volunteers, mostly in Europe. How can users determine these qualities? The framework will have to give hints on strategies for change. We require validation tools that work and are kept up to date. If a certification program was launched at in the future, it would certainly modify the whole Web ecosystem. it helps harmonization of vocabulary accross specifications and maintains regularity. Upcoming accessibility and markup specifications fail on both counts.