| |||||||||||||
IEEE CS SPW 2013 : IEEE CS Security and Privacy Workshops (SPW) | |||||||||||||
Link: http://www.ieee-security.org/TC/SPW2013/cfw.php | |||||||||||||
| |||||||||||||
Call For Papers | |||||||||||||
Since 1980, the IEEE Symposium on Security and Privacy (SP) has been the premier forum for the presentation of developments in computer security and electronic privacy, and for bringing together researchers and practitioners in the field.
In order to further expand the opportunities for scientific exchanges, we created a new venue within the IEEE CS Technical Committee on Security and Privacy called Security and Privacy Workshops (SPW). The typical purpose of such a workshop is to cover a specific aspect of security and privacy in more detail, making it easy for the participants to attend IEEE SP and a specialized workshop at IEEE SPW with just one trip. Furthermore, the co-location offers synergies for the organizers. Historically, we have had some workshops (e.g. W2SP, SADFE) co-located with IEEE SP the last few years; the success and popularity of these workshops has led to us formalizing the process and expanding our scope. There will be some interaction in deciding upon and setting up a workshop, but the initial proposal should already contain as much as possible of the following information: •Contact information of the workshop organizer. •Date (Thursday, May 23, or Friday, May 24) and expected length of the workshop (up to 2 days). •Technical proposal (1 to 2 pages): Topics to be addressed; importance of these topics; preliminary call for papers/posters/contributions; preliminary program committee; proposed review process. •Publication policy: Workshop with or without official proceedings; potential publication via web, technical report, or electronic media. If workshops choose to publish proceedings then it is expected that they will use the IEEE Computer Society Press. The SPW organizers will set up a contract with the CS Press that the individual organizers can utilize. •Expected number of participants and other local meeting issues, such as the special requirements/equipment for the meeting room. •Biographies of workshop organizer(s), including workshop organization experience; particularly SPW organization. •Program committee: who has committed; who has been invited; who will be invited. •Preliminary call for papers/posters/contributions. •Commitment to use EasyChair for organization or reason for choosing otherwise. |
|