Re: ISSUE-65: testing throughout evolution of product (pubic comment)

Anyone famliiar with NVDL or Schematron? Rob Y? 

          Mez

Mary Ellen Zurko, STSM, IBM Lotus CTO Office       (t/l 333-6389)
Lotus/WPLC Security Strategy and Patent Innovation Architect




Web Security Context Issue Tracker <dean+cgi@w3.org> 
Sent by: public-wsc-wg-request@w3.org
04/17/2007 08:30 AM
Please respond to
Web Security Context WG <public-wsc-wg@w3.org>


To
public-wsc-wg@w3.org
cc

Subject
ISSUE-65: testing throughout evolution of product (pubic comment)








ISSUE-65: testing throughout evolution of product (pubic comment)

http://www.w3.org/2006/WSC/Group/track/issues/65

Raised by: Bill Doyle
On product: Note: use cases etc.

>From public comments
raised by: Al Gilman Alfred.S.Gilman@ieee.org

http://lists.w3.org/Archives/Public/public-usable-
authentication/2007Apr/0000.html

testing throughout evolution of product 
where it says, in 10.3 Implementation and testing
   We will pursue resources that allow us to do
   more extensive usability testing, including:
     * Substantially different low fi testing for each iteration
     * Broader and more representative user population participating
     * Lab testing of sample code, for example [147]Johnny 2]
     * Contextual or "in the wild" testing of sample code [148]Social
       Phishing]
     * More iterative combinations of the above, throughout the
       specification lifecycle 
Hooray!
 This program is ambitious, but meritorious.  Wishing you all success.
Please consider
Investigate what can be done with high-function verification technologies 
such 
as NVDL and Schematron to aid authors (and user agents) in deriving 
information that bears on the conforming or non-conforming use of your 
suggested practices.  The flow here is from the logical model for security 

information to machinable checks targeted to two applications: things that 
get 
run on the author side in preparing materials for publication, and the 
same 
things get run on the client or a third-party service when it seems 
there's 
something not quite right in the State of Denmark.
please consider
Stay in touch with the Mobile Web Best Practices WG. They are ahead of you 
on 
the road in exploring new and better paths to testing and deployment.
please consider
Keep a journal.  The WAI stands fair to gain from anything you learn