public-wsc-wg@w3.org from April 2007 by thread

Agenda, Wednesay, 2 May, WSC Call Mary Ellen Zurko (Monday, 30 April)

Fw: ACTION-150 Propose text do drill down on possible classes of conforming implementations -- more concrete than note, more abstract than products Mary Ellen Zurko (Monday, 30 April)

Secure Internet Letterhead Hallam-Baker, Phillip (Saturday, 28 April)

Editing process for Recommendations Close, Tyler J. (Friday, 27 April)

baked Note edits Close, Tyler J. (Friday, 27 April)

Meeting record: WSC WG weekly 2007-04-18 Thomas Roessler (Friday, 27 April)

Fw: [Soups-announce] Call for SOUPS posters and discussion sessions Mary Ellen Zurko (Friday, 27 April)

ISSUE-15 closing Close, Tyler J. (Thursday, 26 April)

ISSUE-31 Correct scenarion 20 intended action Mary Ellen Zurko (Thursday, 26 April)

ISSUE-30 allow for remote opening of web browser Mary Ellen Zurko (Thursday, 26 April)

ISSUE-29 OPEN Define user agent in wsc-usecases Mary Ellen Zurko (Thursday, 26 April)

ISSUE-26 OPEN "currently deployed security information" Mary Ellen Zurko (Thursday, 26 April)

wsc-usecases review Mike Beltzner (Thursday, 26 April)

ISSUE-24 OPEN [editorial] Add "known systemic flaws" to goals Mary Ellen Zurko (Thursday, 26 April)

ISSUE-23 OPEN Rephrase background on usable security in Process secion Mary Ellen Zurko (Thursday, 26 April)

ISSUE-20 OPEN Potential additions to Available Security Information Mary Ellen Zurko (Thursday, 26 April)

Re: ISSUE-19: Arrangement and formatting of use cases Mary Ellen Zurko (Thursday, 26 April)

Re: ISSUE-18: Clarify audience of wsc-usecases Mary Ellen Zurko (Thursday, 26 April)

Re: ISSUE-14: Technologies that reduce risk Mary Ellen Zurko (Thursday, 26 April)

Re: ISSUE-12: User-agents - future proofing Mary Ellen Zurko (Thursday, 26 April)

Re: ISSUE-7: Mental models? Mary Ellen Zurko (Thursday, 26 April)

Re: ISSUE-6 User Interface Issues for Constrained / Mobile Devices Mary Ellen Zurko (Thursday, 26 April)

Fw: Dublin workshop on web authoring Mary Ellen Zurko (Thursday, 26 April)

Regrets Shawn Duffy (Wednesday, 25 April)

ACTION 181: Summary of EV certificate discussion, prototype recommendation Hallam-Baker, Phillip (Wednesday, 25 April)

ISSUE-72: Replace term \"Status Quo\" with something more specific Web Security Context Issue Tracker (Wednesday, 25 April)

ISSUE-71: Change title of Section 7 Web Security Context Issue Tracker (Wednesday, 25 April)

ISSUE-70: Scope should be defined in terms of concepts, not in terms of use cases Web Security Context Issue Tracker (Wednesday, 25 April)

ISSUE-69: New goal--Reduce the number of scenarios in which users\' security depends upon authenticating sites Web Security Context Issue Tracker (Wednesday, 25 April)

ISSUE-68: Note summary, goals, and scope should more clearly focus on problem to be solved---impersonation Web Security Context Issue Tracker (Wednesday, 25 April)

ISSUE-67: The introduction to the note should include a hyperlink to the charter. Web Security Context Issue Tracker (Wednesday, 25 April)

Proposed Recommendation: Identity indicator in chrome Johnathan Nightingale (Wednesday, 25 April)

Proposed Recommendation: Page Info Summary Johnathan Nightingale (Wednesday, 25 April)

Summary of "What is a secure page?" discussion, first draft Yngve N. Pettersen (Developer Opera Software ASA) (Tuesday, 24 April)

