- From: Mike Beltzner <beltzner@mozilla.com>
- Date: Tue, 13 Feb 2007 22:34:22 -0500
- To: "Close, Tyler J." <tyler.close@hp.com>
- Cc: <public-wsc-wg@w3.org>
Without wanting to cause a mess in re-opening this issue, I wonder if we might want to talk about public iteration and channel for public feedback as a commitment. I'm not really thrilled with the idea of dropping the commitment to make the sample code public, since I think getting the widest possible amount of feedback will end up being the best thing for everyone, here. cheers, mike On 13-Feb-07, at 3:46 PM, Close, Tyler J. wrote: > Done, see: > > http://www.w3.org/2006/WSC/drafts/note/Overview.html#usability-testing > > Tyler > > From: public-wsc-wg-request@w3.org [mailto:public-wsc-wg- > request@w3.org] On Behalf Of Mary Ellen Zurko > Sent: Tuesday, February 13, 2007 8:47 AM > To: public-wsc-wg@w3.org > Subject: ACTION-144 Drop public sample code promise from 10.3 and > send text to list & tyler > > > Replace: > ____________________________________________________________________ > Part of a Working Group's activities is developing sample code and > test > suites: > http://www.w3.org/2005/10/Process-20051014/process.html > > Sample code to demonstrate and test the WG's recommendations on > display of > security context information will be implemented in one or more web > user > agents, as extensions to them The most likely web user agents we > will use > as implementation platforms are web browsers. The sample code will > be made > available publiclly as part of the WG's deliverables. To ensure > interoperability and generality of the recommendations, they will be > implemented in the context of at least two web user agents. > Entrance to > Proposed Recommendations required two interoperable implementations of > each feature of a specification. > > > > With: > ____________________________________________________________________ > Part of a Working Group's activities is developing code and test > suites: > http://www.w3.org/2005/10/Process-20051014/process.html > > Code to demonstrate and test the WG's recommendations on display of > security context information will be implemented in one or more web > user > agents, as extensions to them. The most likely web user agents we > will use > as implementation platforms are web browsers. To ensure > interoperability and generality of the recommendations, they will be > implemented in the context of at least two web user agents. > Entrance to > Proposed Recommendations required two interoperable implementations of > each feature of a specification. > > > > Replace: > ____________________________________________________________________ > Functional testing against the sample code and appropriate deployment > configurations will verify that the recommendations can be > translated to > web user agent code, with no functional ill effects on the rest of > the web > user agent. It will show that implementations can conform to the > recommendations, and that the specifications clearly define behaviors. > This is also called conformance testing. > > > > With: > ____________________________________________________________________ > Functional testing against code and appropriate deployment > configurations will verify that the recommendations can be > translated to > web user agent code, with no functional ill effects on the rest of > the web > user agent. It will show that implementations can conform to the > recommendations, and that the specifications clearly define behaviors. > This is also called conformance testing. > > > > Replace: > ____________________________________________________________________ > o Lab testing of sample code (for example, > http://cups.cs.cmu.edu/soups/2005/2005proceedings/p13-garfinkel.pdf) > o Contextual or "in the wild" testing of sample code (for example, > http://www.indiana.edu/~phishing/social-network-experiment/phishing- > preprint.pdf) > > > > With: > ____________________________________________________________________ > o Lab testing of code (for example, > http://cups.cs.cmu.edu/soups/2005/2005proceedings/p13-garfinkel.pdf) > o Contextual or "in the wild" testing of code (for example, > http://www.indiana.edu/~phishing/social-network-experiment/phishing- > preprint.pdf) > > >
Received on Wednesday, 14 February 2007 03:34:34 UTC