W3C home > Mailing lists > Public > www-qa@w3.org > February 2007

Re: Good (and Bad) practices of implementation reports

From: Tim Boland <frederick.boland@nist.gov>
Date: Tue, 20 Feb 2007 09:58:51 -0500
Message-Id: <5.1.1.5.2.20070220094807.01f48520@mailserver.nist.gov>
To: Karl Dubost <karl@w3.org>
Cc: www-qa@w3.org, Lofton Henderson <lofton@rockynet.com>, "Snorre M. Grimsby" <snorre@opera.com>, Patrick Curran <Patrick.Curran@Sun.COM>, "Lynne S. Rosenthal" <lsr@email.nist.gov>, "Mark W. Skall" <mark.skall@nist.gov>

In terms of some past experience, there is a CSS3 Selectors Implementation 
Report Template [1], as well as instructions [2] to help with creating an 
implementation report.  I believe these have worked well so far for the 
purpose intended.

[1]: 
http://www.w3.org/Style/CSS/Test/CSS3/Selectors/20030915/implementreportTEMPLATE.html

[2]: http://www.w3.org/Style/CSS/Test/CSS3/Selectors/report-instruct.txt

In terms of future work, implementation reports are under discussion in 
some of the Web Accessibility Initiative (WAI) groups I'm in (Authoring 
Tools and Web Content) , but these specifications are described in terms of 
guidelines and success criteria (normative requirements), so it's possible 
that the approach taken to create implementation reports in these groups 
may be somewhat different than for other W3C specifications (like CSS), 
where the requirements are expressed in other ways..

Have to think about it some more..

Thanks and best wishes
Tim Boland NIST


At 12:12 PM 2/20/2007 +0900, Karl Dubost wrote:

>Hi Lofton, Snorre, Lynne, Mark, Patrick,
>(and others)
>
>I would like  to have your opinions about Implementation Reports.
>
>
>Short reminder:
>
>    During the CR phase[2], usually it is requested from WGs to prove
>that their language has been implemented /at least/ twice. Rules can
>be made stricter by the WG itself. Often WGs produce an
>implementation report to have a global view of implementations
>landscape.  The QA Matrix[3] lists W3C implementation reports[1] and
>shows their diversity in terms of layouts and information.
>
>
>Questions:
>    - What should contain an implementation report?
>    - What shoud NOT contain an implementation report?
>    - Do you think a common format is desirable?
>    - Do you have success or bad stories when creating an
>implementation report?
>
>
>Reference:
>[1] http://esw.w3.org/topic/ImplementationReport
>[2] http://www.w3.org/2004/02/Process-20040205/tr.html#cfi
>[3] http://www.w3.org/QA/TheMatrix
>
>
>Thanks
>
>
>--
>Karl Dubost - http://www.w3.org/People/karl/
>W3C Conformance Manager, QA Activity Lead
>   QA Weblog - http://www.w3.org/QA/
>      *** Be Strict To Be Cool ***
>
>
>
>
Received on Tuesday, 20 February 2007 15:00:53 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:40:37 UTC