Workshop follow-up: Minutes; next steps.

Hello,

it's high time to start the post-workshop discussions.  We have
draft minutes of the two days available here:

  http://www.w3.org/2005/Security/usability-ws/15-security-ws-wed
  http://www.w3.org/2005/Security/usability-ws/16-security-ws-thu

These are drafts of rough minutes. We'd welcome you to review
them, and to suggest any changes that you would like us to
make.  Please submit any such changes by close of business
Thursday this week.

All presentations are online and linked from the workshop
program now:

  http://www.w3.org/2005/Security/usability-ws/program

We're currently putting final touches on a workshop report that
we hope to have available shortly.

In terms of the most fruitful directions for chartering further
work, we'll be looking for your feedback on the following
general directions:

- Secure chrome
- Secure metadata
- Support for for form-fillers and password managers

I'll send some messages to seed threads on these in a moment.
We very much look forward to hearing your views on these.


In terms of the more general architecture-related topics, such
as requirements for HTTP authentication and authorization, the
Technical Architecture Group (TAG)

  http://www.w3.org/2001/tag/

is the forum that is most likely to carry forward the ball.

The TAG conducts its work on a public mailing list:

  http://www.w3.org/2001/tag/#Membership
  http://lists.w3.org/Archives/Public/www-tag/

There are some recent threads on that mailing list on topics
which relate to some the Workshop's discussions:

  Draft State Finding
  http://lists.w3.org/Archives/Public/www-tag/2006Feb/0076.html

  The 's' in https: more trouble than it's worth?
  http://lists.w3.org/Archives/Public/www-tag/2006Mar/0039.html  

  IETF documents - action item from TAG meeting.
  http://lists.w3.org/Archives/Public/www-tag/2006Apr/0001.html

The TAG has no specific work plan at this point to take up
results from the workshop; we'll make sure that, to the extent
needed, other follow-up work is properly coordinated with the
TAG.

Kind regards,
-- 
Thomas Roessler, W3C   <tlr@w3.org>

Received on Monday, 10 April 2006 17:28:50 UTC