shared knowledge authentication of web sites Mary Ellen Zurko (Tuesday, 24 April)

Updating TrustMe wiki page based on telecon Close, Tyler J. (Monday, 23 April)

Re: Rough proposal: Contextual Password Warnings Thomas Roessler (Monday, 23 April)

Agenda, Wednesay, 25 April, WSC Call Mary Ellen Zurko (Monday, 23 April)

Suggestions for note resulting from a conversation with mez Stuart E. Schechter (Monday, 23 April)

ISSUE-66: Suggested rewrite of last paragraph of 10.3 Web Security Context Issue Tracker (Monday, 23 April)

No Padlock OID Hallam-Baker, Phillip (Sunday, 22 April)

ACTION-182 michael.mccormick@wellsfargo.com (Friday, 20 April)

RE: Favicon anti-pattern michael.mccormick@wellsfargo.com (Friday, 20 April)

Look over background for any further recommendations Mary Ellen Zurko (Friday, 20 April)

Meeting record: WSC WG weekly 2007-04-11 Thomas Roessler (Thursday, 19 April)

RE: Safe Web Browsing Mode Mary Ellen Zurko (Thursday, 19 April)

Use Cases Again Stuart E. Schechter (Wednesday, 18 April)

ACTION-175 - Summarize robustness practices for Firefox Johnathan Nightingale (Tuesday, 17 April)

regrets for 17 April call Timothy Hahn (Tuesday, 17 April)

ACTION-194 refine UrlRecommendation Mary Ellen Zurko (Tuesday, 17 April)

ISSUE-65: testing throughout evolution of product (pubic comment) Web Security Context Issue Tracker (Tuesday, 17 April)

ISSUE-64: \'where\' is less universal than \'how\' for drill-down (public comment) Web Security Context Issue Tracker (Tuesday, 17 April)

ISSUE-63: consistency is good where it fits; it doesn\'t always fit; so undergird your consistency with a model (public comment) Web Security Context Issue Tracker (Tuesday, 17 April)

ISSUE-62: User-adjustable step size is part of Universal Design (public comment) Web Security Context Issue Tracker (Tuesday, 17 April)

ISSUE-61: Know you don\'t know your users (public comment) Web Security Context Issue Tracker (Tuesday, 17 April)

ISSUE-60: reinvent Help and DoIt (public comment) Web Security Context Issue Tracker (Tuesday, 17 April)

ISSUE-59: challenge and recover are essential; one presentation fits all -NOT (pubic comment) Web Security Context Issue Tracker (Tuesday, 17 April)

ISSUE-58: simplicity is in the [diverse] world of the user (public comment) Web Security Context Issue Tracker (Tuesday, 17 April)

ISSUE-57: qualify your interrupts; communicate subliminally always and through the focus rarely (public comment) Web Security Context Issue Tracker (Tuesday, 17 April)

ISSUE-56: habit is little help, here (public comment) Web Security Context Issue Tracker (Tuesday, 17 April)

ISSUE-55: realism is not universal, nor does ordinariness befit exceptional communications (public comment) Web Security Context Issue Tracker (Tuesday, 17 April)

ISSUE-54: user understanding is where it\'s at (pubic comment) Web Security Context Issue Tracker (Tuesday, 17 April)

ISSUE-53: augment general usability wisdom because you are operating on a fringe (as is WAI) (Public Comnment) Web Security Context Issue Tracker (Tuesday, 17 April)

ISSUE-52: benchmarking success -- it\'s out there (public comment) Web Security Context Issue Tracker (Tuesday, 17 April)

ISSUE-51: distinguished Chrome is not the answer (public comment) Web Security Context Issue Tracker (Tuesday, 17 April)

Agenda, Wednesay, 18 April, WSC Call Mary Ellen Zurko (Monday, 16 April)

ACTION-188 summarize robustness practices in terms of limitations on sites\\\\\\\\' freedom Mary Ellen Zurko (Monday, 16 April)

Futures area of our wiki Mary Ellen Zurko (Monday, 16 April)

