Re: Agenda: WSC WG distributed meeting, Wednesday, 2008-04-30

Regrets, I have to take an exam.


-- Maritza

	http://www.cs.columbia.edu/~maritzaj/



On Apr 29, 2008, at 8:32 AM, Mary Ellen Zurko wrote:

>
>         Web Security Context (WSC) Call Agenda
>
> Calling information:
> Wednesday, 02 April 2008
> 11:00 am - 12:30 pm Eastern time
> http://www.w3.org/2006/WSC/Group/#meetings
> http://www.w3.org/Guide/1998/08/teleconference-calendar#D20080430
>
>
> Agenda
>
> 1) Pick a scribe
> http://www.w3.org/2006/WSC/Group/cheatsheet#Scribing
> http://www.w3.org/2006/WSC/scribes
>
> 2) Approve minutes from meetings
> http://www.w3.org/2008/04/16-wsc-minutes.html
>
> 3) Weekly completed action items
> (Usually checkpointed Friday am, US East Coast time)
> [pending review] ACTION-406: Ian Fette to Point out user burden  
> concerns w/ petnames in detail - due 2008-03-26
> [pending review] ACTION-410: Anil Saldhana to Update section 5.1.5.  
> Replace last sentence with: "A pinned self-signed certificate SHOULD  
> be considered sufficient identification to allow user agents to  
> associate a Petname with the site, if supported." - due 2008-04-17
> [pending review] ACTION-420: Anil Saldhana to Change 6.4.2  
> (notification / status) to include "MAY solicit user interaction" -  
> due 2008-04-23
>
> 4) Open Action Items
> http://lists.w3.org/Archives/Public/public-wsc-wg/2008Apr/0052.html
>
> 5) Action items closed due to inactivity
> [pending review] ACTION-404: Stephen Farrell to Propose wording for  
> 7.1 (chrome and UI practices) to weaken requirement to stuff that  
> makes sense in a given context - due 2008-03-26
> [pending review] ACTION-407: Tyler Close to Refine petname proposal  
> in light of 2008-03-19 call's discussion - due 2008-03-26
>
> 6) Agenda bashing
>
> 7) ISSUE-110 POST triggered via JavaScript
> http://www.w3.org/2006/WSC/track/issues/110
>
> 8) ISSUE-116 ReconfigureChrome Should users be able to reconfigure  
> primary chrome?
> http://www.w3.org/2006/WSC/track/issues/116
>
> 9) ISSUE-128 Strong / weak algorithms?
> http://www.w3.org/2006/WSC/track/issues/128
>
> 10) ISSUE-133 Plugin Problems How do our definition of Web Page and  
> the Robustiness section interact?
> http://www.w3.org/2006/WSC/track/issues/133
>
> 11) Next meeting - 07 May 2008
> More issues:
>
> ISSUE-110 POST triggered via JavaScript
> http://lists.w3.org/Archives/Public/public-wsc-wg/2007Nov/0105.html
>
> ISSUE-116 ReconfigureChrome Should users be able to reconfigure  
> primary chrome?
> http://lists.w3.org/Archives/Public/public-wsc-wg/2008Mar/0213.html
>
> ISSUE-138 Downgrade strength of Issuer field's Organization attribute
> http://www.w3.org/2006/WSC/track/issues/138
>
> ISSUE-181 Should there be an authoring practice suggesting http/ 
> https URI space consistency
> http://www.w3.org/2006/WSC/track/issues/181
>
> ISSUE-183 Automatic Selfsigned Certificate acceptance/probation MUST  
> NOT be implemented unless there is a history capability
> http://www.w3.org/2006/WSC/track/issues/183
>
> ISSUE-185 UI recommendations for URI handlers?
> http://www.w3.org/2006/WSC/track/issues/185
>
> ISSUE-188 props xit needs an acknowlegements section
> http://www.w3.org/2006/WSC/track/issues/188
>
> ISSUE-190 relaxedpathvalidation Relaxed Path Validation - optional,  
> recommended?
> http://www.w3.org/2006/WSC/track/issues/190
>
> ISSUE-192 ConformanceChrome Keep Chrome visible if its used for SCI
> http://www.w3.org/2006/WSC/track/issues/192
>
> ISSUE-193 MultiPageChrome Make multiple web pages chrome section rfc  
> 2119ed
> http://www.w3.org/2006/WSC/track/issues/193
>
> ISSUE-194 SizeMatters Window sizing a must
> http://www.w3.org/2006/WSC/track/issues/194
>
> ISSUE-195 RestrictPopups use SHOULD on popup restrictions
> http://www.w3.org/2006/WSC/track/issues/195
>
> ISSUE-74 Dependencies on other wgs
> http://www.w3.org/2006/WSC/track/issues/74
>
> ISSUE-75 Relation to existing standards and related work
> http://www.w3.org/2006/WSC/track/issues/75
>
>