ISSUE-223: Define criteria now for the test/implementation phase of the compliance spec

implementation criteria

Define criteria now for the test/implementation phase of the compliance spec

State:
RAISED
Product:
Compliance Current
Raised by:
David Wainberg
Opened on:
2013-10-02
Description:
While it is straightforward to demonstrate a working implementation of a technical specification, it is not so for a policy specification. If a technical specification breaks something technical, that is relatively easy to identify and solve for. But how will we evaluate the success or feasibility of implementations against the policy spec? Will we evaluate cost of implementation? Impact on the marketplace? Impact on users? Understandability of the spec by users?

We need to define criteria now for two reasons. One, it will give us much needed guidance with respect to the result we are trying to achieve. Two, it will give potential implementers predictability and comfort with respect to the kinds of feedback that will be taken and incorporated into the process.
Related Actions Items:
No related actions
Related emails:
  1. Re: Batch closing of old issues (from fielding@gbiv.com on 2015-03-25)
  2. Batch closing of old issues (from jbrookman@cdt.org on 2015-03-24)
  3. ISSUE-223 Criteria for implementation testing (from dwainberg@appnexus.com on 2013-11-18)
  4. ISSUE-223 please add to the agenda (from dwainberg@appnexus.com on 2013-11-04)
  5. tracking-ISSUE-223 (implementation criteria): Define criteria now for the test/implementation phase of the compliance spec [Compliance Current] (from sysbot+tracker@w3.org on 2013-10-02)

Related notes:

No additional notes.

Display change log ATOM feed


Matthias Schunter <matthias.schunter@intel.com>, Chair, Bert Bos <bert@w3.org>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.325 2014-09-10 21:42:02 ted Exp $