-
Notifications
You must be signed in to change notification settings - Fork 0
/
workshops.html
executable file
·265 lines (184 loc) · 13.5 KB
/
workshops.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->
<link rel="apple-touch-icon" sizes="57x57" href="images/favicons/apple-icon-57x57.png">
<link rel="apple-touch-icon" sizes="60x60" href="images/favicons/apple-icon-60x60.png">
<link rel="apple-touch-icon" sizes="72x72" href="images/favicons/apple-icon-72x72.png">
<link rel="apple-touch-icon" sizes="76x76" href="images/favicons/apple-icon-76x76.png">
<link rel="apple-touch-icon" sizes="114x114" href="images/favicons/apple-icon-114x114.png">
<link rel="apple-touch-icon" sizes="120x120" href="images/favicons/apple-icon-120x120.png">
<link rel="apple-touch-icon" sizes="144x144" href="images/favicons/apple-icon-144x144.png">
<link rel="apple-touch-icon" sizes="152x152" href="images/favicons/apple-icon-152x152.png">
<link rel="apple-touch-icon" sizes="180x180" href="images/favicons/apple-icon-180x180.png">
<link rel="icon" type="image/png" sizes="192x192" href="images/favicons/android-icon-192x192.png">
<link rel="icon" type="image/png" sizes="32x32" href="images/favicons/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="96x96" href="images/favicons/favicon-96x96.png">
<link rel="icon" type="image/png" sizes="16x16" href="images/favicons/favicon-16x16.png">
<link rel="manifest" href="images/favicons/manifest.json">
<meta name="msapplication-TileColor" content="#ffffff">
<meta name="msapplication-TileImage" content="images/favicons/ms-icon-144x144.png">
<meta name="theme-color" content="#ffffff">
<meta name="description" content="2016 IEEE International Conference on Cloud and Autonomic Computing (ICCAC)">
<title>ICCAC 2016 Conference</title>
<!-- Bootstrap core CSS -->
<link href="dist/css/bootstrap.min.css" rel="stylesheet">
<!-- Custom styles for this template -->
<link href="offcanvas.css" rel="stylesheet">
</head>
<body>
<div id="navBar"></div>
<div class="container">
<div class="row row-offcanvas row-offcanvas-right">
<div class="col-xs-12 col-sm-9">
<!-- ************************ start main body ************************ -->
<h4>FAS*W 2016 (SASO AND ICCAC)</h4>
<h1>Call for Workshop Proposals</h1>
<p>2016 IEEE 1st International Workshops on Foundations and Applications of Self* Systems (FAS*W), Augsburg, Germany, September 12 & 16, 2016 </br>
<a href="http://fasstar2016.informatik.uni-augsburg.de/" target="_blank">http://fasstar2016.informatik.uni-augsburg.de/</a></br>
<a href="http://iccac2016.se.rit.edu/" target="_blank">http://iccac2016.se.rit.edu/</a></br>
<a href="http://saso2016.informatik.uni-augsburg.de" target="_blank">http://saso2016.informatik.uni-augsburg.de</a></br>
</p>
<p>=========================================================================</p>
<p>(Please accept our apologies if you receive multiple copies of this call)</p>
<p>The FAS* 2016 Steering Committee invites proposals for the Workshop Program to be held along with the technical conferences SASO 2016 and ICCAC 2016. FAS*W workshops will provide a meeting for presenting novel ideas in a less formal and possibly more focused way than the conferences themselves. Their aim is to stimulate and facilitate active exchange, interaction, and comparison of approaches, methods, and ideas related to specific topics, both theoretical and applied, in the general area of Self-Adaptive and Self-Organizing Systems as well as Cloud and Autonomic Computing. To motivate the discussion and participation of all the workshop attendants, we encourage organizers to get away of the typical "mini-conference" format of a workshop, and include more discussion sessions, panels, etc. Members from all areas of the SASO and ICCAC communities are invited to submit workshop proposals for review. Workshops on global challenges, applications or on new and emerging topics are particularly encouraged. Workshops can vary in length, but most will be one full day in duration. Optionally, if desired by the organizers, workshop proceedings can be published through IEEE. Attendance of workshops will be included in the registration fee for the main SASO/ICCAC conference</p>
<p>-------------------------------------------------------------------------</p>
<h4>Important Dates</h4>
<p>-------------------------------------------------------------------------</p>
<!--
<ul>
<li>Workshop proposal submission deadline: April 4, 2016*</li>
<li>Workshop acceptance notification: April 11, 2016*</li>
<li>CfP submission deadline: April 20, 2016</li>
<li>Workshop paper submission deadline: July 4, 2016</li>
<li>Workshop paper acceptance notification: July 17, 2016</li>
<li>Early registration Deadline: TBD</li>
<li>Camera-ready papers due: July 22, 2016</li>
<li>Workshop notes submission to WS chairs: July 26, 2016</li>
<li>Workshops dates: September 12 & 16, 2016</li>
</ul>
-->
<div id="workshopInfo"></div>
<p>* Please submit your workshop proposals as soon as possible (i.e. before April 4)! We will try to decide earlier on workshop acceptance in order to give the organizers more time to solicit papers.</p>
<p>-------------------------------------------------------------------------</p>
<h4>FAS*W 2016 Workshops - Requirements for Submission</h4>
<p>-------------------------------------------------------------------------</p>
<p>Proposals for workshops should be separated in two parts. The <b>first part</b> should be organized as preliminary call for papers or call for participation, depending on the intended format of the workshop, with a maximum of two pages and contain the following information:</p>
<ul>
<li>Title of the workshop.</li>
<li>A brief technical description of the workshop, specifying the workshop goals, the technical issues that it will address, and the relevance of the workshop to the main conferences. Please specify, which of the two main conferences the workshop assigned to (if any)!</li>
<li>Description of paper review process (if any) and acceptance standards in order to keep the workshop high in quality. Note that papers must be in the same format as the conference proceedings and may not be more than 6 pages in length.</li>
<li>The names, affiliations, postal addresses, phone numbers, and email addresses of the proposed workshop organizing committee. This committee should consist of three or four people knowledgeable about the technical issues to be addressed. The organizing committee should include individuals from multiple institutions.</li>
<li>The primary email address for contacting the organizing committee.</li>
<li>Expected duration of the workshop (half or full day).</li>
<li>A brief description of the workshop format.</li>
<li>List of potential program committee members (if applicable), including their title and affiliations.</li>
<li>List of potential invited speakers, panelists, or disputants (if applicable).</li>
</ul>
<p>The <b>second part</b> with a maximum of three pages should contain additional information not suitable for a Call for Papers, including:</p>
<ul>
<li>A discussion of why and to whom the workshop is of interest.</li>
<li>A list of related workshops held within the last three years, if any, and their relation to the proposed workshop.</li>
<li>Information about previous offerings of the proposed workshop: when and where it has been offered in the past, organizers names and affiliations, number of submissions, acceptances and registered attendees.</li>
<li>An indication of the envisaged acceptance rate (if applicable).</li>
<li>A description of the qualifications of the individual committee members with respect to organizing a SASO or ICCAC workshop, including a list of workshops previously arranged by any members of the proposed organizing committee, if any.</li>
<li>A list of places (distribution lists, web sites, journals, etc.) where the workshop is planned to be advertised.</li>
</ul>
<p>All proposals should be submitted in plain ASCII text or PDF format by electronic mail to the FAS*W 2016 Workshop Chairs, via Monika Lorenz, as described below.</p>
<p>The selection of the workshops to be included in the final FAS* 2016 Workshop program will be based upon multiple factors, including:</p>
<ul>
<li>the scientific/technical interest of the topics,</li>
<li>the quality of the proposal,</li>
<li>complementarity with the conference topics,</li>
<li>balance and distinctness of workshop topics, and </li>
<li>the capacity of the conference workshop program.</li>
</ul>
<p>Note that authors of proposals addressing similar and/or overlapping content areas and/or audiences may be requested to merge their proposals.</p>
<p>-------------------------------------------------------------------------</p>
<h4>Responsibilities of FAS* 2016 Workshop Organizers</h4>
<p>-------------------------------------------------------------------------</p>
<p>For all accepted proposals, FAS* 2016 will be responsible for:</p>
<li>Providing publicity for the workshop series as a whole.</li>
<li>Providing logistical support and a meeting place for the workshops.</li>
<li>Together with the organizers, determining the workshop date and time.</li>
<li>Liaising and coordinating between the workshop chairs and the finance chair, publicity chair, registration chair, and web chair for FAS*.</li>
<li>Arranging for publication of proceedings.</li>
<br>
<p>Workshop organizers will be responsible for the following:</p>
<li>Setting up a web site for the workshop.</li>
<li>Advertising the workshop (and the main FAS* conference), and issuing a call for papers and a call for participation.</li>
<li>Collecting and evaluating submissions, notifying authors of acceptance or rejection on a timely basis, and ensuring a transparent and fair selection process. All workshop organizers commit themselves to adopt the deadlines set by the committee.</li>
<li>Making the pdf of the whole workshop notes available to the workshop chair, as well as a list of audio-visual requirements and any special room requirements.</li>
<li>Writing a 1-page organizers’ introduction for the workshop proceedings.</li>
<li>Ensuring that the workshop organizers and the participants register for the workshop and/or the main conference (at least one author must register for the paper to appear in the proceedings).</li>
<p>FAS* reserves the right to cancel any workshop if the above responsibilities are not fulfilled, or if too few attendees register for the workshop to support its running costs.</p>
<p>-------------------------------------------------------------------------</p>
<h4>Submissions and Inquiries</h4>
<p>-------------------------------------------------------------------------</p>
Please send proposals (as a PDF document) and inquiries to:
Monika Lorenz <a href="mailto:[email protected] ">[email protected] </a>
<p>-------------------------------------------------------------------------</p>
FAS*W Workshop Chairs
<p>
Sameh Elnikety </br>
Microsoft Research, USA</br>
E-Mail: [email protected] </br>
</p>
<p>
Peter Lewis</br>
School of Engineering and Applied Science, Aston University, UK</br>
E-Mail: [email protected] </br>
</p>
<p>
Christian Müller-Schloer</br>
Institute for Systems Engineering, Leibniz University Hannover, DE</br>
E-Mail: [email protected]</br>
</p>
<p>-------------------------------------------------------------------------</p>
<!-- ************************ End main body ************************ -->
</div><!--/span-->
<div class="col-xs-6 col-sm-3 sidebar-offcanvas" id="sidebar">
<div id="rightPanel"></div>
</div><!--/span-->
</div><!--/row-->
<hr>
<footer>
<p>© 2016 ICCAC</p>
</footer>
</div><!--/.container-->
<!-- Start of Google Tracking Info -->
<script>
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
})(window,document,'script','//www.google-analytics.com/analytics.js','ga');
ga('create', 'UA-71619324-1', 'auto');
ga('send', 'pageview');
</script>
<!-- End of Google Tracking Info -->
<!-- Bootstrap core JavaScript
================================================== -->
<!-- Placed at the end of the document so the pages load faster -->
<script src="https://ajax.googleapis.com/ajax/libs/jquery/2.1.4/jquery.min.js"></script>
<script>window.jQuery || document.write('<script src="assets/js/vendor/jquery.min.js"><\/script>')</script>
<script src="dist/js/bootstrap.min.js"></script>
<!-- IE10 viewport hack for Surface/desktop Windows 8 bug -->
<script src="assets/js/ie10-viewport-bug-workaround.js"></script>
<script src="offcanvas.js"></script>
<!-- Start Loading shared items -->
<script>
$(document).ready(function(){
$('#rightPanel').load("includes/rightPanel.html"); .2
$('#navBar').load("includes/navBar.html");
$('#workshopInfo').load("impDates/workshops.html");
$(window).on('load', function(){
$('#AllcallNavLink').addClass('dkActive');
})
});
</script>
<!-- End Loading shared items -->
</body>
</html>