ACTION-189: Cabfourm X.509v3/ PKIX guidelines Hallam-Baker, Phillip (Monday, 16 April)

Cabfourm X.509v3/ PKIX guidelines Hallam-Baker, Phillip (Monday, 16 April)

Error handling proposal Mary Ellen Zurko (Monday, 16 April)

ISSUE-50: present web security is not good enough; even \'though fixing that is out of scope for this deliverable (public comment) Web Security Context Issue Tracker (Monday, 16 April)

ISSUE-49: trust in browser password cache needs to be better justified (pubic comment) Web Security Context Issue Tracker (Monday, 16 April)

ISSUE-48: platform and browser security out of scope - NOT (public comment) Web Security Context Issue Tracker (Monday, 16 April)

ISSUE-47: define extension interface for content-scanning tools (public comment) Web Security Context Issue Tracker (Monday, 16 April)

[fwd] Re: Shared Public Knowledge (from: dan.schutzer@fstc.org) Thomas Roessler (Sunday, 15 April)

ISSUE-46: define extension interface for content-scanning tools (public comment) Web Security Context Issue Tracker (Sunday, 15 April)

ISSUE-45: full legal entity identification (is a must) (pubic comment) Web Security Context Issue Tracker (Sunday, 15 April)

ISSUE-44: beyond \'who\' (some day) (pubic comment) Web Security Context Issue Tracker (Sunday, 15 April)

ISSUE-43: don\'t disable assistive technology (public comment) Web Security Context Issue Tracker (Sunday, 15 April)

ISSUE-42: Re: 3.2 Non-HTTP Web interactions (public comment) Web Security Context Issue Tracker (Sunday, 15 April)

ISSUE-41: limited guidance on presentation OK (public comment) Web Security Context Issue Tracker (Sunday, 15 April)

ISSUE-40: Drill-down access to all security information is not \'nice,\' it\'s required (by UAAG 1.0). (public comment) Web Security Context Issue Tracker (Sunday, 15 April)

ISSUE-39: cooperate with WAI-ARIA \'politeness\' (from public comments) Web Security Context Issue Tracker (Sunday, 15 April)

ISSUE-38: no safe haven in presentation space (from public comments) Web Security Context Issue Tracker (Sunday, 15 April)

ISSUE-37: qualify your interrupts (from public comments) Web Security Context Issue Tracker (Sunday, 15 April)

ISSUE-36: presentation norms -- no oneSizeFitsAll (from public comments) Web Security Context Issue Tracker (Sunday, 15 April)

Risky display-only use cases (ACTION-193) michael.mccormick@wellsfargo.com (Friday, 13 April)

ISSUE-35: information overload/underload -- no oneSizeFitsAll (public comment) Web Security Context Issue Tracker (Friday, 13 April)

ISSUE-34: Formal studies don\'t cover disability access adequately, use experts too - (public comment) Web Security Context Issue Tracker (Friday, 13 April)

ISSUE-33: Charter retains authority Review of Note Web Security Context Issue Tracker (Friday, 13 April)

DNSSEC indicator Dan Schutzer (Friday, 13 April)

"The Emperor's New Security Indicators" michael.mccormick@wellsfargo.com (Thursday, 12 April)

FW: sitekey auth busted on BoA site michael.mccormick@wellsfargo.com (Thursday, 12 April)

FW: .safe TLD idea from ICANN michael.mccormick@wellsfargo.com (Thursday, 12 April)

Re: ACTION-172 OPEN Map threat trees to use case dimensions Stuart Schechter 2007-04-04 Mary Ellen Zurko (Thursday, 12 April)

ISSUE-32: explain dynamic content better Web Security Context Issue Tracker (Thursday, 12 April)

ISSUE-31: Correct scenarion 20 intended action Web Security Context Issue Tracker (Thursday, 12 April)

ISSUE-30: Web Security Context Issue Tracker (Thursday, 12 April)

ISSUE-29: Define user agent in wsc-usecases Web Security Context Issue Tracker (Thursday, 12 April)

