Note structure (Was: Design principles to Note)

Hi all,
 
I've reconfigured the NoteIndex a bit to fit the content people have
agreed to provide and to cover the areas we've been talking about. See:
 
http://www.w3.org/2006/WSC/wiki/NoteIndex
 
The third level headings in that index won't appear in the actual note,
they're just there to keep track of why I reordered things the way I
did.
 
The third major section "What the solution should look like" is to
contain the Design Principles / Assumptions / Verification material that
Mez refers to in the email below. Mez, are you and Maritza going to
draft those sections of the Note? If so, I think we've got volunteers
for most everything else.
 
There are some outstanding Action items for text in the NoteGoals,
NoteOutOfScope and NoteUseCases sections. After those are in, I'll mop
up.
 
We've got volunteers for the NoteUserAgents and
NoteSecurityContextAvailable sections. I'ld like to work on the
NoteProblemsWithCurrentUserInterface section, but Phil should really add
some content there as well. He did after all write a book on the
subject.
 
Everyone adding content should fill out the NoteReferences and
NoteAcknowledgments as they steal (err, author) their sections.
 
Hopefully the above is a feasible amount of work to get done by January
15th. If so, I'll convert it into the W3C's XML format for the 22nd,
which will give us all a week to ponder it before our f2f on the 30th,
31st.
 
I love it when a plan comes together...
 
Tyler

________________________________

From: public-wsc-wg-request@w3.org [mailto:public-wsc-wg-request@w3.org]
On Behalf Of Mary Ellen Zurko
Sent: Wednesday, December 20, 2006 8:03 AM
To: public-wsc-wg@w3.org
Subject: Design principles to Note



I propose we include Design Principles we will use to inform and support
our recommendations in the Note. It was at one time what I meant by the
References section, but it needs to be separate from a pure list of
references. Either as part of a larger "verification section"
(generalizing our User Testing Veriffication section) or as part of the
Assumptions section, or a new section. Tyler (or anyone), suggestions
for structuring this. 

I've put in bold items in our SharedBookmarks section that form the
basis for those Design Principles (which Martiza and I started on as
ACTION-20 and ACTION-21, and are now in the wiki): 
http://www.w3.org/2006/WSC/wiki/SharedBookmarks

I encourage everyone to do two things:

1) If you have other references for our SharedBookmarks, add them,
always including some annotation on why they're (potentially) pertinent
to our work. 

2) Take a look at the proposed Design Principles I've put in bold. I
don't propose that we slavishly follow them, I don't propose that we
will not have others, but I do propose them (and any modifications) as a
documented basis in the Note for one of the sets of assumptions we'll
use (see last bullet item in:) 

http://www.w3.org/2006/WSC/wiki/NoteAssumptions

          Mez

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