- From: Thomas Roessler <tlr@w3.org>
- Date: Wed, 19 Mar 2008 17:47:51 +0100
- To: WSC WG <public-wsc-wg@w3.org>
I realized during today's call that I forgot to call out two more changes that I had made last night, and that aren't entirely obvious: - In the error interactions section: <p>The error interactions characterized in this section are intended to communciate security context information, and therefore MUST fulfill relevant requirements in <a href="#sec-robustness-ui"><b>8.2 Chrome and User Interface Practices</b></a>.</p> </div> This one obviously needs more review along with the overall conformance model question. - The "managing user attention" section has explicit material about what to do during error interactions. Also, the conformance model in section 7 needs more review, as we've seen on today's call. Happy holidays to those who take them around this time, -- Thomas Roessler, W3C <tlr@w3.org> On 2008-03-19 00:13:38 +0100, Thomas Roessler wrote: > From: Thomas Roessler <tlr@w3.org> > To: WSC WG <public-wsc-wg@w3.org> > Date: Wed, 19 Mar 2008 00:13:38 +0100 > Subject: New editor's draft shuffles sections. > > I've taken a first stab at my action items ACTION-383, ACTION-384, > to redo the robustness section. It's still available here: > > http://www.w3.org/2006/WSC/drafts/rec/rewrite.html#Robustness > > However, I've (for now) moved the safe form bar and the usage modes > into appendices, so the section numbers have changed. Also, many of > the section numbers (but not anchors!) inside the robustness section > have changed significantly. > > I'll put this on the agenda for the call tomorrow for some initial > discussion, but anticipate that we'll need to talk more about this. > > Cheers, > -- > Thomas Roessler, W3C <tlr@w3.org>
Received on Wednesday, 19 March 2008 16:48:29 UTC