RE: DNSSEC indicator michael.mccormick@wellsfargo.com (Thursday, 12 April)

Meeting record: WSC WG weekly 2007-04-04 Thomas Roessler (Thursday, 12 April)

Action item summary 2007-04-11 Thomas Roessler (Thursday, 12 April)

Shared Public Knowledge michael.mccormick@wellsfargo.com (Wednesday, 11 April)

regrets for 11 April WSC call Timothy Hahn (Wednesday, 11 April)

Agenda, Wednesay, 11 April, WSC Call Mary Ellen Zurko (Monday, 9 April)

ISSUE-28: \"available security information\" Web Security Context Issue Tracker (Sunday, 8 April)

ISSUE-27: [editorial?] techniques for content based detection Web Security Context Issue Tracker (Sunday, 8 April)

ISSUE-26: \"currently deployed security information\" Web Security Context Issue Tracker (Sunday, 8 April)

status of my action items -- some due date adjustments Thomas Roessler (Sunday, 8 April)

ACTION-154 Track HTTP Auth related extensions Bill Doyle 2007-03-20 Mary Ellen Zurko (Friday, 6 April)

ISSUE-25: Participants need to review wsc-usecases Web Security Context Issue Tracker (Thursday, 5 April)

Meeting record: WSC WG weekly 2007-03-28 Thomas Roessler (Thursday, 5 April)

Action item summary 2007-04-04 Thomas Roessler (Thursday, 5 April)

Comments about the note Jan Vidar Krey (Thursday, 5 April)

RE: review comments due April 4 Close, Tyler J. (Thursday, 5 April)

Available security information section clarification Close, Tyler J. (Thursday, 5 April)

XSS out of scope Close, Tyler J. (Thursday, 5 April)

RE: diffmk Close, Tyler J. (Wednesday, 4 April)

Firefox usability data on Location Bar Close, Tyler J. (Wednesday, 4 April)

Note review point - Scoping non-UI recs Johnathan Nightingale (Wednesday, 4 April)

Regrets Serge Egelman (Wednesday, 4 April)

Comments on Note Shawn Duffy (Wednesday, 4 April)

Regrets... and editing Shawn Duffy (Wednesday, 4 April)

Re: comments on use-cases Maritza Johnson (Wednesday, 4 April)

Comment on Note Bob Pinheiro (Wednesday, 4 April)

Comments RE: The Working draft Robert Yonaitis (Wednesday, 4 April)

Re: ACTION-149: FSTC's list of authentication techniques (BMA taxonomy) Mary Ellen Zurko (Tuesday, 3 April)

Re: Documenting status quo Mary Ellen Zurko (Tuesday, 3 April)

Fw: ACTION-156: List of privacy and security indicators Mary Ellen Zurko (Tuesday, 3 April)

RE: Regrets for April 4, Call Robert Yonaitis (Monday, 2 April)

Agenda, WEDNESDAY, 4 April, WSC Call Mary Ellen Zurko (Monday, 2 April)

Re: ISSUE-22: Rephrase favicon text Thomas Roessler (Monday, 2 April)

Re: ACTION-106 Propose clarifying language for 8.2.5 Thomas Roessler (Monday, 2 April)

Robustness practices -- pending (but closed) actions. Thomas Roessler (Monday, 2 April)

Re: What is a secure page? Thomas Roessler (Monday, 2 April)

Rough rec proposal: revisiting past decisions Thomas Roessler (Monday, 2 April)

RE: Recommendations for "Lightening Discussions" at next week's meeting michael.mccormick@wellsfargo.com (Monday, 2 April)

Re: Rec Proposal: Separate in-browser editor for entry of Personally Identifiable Information (PII) Thomas Roessler (Monday, 2 April)

Fw: ACTION-154 OPEN Track HTTP Auth related extensions Bill Doyle 2007-03-20 Mary Ellen Zurko (Monday, 2 April)

Lightening Recommendations Mary Ellen Zurko (Monday, 2 April)

Last message date: Monday, 30 April 2007 20:15:39 UTC