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

Bob Pinheiro

• RE: Shared Public Knowledge (Wednesday, 18 April)
• Re: Shared Public Knowledge (Thursday, 12 April)
• Comment on Note (Wednesday, 4 April)

Bruno von Niman

• RE: Agenda, Wednesay, 25 April, WSC Call (Tuesday, 24 April)
• RE: Agenda, Wednesay, 11 April, WSC Call (Tuesday, 10 April)
• RE: Question re: Comments USE-Cases (Wednesday, 4 April)

Chuck Wade

• Re: Shared Public Knowledge (Saturday, 14 April)
• Re: FW: sitekey auth busted on BoA site (Thursday, 12 April)
• Re: Shared Public Knowledge (Thursday, 12 April)
• Re: Shared Public Knowledge (Thursday, 12 April)
• Re: Shared Public Knowledge (Thursday, 12 April)
• Re: Firefox usability data on Location Bar (Wednesday, 11 April)
• Re: ACTION-149: FSTC's list of authentication techniques (BMA taxonomy) (Wednesday, 4 April)

Close, Tyler J.

• Editing process for Recommendations (Friday, 27 April)
• baked Note edits (Friday, 27 April)
• RE: ISSUE-14: Technologies that reduce risk (Friday, 27 April)
• RE: ISSUE-19: Arrangement and formatting of use cases (Friday, 27 April)
• RE: ISSUE-20 OPEN Potential additions to Available Security Information (Friday, 27 April)
• RE: ISSUE-26 OPEN "currently deployed security information" (Friday, 27 April)
• RE: ISSUE-29 OPEN Define user agent in wsc-usecases (Friday, 27 April)
• RE: ISSUE-30 allow for remote opening of web browser (Friday, 27 April)
• RE: ISSUE-31 Correct scenarion 20 intended action (Friday, 27 April)
• ISSUE-15 closing (Thursday, 26 April)
• Updating TrustMe wiki page based on telecon (Monday, 23 April)
• RE: comments about note (Tuesday, 10 April)
• RE: ISSUE-27: [editorial?] techniques for content based detection (Tuesday, 10 April)
• RE: comments on use-cases (Tuesday, 10 April)
• RE: Question re: Comments USE-Cases (Tuesday, 10 April)
• RE: Firefox usability data on Location Bar (Tuesday, 10 April)
• RE: Firefox usability data on Location Bar (Tuesday, 10 April)
• RE: comments on use-cases (Tuesday, 10 April)
• RE: Comment on Note (Tuesday, 10 April)
• RE: Available security information section clarification (Tuesday, 10 April)
• RE: ISSUE-27: [editorial?] techniques for content based detection (Tuesday, 10 April)
• RE: Available security information section clarification (Tuesday, 10 April)
• RE: ISSUE-28: \"available security information\" (Tuesday, 10 April)
• RE: review comments due April 4 (Thursday, 5 April)
• Available security information section clarification (Thursday, 5 April)
• XSS out of scope (Thursday, 5 April)
• RE: diffmk (Wednesday, 4 April)
• Firefox usability data on Location Bar (Wednesday, 4 April)

Dan Schutzer

• RE: DNSSEC indicator (Thursday, 26 April)
• RE: DNSSEC indicator (Thursday, 26 April)
• RE: Rough proposal: Contextual Password Warnings (Monday, 23 April)
• RE: Suggestions for note resulting from a conversation with mez (Monday, 23 April)
• RE: Safe Web Browsing Mode (Monday, 23 April)
• DNSSEC indicator (Friday, 13 April)
• RE: Shared Public Knowledge (Thursday, 12 April)
• RE: XSS out of scope (Friday, 6 April)
• RE: Question re: Comments USE-Cases (Wednesday, 4 April)
• RE: Recommendations for "Lightening Discussions" at next week's meeting (Wednesday, 4 April)
• RE: Recommendations for "Lightening Discussions" at next week's meeting (Monday, 2 April)

