[QA IG] QA Findings

This is an excerpt of W3C QA IG F2F minutes of Mandelieu, France,  
27/28 February 2006
Each topic indivually given to help the discussion.
http://www.w3.org/QA/2006/03/minutes_of_qa_ig_f2f_at_the_w3.html


QA Findings
http://www.w3.org/QA/2006/03/minutes_of_qa_ig_f2f_at_the_w3#qa-findings

    [43]Tag Findings are short documents dealing with issues about
    architecture. The format is quite interesting and gathering the
    knowledge about one particular topic of Web architecture. Dominique
    Hazaël-Massieux has suggested that it might be possible to publish
    QA Findings.

      [43] http://www.w3.org/2001/tag/findings

    For example, in MWI WG, they are writing best practices, some of
    these practices are not testable. So, they are not normative. An
    requirement don't have to be testable to be normative, but life
    become much harder if non testable normative requirements are
    provided in a specification. Having a summary of all discussions
    which have been done for this specific topic would be very useful
    and could serve as a QA Findings.

    When a discussion got enough momentum on the www-qa mailing-list,
    someone will take the responsibility about prototyping the topic on
    the [44]QA wiki and collect information. Once the document has
    reached maturity, we might publish it as a QA Finding, probably on
    the QA Weblog.

      [44] http://esw.w3.org/topic/QA

    ACTION: Dom to start a wiki page on testability/normativity before
    mid-March and will report on www-qa.


-- 
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 Wednesday, 8 March 2006 05:29:39 UTC