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