Doyle, Bill

• Re: ISSUE-40: Drill-down access to all security information is not \'nice,\' it\'s required (by UAAG 1.0). (public comment) (Friday, 27 April)
• ISSUE-46: widely deployed baseline, yes; usage and presentation, yes (pubic comment) (Friday, 20 April)
• RE: ISSUE-47: define extension interface for content-scanning tools (public comment) (Friday, 20 April)
• RE: ISSUE-40: Drill-down access to all security information is not \'nice,\' it\'s required (by UAAG 1.0). (public comment) (Thursday, 19 April)
• RE: Shared Public Knowledge (Friday, 13 April)
• RE: ACTION-196 (Thursday, 12 April)
• RE: comments about note (Thursday, 12 April)
• RE: ACTION-154 Track HTTP Auth related extensions Bill Doyle 2007-03-20 (Friday, 6 April)
• comments about note (Tuesday, 3 April)

George Staikos

• Re: ACTION-188 summarize robustness practices in terms of limitations on sites\\\\\\\\' freedom (Sunday, 22 April)

Hallam-Baker, Phillip

• RE: Secure Internet Letterhead (Monday, 30 April)
• Secure Internet Letterhead (Saturday, 28 April)
• RE: DNSSEC indicator (Thursday, 26 April)
• RE: ACTION 181: Summary of EV certificate discussion, prototype recommendation (Wednesday, 25 April)
• RE: ACTION 181: Summary of EV certificate discussion, prototype recommendation (Wednesday, 25 April)
• RE: ACTION 181: Summary of EV certificate discussion, prototype recommendation (Wednesday, 25 April)
• ACTION 181: Summary of EV certificate discussion, prototype recommendation (Wednesday, 25 April)
• RE: No Padlock OID (Monday, 23 April)
• No Padlock OID (Sunday, 22 April)
• ACTION-189: Cabfourm X.509v3/ PKIX guidelines (Monday, 16 April)
• Cabfourm X.509v3/ PKIX guidelines (Monday, 16 April)

Jan Vidar Krey

• Comments about the note (Thursday, 5 April)

Johnathan Nightingale

• Proposed Recommendation: Identity indicator in chrome (Wednesday, 25 April)
• Proposed Recommendation: Page Info Summary (Wednesday, 25 April)
• Re: No Padlock OID (Monday, 23 April)
• ACTION-175 - Summarize robustness practices for Firefox (Tuesday, 17 April)
• Re: ISSUE-28: \"available security information\" (Monday, 9 April)
• Re: Agenda, Wednesay, 11 April, WSC Call (Monday, 9 April)
• Re: Note review point - Scoping non-UI recs (Monday, 9 April)
• Note review point - Scoping non-UI recs (Wednesday, 4 April)

Luis Barriga \(KI/EAB\)

• RE: Proposed Recommendation: Page Info Summary (Thursday, 26 April)
• RE: DNSSEC indicator (Thursday, 26 April)
• RE: FW: .safe TLD idea from ICANN (Monday, 16 April)
• RE: ISSUE-29: Define user agent in wsc-usecases (Friday, 13 April)

Maritza Johnson

• Re: comments on use-cases (Monday, 16 April)
• Re: Question re: Comments USE-Cases (Wednesday, 4 April)
• Re: comments on use-cases (Wednesday, 4 April)

Mary Ellen Zurko

