W3C home > Mailing lists > Public > public-tracking@w3.org > October 2013

tracking-ISSUE-223 (implementation criteria): Define criteria now for the test/implementation phase of the compliance spec [Compliance Current]

From: Tracking Protection Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Wed, 02 Oct 2013 16:05:57 +0000
Message-Id: <E1VROw1-0004L4-Li@shauna.w3.org>
To: public-tracking@w3.org
tracking-ISSUE-223 (implementation criteria): Define criteria now for the test/implementation phase of the compliance spec [Compliance Current]

http://www.w3.org/2011/tracking-protection/track/issues/223

Raised by: David Wainberg
On product: Compliance Current

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.
Received on Wednesday, 2 October 2013 16:06:02 UTC

This archive was generated by hypermail 2.3.1 : Friday, 3 November 2017 21:45:19 UTC