RE: ACTION-515 and ACTION-516: Publishing John Kemp's TAG work on security

My conclusion about ACTION-515 is that we shouldn't do the action ("publishing John Kemp's TAG work on security") but rather consider a different action, which is to draft a TAG security roadmap. I marked

http://www.w3.org/2001/tag/group/track/actions/515

as pending review.  Perhaps we can discuss a TAG security roadmap (and other roadmaps we might want to produce) at the F2F?

Larry
--
http://larry.masinter.net


-----Original Message-----
From: Thomas Roessler [mailto:tlr@w3.org] 
Sent: Tuesday, August 09, 2011 11:06 PM
To: www-tag@w3.org
Cc: Thomas Roessler; Mark Nottingham; Larry Masinter; John Kemp; Tobias Gondrom; Noah Mendelsohn
Subject: Re: ACTION-515 and ACTION-516: Publishing John Kemp's TAG work on security

On Aug 9, 2011, at 21:41 , Tobias Gondrom wrote:
> 
> actually am not quite sure about the purpose of this document and how I can help.
> Agree with Mark, the page is a basic introduction, but the aspired value and for whom and why is not clear to me.
> 
> If work/input is needed to help the IAB/TAG on the security topic or wiki pages, please let me know (with link to wiki/work item and aspired goals/results).
> 
> Btw. just fyi: a somewhat related doc in websec is http://tools.ietf.org/id/draft-hodges-websec-framework-reqs-00.txt (where we try to define requirements to be used by websec and W3C WebAppSec). But still very rough, i.e. work in progress.

Another related document is, of course, the excellent Browser Security Handbook:
	http://code.google.com/p/browsersec/wiki/Main

I'd recommend to review the existing documents first and to find out what exactly the TAG is trying to add to those.

Received on Thursday, 18 August 2011 13:55:28 UTC