• Agenda, Wednesay, 2 May, WSC Call (Monday, 30 April)
• RE: DNSSEC indicator (Monday, 30 April)
• Re: Secure Internet Letterhead (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 (Monday, 30 April)
• Fw: [Soups-announce] Call for SOUPS posters and discussion sessions (Friday, 27 April)
• ISSUE-31 Correct scenarion 20 intended action (Thursday, 26 April)
• ISSUE-30 allow for remote opening of web browser (Thursday, 26 April)
• ISSUE-29 OPEN Define user agent in wsc-usecases (Thursday, 26 April)
• ISSUE-26 OPEN "currently deployed security information" (Thursday, 26 April)
• ISSUE-24 OPEN [editorial] Add "known systemic flaws" to goals (Thursday, 26 April)
• ISSUE-23 OPEN Rephrase background on usable security in Process secion (Thursday, 26 April)
• ISSUE-20 OPEN Potential additions to Available Security Information (Thursday, 26 April)
• Re: ISSUE-19: Arrangement and formatting of use cases (Thursday, 26 April)
• Re: ISSUE-18: Clarify audience of wsc-usecases (Thursday, 26 April)
• Re: ISSUE-14: Technologies that reduce risk (Thursday, 26 April)
• Re: ISSUE-12: User-agents - future proofing (Thursday, 26 April)
• Re: ISSUE-7: Mental models? (Thursday, 26 April)
• Re: ISSUE-6 User Interface Issues for Constrained / Mobile Devices (Thursday, 26 April)
• Fw: Dublin workshop on web authoring (Thursday, 26 April)
• Re: ISSUE-69: New goal--Reduce the number of scenarios in which users\' security depends upon authenticating sites (Wednesday, 25 April)
• Re: Proposed Recommendation: Page Info Summary (Wednesday, 25 April)
• Re: ACTION 181: Summary of EV certificate discussion, prototype recommendation (Wednesday, 25 April)
• Re: ISSUE-68: Note summary, goals, and scope should more clearly focus on problem to be solved---impersonation (Wednesday, 25 April)
• Re: Summary of "What is a secure page?" discussion, first draft (Wednesday, 25 April)
• RE: ACTION-182 - SSL error anti patterns (Wednesday, 25 April)
• shared knowledge authentication of web sites (Tuesday, 24 April)
• Re: Shared Public Knowledge (Tuesday, 24 April)
• Re: Rough rec proposal: revisiting past decisions (Monday, 23 April)
• Agenda, Wednesay, 25 April, WSC Call (Monday, 23 April)
• Re: Use Cases Again (Monday, 23 April)
• RE: Safe Web Browsing Mode (Friday, 20 April)
• RE: Favicon anti-pattern (Friday, 20 April)
• Re: ACTION-182 (Friday, 20 April)
• Look over background for any further recommendations (Friday, 20 April)
• Re: ISSUE-65: testing throughout evolution of product (pubic comment) (Thursday, 19 April)
• Re: ISSUE-64: \'where\' is less universal than \'how\' for drill-down (public comment) (Thursday, 19 April)
• Re: ISSUE-63: consistency is good where it fits; it doesn\'t always fit; so undergird your consistency with a model (public comment) (Thursday, 19 April)
• Re: ISSUE-62: User-adjustable step size is part of Universal Design (public comment) (Thursday, 19 April)
• Re: ISSUE-61: Know you don\'t know your users (public comment) (Thursday, 19 April)
• Re: ISSUE-60: reinvent Help and DoIt (public comment) (Thursday, 19 April)
• Re: ISSUE-59: challenge and recover are essential; one presentation fits all -NOT (pubic comment) (Thursday, 19 April)
• Re: ISSUE-58: simplicity is in the [diverse] world of the user (public comment) (Thursday, 19 April)
• Re: ISSUE-57: qualify your interrupts; communicate subliminally always and through the focus rarely (public comment) (Thursday, 19 April)
• Re: ISSUE-56: habit is little help, here (public comment) (Thursday, 19 April)
• Re: ISSUE-55: realism is not universal, nor does ordinariness befit exceptional communications (public comment) (Thursday, 19 April)
• Re: ISSUE-54: user understanding is where it\'s at (pubic comment) (Thursday, 19 April)
• Re: ISSUE-53: augment general usability wisdom because you are operating on a fringe (as is WAI) (Public Comnment) (Thursday, 19 April)
• Re: ISSUE-52: benchmarking success -- it\'s out there (public comment) (Thursday, 19 April)
• Re: ISSUE-51: distinguished Chrome is not the answer (public comment) (Thursday, 19 April)
• RE: Safe Web Browsing Mode (Thursday, 19 April)
• Re: ACTION-188 summarize robustness practices in terms of limitations on sites\\\\\\\\' freedom (Thursday, 19 April)
• Re: ISSUE-50: present web security is not good enough; even \'though fixing that is out of scope for this deliverable (public comment) (Thursday, 19 April)
• Re: ISSUE-49: trust in browser password cache needs to be better justified (pubic comment) (Thursday, 19 April)
• Re: ISSUE-48: platform and browser security out of scope - NOT (public comment) (Wednesday, 18 April)
• Re: ISSUE-47: define extension interface for content-scanning tools (public comment) (Wednesday, 18 April)
• Re: ISSUE-46: define extension interface for content-scanning tools (public comment) (Wednesday, 18 April)
• Re: ISSUE-45: full legal entity identification (is a must) (pubic comment) (Wednesday, 18 April)
• Re: ISSUE-44: beyond \'who\' (some day) (pubic comment) (Wednesday, 18 April)
• Re: ISSUE-43: don\'t disable assistive technology (public comment) (Wednesday, 18 April)
• Re: ISSUE-42: Re: 3.2 Non-HTTP Web interactions (public comment) (Wednesday, 18 April)
• Re: ISSUE-41: limited guidance on presentation OK (public comment) (Wednesday, 18 April)
• Re: ISSUE-40: Drill-down access to all security information is not \'nice,\' it\'s required (by UAAG 1.0). (public comment) (Wednesday, 18 April)
• Re: ISSUE-39: cooperate with WAI-ARIA \'politeness\' (from public comments) (Wednesday, 18 April)
• Re: ISSUE-38: no safe haven in presentation space (from public comments) (Wednesday, 18 April)
• Re: ISSUE-37: qualify your interrupts (from public comments) (Wednesday, 18 April)
• RE: Shared Public Knowledge (Wednesday, 18 April)
• Re: ISSUE-36: presentation norms -- no oneSizeFitsAll (from public comments) (Tuesday, 17 April)
• Re: ISSUE-35: information overload/underload -- no oneSizeFitsAll (public comment) (Tuesday, 17 April)
• Re: ISSUE-34: Formal studies don\'t cover disability access adequately, use experts too - (public comment) (Tuesday, 17 April)
• ACTION-194 refine UrlRecommendation (Tuesday, 17 April)
• Agenda, Wednesay, 18 April, WSC Call (Monday, 16 April)
• RE: Recommendations for "Lightening Discussions" at next week's meeting (Monday, 16 April)
• Re: ISSUE-33: Charter retains authority Review of Note (Monday, 16 April)
• ACTION-188 summarize robustness practices in terms of limitations on sites\\\\\\\\' freedom (Monday, 16 April)
• Futures area of our wiki (Monday, 16 April)
• RE: ISSUE-29: Define user agent in wsc-usecases (Monday, 16 April)
• Re: FW: .safe TLD idea from ICANN (Monday, 16 April)
• Error handling proposal (Monday, 16 April)
• RE: Shared Public Knowledge (Friday, 13 April)
• Re: ACTION-172 OPEN Map threat trees to use case dimensions Stuart Schechter 2007-04-04 (Thursday, 12 April)
• Re: Shared Public Knowledge (Thursday, 12 April)
• RE: ISSUE-28: \"available security information\" (Thursday, 12 April)
• Agenda, Wednesay, 11 April, WSC Call (Monday, 9 April)
• Re: Available security information section clarification (Monday, 9 April)
• Re: ISSUE-25: Participants need to review wsc-usecases (Monday, 9 April)
• Re: ISSUE-28: \"available security information\" (Monday, 9 April)
• ACTION-154 Track HTTP Auth related extensions Bill Doyle 2007-03-20 (Friday, 6 April)
• Re: XSS out of scope (Friday, 6 April)
• Re: Available security information section clarification (Friday, 6 April)
• Re: Note review point - Scoping non-UI recs (Friday, 6 April)
• Re: Comment on Note (Friday, 6 April)
• Re: comments on use-cases (Friday, 6 April)
• Re: Comments RE: The Working draft - Section 7 (Friday, 6 April)
• Re: Comments RE: The Working draft - section 6.5 (Friday, 6 April)
• Re: Comments RE: The Working draft - section 6.2 (Friday, 6 April)
• Re: Comments RE: The Working draft - section 42. (Friday, 6 April)
• Re: Question re: Comments USE-Cases (Wednesday, 4 April)
• RE: Recommendations for "Lightening Discussions" at next week's meeting (Wednesday, 4 April)
• RE: Recommendations for "Lightening Discussions" at next week's meeting (Wednesday, 4 April)
• Re: ACTION-149: FSTC's list of authentication techniques (BMA taxonomy) (Tuesday, 3 April)
• Re: Question re: Comments USE-Cases (Tuesday, 3 April)
• Re: Documenting status quo (Tuesday, 3 April)
• Fw: ACTION-156: List of privacy and security indicators (Tuesday, 3 April)
• Agenda, WEDNESDAY, 4 April, WSC Call (Monday, 2 April)
• RE: Recommendations for "Lightening Discussions" at next week's meeting (Monday, 2 April)
• Fw: ACTION-154 OPEN Track HTTP Auth related extensions Bill Doyle 2007-03-20 (Monday, 2 April)
• Lightening Recommendations (Monday, 2 April)

michael.mccormick@wellsfargo.com

• RE: DNSSEC indicator (Monday, 30 April)
• RE: ACTION-182 - SSL error anti patterns (Friday, 27 April)
• RE: ACTION 181: Summary of EV certificate discussion, prototype recommendation (Wednesday, 25 April)
• RE: ACTION 181: Summary of EV certificate discussion, prototype recommendation (Wednesday, 25 April)
• RE: ACTION 181: Summary of EV certificate discussion, prototype recommendation (Wednesday, 25 April)
• RE: ACTION-182 (Monday, 23 April)
• RE: ACTION-182 (Monday, 23 April)
• ACTION-182 (Friday, 20 April)
• RE: Favicon anti-pattern (Friday, 20 April)
• RE: Recommendations for "Lightening Discussions" at next week's meeting (Tuesday, 17 April)
• RE: Shared Public Knowledge (Saturday, 14 April)
• RE: DNSSEC indicator (Friday, 13 April)
• RE: DNSSEC indicator (Friday, 13 April)
• Risky display-only use cases (ACTION-193) (Friday, 13 April)
• RE: FW: sitekey auth busted on BoA site (Thursday, 12 April)
• RE: Shared Public Knowledge (Thursday, 12 April)
• "The Emperor's New Security Indicators" (Thursday, 12 April)
• FW: sitekey auth busted on BoA site (Thursday, 12 April)
• FW: .safe TLD idea from ICANN (Thursday, 12 April)
• RE: DNSSEC indicator (Thursday, 12 April)
• Shared Public Knowledge (Wednesday, 11 April)
• RE: Recommendations for "Lightening Discussions" at next week's meeting (Tuesday, 3 April)
• RE: Recommendations for "Lightening Discussions" at next week's meeting (Monday, 2 April)

Mike Beltzner

• wsc-usecases review (Thursday, 26 April)
• Re: No Padlock OID (Sunday, 22 April)
• Re: XSS out of scope (Friday, 6 April)
• Re: Firefox usability data on Location Bar (Thursday, 5 April)
• Re: Comments about the note (Thursday, 5 April)
• Re: Question re: Comments USE-Cases (Wednesday, 4 April)

Robert Yonaitis

• Regrets: Agenda, Wednesay, 25 April, WSC Call (Wednesday, 25 April)
• RE: ISSUE-36: presentation norms -- no oneSizeFitsAll (from public comments) (Tuesday, 17 April)
• RE: Comments RE: The Working draft - section 6.2 (Thursday, 12 April)
• Regrets: 11 April, WSC Call (Wednesday, 11 April)
• RE: Comments RE: The Working draft - Section 7 (Friday, 6 April)
• RE: Question re: Comments USE-Cases (Wednesday, 4 April)
• Comments RE: The Working draft (Wednesday, 4 April)
• Introduction to group (Tuesday, 3 April)
• Question re: Comments USE-Cases (Tuesday, 3 April)
• Regrets for April 4, Call (Monday, 2 April)
• RE: Regrets for April 4, Call (Monday, 2 April)

Serge Egelman

• Re: Available security information section clarification (Monday, 9 April)
• Regrets (Wednesday, 4 April)

Shawn Duffy

• Regrets (Wednesday, 25 April)
• Re: XSS out of scope (Friday, 6 April)
• Re: XSS out of scope (Friday, 6 April)
• Re: XSS out of scope (Thursday, 5 April)
• Comments on Note (Wednesday, 4 April)
• Regrets... and editing (Wednesday, 4 April)

Stephen Farrell

• Re: No Padlock OID (Monday, 23 April)
• Re: No Padlock OID (Sunday, 22 April)
• Re: Shared Public Knowledge (Saturday, 14 April)
• Re: Shared Public Knowledge (Thursday, 12 April)
• Re: Shared Public Knowledge (Thursday, 12 April)

Stuart E. Schechter

• Re: DNSSEC indicator (Thursday, 26 April)
• Suggestions for note resulting from a conversation with mez (Monday, 23 April)
• Use Cases Again (Wednesday, 18 April)
• Re: DNSSEC indicator (Friday, 13 April)
• Re: DNSSEC indicator (Friday, 13 April)
• Re: DNSSEC indicator (Friday, 13 April)
• Re: DNSSEC indicator (Thursday, 12 April)

Thomas Roessler

• Re: Editing process for Recommendations (Saturday, 28 April)
• Meeting record: WSC WG weekly 2007-04-18 (Friday, 27 April)
• Re: ISSUE-24 OPEN [editorial] Add "known systemic flaws" to goals (Thursday, 26 April)
• Re: DNSSEC indicator (Thursday, 26 April)
• Re: Rough rec proposal: revisiting past decisions (Monday, 23 April)
• Re: Rough proposal: Contextual Password Warnings (Monday, 23 April)
• Re: ACTION-188 summarize robustness practices in terms of limitations on sites' freedom (Sunday, 22 April)
• Meeting record: WSC WG weekly 2007-04-11 (Thursday, 19 April)
• Re: ISSUE-33: Charter retains authority Review of Note (Monday, 16 April)
• Re: Action item concerning mixed content / "what is a secure page" (Monday, 16 April)
• agenda item for this week? (Re: Action item concerning mixed content / "what is a secure page") (Monday, 16 April)
• Re: FW: .safe TLD idea from ICANN (Monday, 16 April)
• [fwd] Re: Shared Public Knowledge (from: dan.schutzer@fstc.org) (Sunday, 15 April)
• Meeting record: WSC WG weekly 2007-04-04 (Thursday, 12 April)
• Action item summary 2007-04-11 (Thursday, 12 April)
• Re: comments about note (Thursday, 12 April)
• Re: Proposed action item concerning robustness of user agent UIs (Wednesday, 11 April)
• Re: Available security information section clarification (Wednesday, 11 April)
• Re: comments about note (Wednesday, 11 April)
• Re: ISSUE-27: [editorial?] techniques for content based detection (Tuesday, 10 April)
• Re: status of my action items -- some due date adjustments (Monday, 9 April)
• Re: Note review point - Scoping non-UI recs (Sunday, 8 April)
• Re: Available security information section clarification (Sunday, 8 April)
• Re: XSS out of scope (Sunday, 8 April)
• Re: ISSUE-25: Participants need to review wsc-usecases (Sunday, 8 April)
• status of my action items -- some due date adjustments (Sunday, 8 April)
• Action item concerning mixed content / "what is a secure page" (Thursday, 5 April)
• Proposed action item concerning robustness of user agent UIs (Thursday, 5 April)
• Meeting record: WSC WG weekly 2007-03-28 (Thursday, 5 April)
• Action item summary 2007-04-04 (Thursday, 5 April)
• Re: diffmk (Thursday, 5 April)
• Re: Question re: Comments USE-Cases (Wednesday, 4 April)
• Re: Question re: Comments USE-Cases (Wednesday, 4 April)
• Re: Question re: Comments USE-Cases (Wednesday, 4 April)
• Re: ISSUE-22: Rephrase favicon text (Monday, 2 April)
• Re: ACTION-106 Propose clarifying language for 8.2.5 (Monday, 2 April)
• Robustness practices -- pending (but closed) actions. (Monday, 2 April)
• Re: Recommendations for "Lightening Discussions" at next week's meeting (Monday, 2 April)
• Re: What is a secure page? (Monday, 2 April)
• Rough rec proposal: revisiting past decisions (Monday, 2 April)
• Re: Rec Proposal: Separate in-browser editor for entry of Personally Identifiable Information (PII) (Monday, 2 April)

Timothy Hahn

• Re: ISSUE-18: Clarify audience of wsc-usecases (Friday, 27 April)
• Re: Agenda, Wednesay, 25 April, WSC Call (Wednesday, 25 April)
• Re: ISSUE-51: distinguished Chrome is not the answer (public comment) (Thursday, 19 April)
• RE: Shared Public Knowledge (Wednesday, 18 April)
• RE: Shared Public Knowledge (Wednesday, 18 April)
• regrets for 17 April call (Tuesday, 17 April)
• regrets for 11 April WSC call (Wednesday, 11 April)
• Re: ISSUE-28: \"available security information\" (Monday, 9 April)

Web Security Context Issue Tracker

• ISSUE-72: Replace term \"Status Quo\" with something more specific (Wednesday, 25 April)
• ISSUE-71: Change title of Section 7 (Wednesday, 25 April)
• ISSUE-70: Scope should be defined in terms of concepts, not in terms of use cases (Wednesday, 25 April)
• ISSUE-69: New goal--Reduce the number of scenarios in which users\' security depends upon authenticating sites (Wednesday, 25 April)
• ISSUE-68: Note summary, goals, and scope should more clearly focus on problem to be solved---impersonation (Wednesday, 25 April)
• ISSUE-67: The introduction to the note should include a hyperlink to the charter. (Wednesday, 25 April)
• ISSUE-66: Suggested rewrite of last paragraph of 10.3 (Monday, 23 April)
• ISSUE-65: testing throughout evolution of product (pubic comment) (Tuesday, 17 April)
• ISSUE-64: \'where\' is less universal than \'how\' for drill-down (public comment) (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) (Tuesday, 17 April)
• ISSUE-62: User-adjustable step size is part of Universal Design (public comment) (Tuesday, 17 April)
• ISSUE-61: Know you don\'t know your users (public comment) (Tuesday, 17 April)
• ISSUE-60: reinvent Help and DoIt (public comment) (Tuesday, 17 April)
• ISSUE-59: challenge and recover are essential; one presentation fits all -NOT (pubic comment) (Tuesday, 17 April)
• ISSUE-58: simplicity is in the [diverse] world of the user (public comment) (Tuesday, 17 April)
• ISSUE-57: qualify your interrupts; communicate subliminally always and through the focus rarely (public comment) (Tuesday, 17 April)
• ISSUE-56: habit is little help, here (public comment) (Tuesday, 17 April)
• ISSUE-55: realism is not universal, nor does ordinariness befit exceptional communications (public comment) (Tuesday, 17 April)
• ISSUE-54: user understanding is where it\'s at (pubic comment) (Tuesday, 17 April)
• ISSUE-53: augment general usability wisdom because you are operating on a fringe (as is WAI) (Public Comnment) (Tuesday, 17 April)
• ISSUE-52: benchmarking success -- it\'s out there (public comment) (Tuesday, 17 April)
• ISSUE-51: distinguished Chrome is not the answer (public comment) (Tuesday, 17 April)
• ISSUE-50: present web security is not good enough; even \'though fixing that is out of scope for this deliverable (public comment) (Monday, 16 April)
• ISSUE-49: trust in browser password cache needs to be better justified (pubic comment) (Monday, 16 April)
• ISSUE-48: platform and browser security out of scope - NOT (public comment) (Monday, 16 April)
• ISSUE-47: define extension interface for content-scanning tools (public comment) (Monday, 16 April)
• ISSUE-46: define extension interface for content-scanning tools (public comment) (Sunday, 15 April)
• ISSUE-45: full legal entity identification (is a must) (pubic comment) (Sunday, 15 April)
• ISSUE-44: beyond \'who\' (some day) (pubic comment) (Sunday, 15 April)
• ISSUE-43: don\'t disable assistive technology (public comment) (Sunday, 15 April)
• ISSUE-42: Re: 3.2 Non-HTTP Web interactions (public comment) (Sunday, 15 April)
• ISSUE-41: limited guidance on presentation OK (public comment) (Sunday, 15 April)
• ISSUE-40: Drill-down access to all security information is not \'nice,\' it\'s required (by UAAG 1.0). (public comment) (Sunday, 15 April)
• ISSUE-39: cooperate with WAI-ARIA \'politeness\' (from public comments) (Sunday, 15 April)
• ISSUE-38: no safe haven in presentation space (from public comments) (Sunday, 15 April)
• ISSUE-37: qualify your interrupts (from public comments) (Sunday, 15 April)
• ISSUE-36: presentation norms -- no oneSizeFitsAll (from public comments) (Sunday, 15 April)
• ISSUE-35: information overload/underload -- no oneSizeFitsAll (public comment) (Friday, 13 April)
• ISSUE-34: Formal studies don\'t cover disability access adequately, use experts too - (public comment) (Friday, 13 April)
• ISSUE-33: Charter retains authority Review of Note (Friday, 13 April)
• ISSUE-32: explain dynamic content better (Thursday, 12 April)
• ISSUE-31: Correct scenarion 20 intended action (Thursday, 12 April)
• ISSUE-30: (Thursday, 12 April)
• ISSUE-29: Define user agent in wsc-usecases (Thursday, 12 April)
• ISSUE-28: \"available security information\" (Sunday, 8 April)
• ISSUE-27: [editorial?] techniques for content based detection (Sunday, 8 April)
• ISSUE-26: \"currently deployed security information\" (Sunday, 8 April)
• ISSUE-25: Participants need to review wsc-usecases (Thursday, 5 April)

Yngve N. Pettersen (Developer Opera Software ASA)

• Re: Summary of "What is a secure page?" discussion, first draft (Tuesday, 24 April)
• Summary of "What is a secure page?" discussion, first draft (Tuesday, 24 April)

Yngve Nysaeter Pettersen

• Re: Summary of "What is a secure page?" discussion, first draft (Wednesday, 25 April)
• Re: FW: .safe TLD idea from ICANN (Monday, 16 April)
• Re: DNSSEC indicator (Thursday, 12 April)

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