W3C home > Mailing lists > Public > public-wsc-wg@w3.org > April 2007

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

From: Mary Ellen Zurko <Mary_Ellen_Zurko@notesdev.ibm.com>
Date: Thu, 19 Apr 2007 17:24:38 -0400
To: Web Security Context WG <public-wsc-wg@w3.org>
Message-ID: <OF28F0337C.2F92F66A-ON852572C2.00758DB3-852572C2.00759CB4@LocalDomain>
Anyone famliiar with NVDL or Schematron? Rob Y? 


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>


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

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


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

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


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
     * More iterative combinations of the above, throughout the
       specification lifecycle 
 This program is ambitious, but meritorious.  Wishing you all success.
Please consider
Investigate what can be done with high-function verification technologies 
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 
run on the author side in preparing materials for publication, and the 
things get run on the client or a third-party service when it seems 
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 
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
Received on Thursday, 19 April 2007 21:24:42 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:14:15 UTC