-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathcamera-ready-instructions.html
More file actions
252 lines (209 loc) · 12.6 KB
/
Copy pathcamera-ready-instructions.html
File metadata and controls
252 lines (209 loc) · 12.6 KB
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
---
layout: default
---
{% include slider-cf-camera-ready-instructions.html %}
<!-- Content -->
<div class="block">
<div class="container">
<div class="row">
<div class="col-md-3">
<section class="events small" id="events-small">
<header>
<h2>Dates</h2>
</header>
<div class="section-content">
<article class="event nearest">
<figure class="date">
<div class="month">oct</div>
<div class="day">1</div>
</figure>
<aside>
<header>
<h>Camera-ready deadline</h>
</header>
</aside>
</article><!-- /article -->
<br>
</div><!-- /.section-content -->
</section><!-- /.events-small -->
<section class="events small" id="events-small">
<header>
<h2>Links</h2>
</header>
<div class="section-content">
<ul class="list-links">
<li><h4><a href="#submit">Submission site</a></h4></li>
<li><h4><a href="papers.html">Call for papers</a></h4></li>
<!--li><h4><a href="posters.html">Call for posters</a></h4></li-->
<li><h4><a href="program-committee.html">Program committee</a></h4></li>
</ul>
</div><!-- /.section-content -->
</section><!-- /.events-small -->
</div><!-- /.col-md-3 -->
<div class="col-md-6">
<section id="main-content">
<header>
<h1>Camera-ready preparation and copyright assignment</h1>
</header>
<div class="section-content">
<p>
These instructions are for the authors of accepted or conditionally accepted papers. Conditionally accepted
papers may be rejected, but authors should still follow the instructions optimistically until told to stop.
<br><br>
Time is short, so start now. Delays or mistakes could cause your paper to be excluded from the conference proceedings.
</p>
<a id="guidelines"><h2>Guidelines</h2></a>
<p>
As part of our efforts at fostering diversity and inclusiveness, we request you to adhere to the following guidelines on how to write the camera-ready version of your paper and prepare your conference presentation.
<p><b>Design for accessibility </b>: Color perception varies from person to person depending on
several factors such as age, <a href ="https://nei.nih.gov/health/color_blindness/facts_about">color blindness </a>, etc. To ensure that the contents of your paper are accessible to all, consider taking the following steps:
</p>
<ol type ="a">
<li><p> Use patterns, symbols and textures to emphasize and contrast visual elements in graphs and figures, rather than using colors alone. </p> </li>
<li><p>Use a color-blind friendly palette that is designed with accessibility for visually impaired people. Avoid bad color combinations such as green/red or blue/purple.
</p></li>
<li> <p> Write captions that describe the insight you want to highlight from each figure. </p></li>
</ol>
<p><b>Use inclusive examples</b>: Fine technical writing makes liberal use of examples to elucidate complex
ideas. But they also offer an opportunity to promote inclusiveness by challenging common implicit
assumptions and biases.</p>
<ol type ="a">
<li><p> Avoid the use of male pronouns (“he”, “his”) in favor of female (“she”, “her”) or gender-neutral (“they”, “their”) ones. </p></li>
<li><p> Pick names and icons associated with underrepresented minorities in our community, such as women, Latinos, etc.</p></li>
<li><p> Refrain from assuming binary gender. For instance, populate a “gender” column in a table using more than just “male” and “female” values.</p></li>
<li><p> Be mindful of the diverse backgrounds people have: not everyone has two parents, not every married man has a wife, etc. </p></li>
</ol>
</p>
<br><br>
<p>
</p><h4>To do now:</h4>
<p></p>
<ul>
<li><p><b style="color:red;">Email</b> the final title and author list to <b>Sumita Barahmand (sumitab [at] microsoft [dot] com)</b> by <b style="color:red;">13 September 2019</b>,
after which no changes are possible (this information will be used for the proceedings).
<br>
In your email, use the subject "SoCC 2019 final information" and in the body include a single line with the following format (including quotes): <br><br>
"Paper Type","Title","Lead Author:Affiliation;Author2:Affiliation;Author3:Affiliation;etc.","Lead Author e-mail",”Author e-mail;Author e-mail"
<br><br>
For "Paper Type" if you have a regular research or industry conference paper then use "Full Paper". For vision papers use “Short Paper”. If you have a poster abstract, then use "Abstract”.
<br><br>
<b>Sample record:</b> <br>
"Full Paper","This is a Sample Title","Adrienne Griscti:Association for Computing Machinery;Craig Rodkin:Peace University;John Smith:Hunter Corp.","griscti@hq.acm.org",”rodkin@pu.edu;smith@hunter.com”
</p></li>
<li><p> ACM will invite the lead author to <b style="color:red;">complete the ACM copyright form online</b>.
Do this promptly: this step blocks the rest. It provides the DOI, rights management text, and bibliographic strip that
must be in the paper. The permission and DOI info are on page 2 of the copyright document.
If you do not receive an email from ACM by <b>September 20th</b>, inform Sumita Barahmand.
It is an automatic email, so check your spam folder and set the spam settings to allow emails from "rightsreview@acm.org".</p></li>
<li><p>At least one of the authors must <b style="color:red;">register for the conference</b> to present the paper, so take advantage of the early registration discount.
</p></li>
</ul>
<h4>To do by <b style="color:red;">1 October 2019</b> (<b>Accepted Papers</b>):</h4>
<p>
Ship the final camera-ready materials. This includes the final PDF and <b>all source files
for each paper – all files which were used to create the final output (PDF), be they Word, LaTeX, image files, etc. </b>
In anticipation of serving both accessibility compliant PDF and responsive HTML5 formatted files from the ACM Digital Library, ACM is now enforcing this requirement.
The materials should be prepared this way:
</p><ul>
<li><p> Format the paper using the acmart.cls file available in <a href="https://acmsocc.github.io/2019/assets/camera-ready-tex/SoCC-acmart-master.zip">SoCC-acmart-master.zip</a>.
Example latex files are socc2019-sample-sigconf.tex and socc2019-sample-base.bib. Fonts used in the template <b>cannot</b> be substituted; margin adjustments are not allowed.
</li></p>
<li><p>Add the correct rights management statement and bibliographic strip on the bottom of the first page, left column. You will receive these details after completing your copyright form, after which you may need to replace the one in the template with the one from ACM.
</p></li>
<li><p>Use only Type 1 fonts (scalable), not Type 3 (bitmapped), and embed all fonts within the PDF.
ACM has documentation on <a href="http://www.acm.org/binaries/content/assets/publications/word-to-pdf-instructions-.txt">how to embed fonts correctly</a>.
It refers to the distiller settings file that can be found <a href="http://www.acm.org/binaries/content/assets/publications/acm1.joboptions">here</a></p></li>
<li><p>Do not include page numbers.
</p></li>
<li><p>Name your file according to this rule: paperID-lastnameOfFirstAuthor.pdf
</p></li>
<li><p>Apply keywords and ACM Computing Classification categories and terms.
For the classification of your paper follow the scheme <a href="http://www.acm.org/about/class/1998" target="_blank">here</a>.
</p></li>
<li><p>Follow the page limits in the <a href="https://acmsocc.github.io/2019/papers.html">submission</a>: <br>
<b>Full Paper</b>: 12 pages including the title page, abstract, and appendices, but excluding references. <br>
<b>Vision Paper</b>: 5 pages including the title page, abstract, and appendices, but excluding references. <br>
These limits are strict and final.
</p></li>
<li><p>Remove the "submission type" line, which you may have included in the submission.
</p></li>
<li><p> ACM requires titles and abstracts be submitted in English; author(s) (including affiliations) submitted using the Roman Alphabet as opposed to Cyrillic, Chinese, or Arabic.
</li></p>
<li><p>Use the paper-submission site (below) to upload your final camera-ready materials.
This includes the final PDF file, named according to the above criterion,
and an archive of your source files, which is a new ACM requirement.
</p></li>
</ul>
<p>
If you have any other question regarding the proceedings, contact <b>Sumita Barahmand (sumitab [at] microsoft [dot] com)</b>. Do not wait.
</p>
<a id="submit"><h2>Submission site</h2></a>
<p>
<b style="color:red;">Please use HotCRP to submit your camera ready materials: <a href="https://socc19.hotcrp.com" target="_blank">https://socc19.hotcrp.com</a></b>
</p>
</div><!-- /.section-content -->
</section><!-- /.main-content -->
</div><!-- /.col-md-6 -->
<div class="col-md-3">
<section class="news-small" id="news-small">
<header>
<h2>Latest news</h2>
</header>
<div class="section-content">
<a class="twitter-timeline" href="https://twitter.com/ACMSoCC">Tweets by acmsocc2018</a>
<script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script>
</section><!-- /.news-small -->
</div><!-- /.col-md-3 -->
</div><!-- /.row -->
</div><!-- /.container -->
</div>
<!-- end Content -->
</div>
<!-- Footer -->
<footer id="page-footer">
<section id="footer-top">
<div class="container">
<div class="footer-inner">
<div class="footer-social">
<!--<figure>Follow us:</figure>-->
<div class="icons">
<!--<a href="https://twitter.com/ACMSoCC2016"><i class="fa fa-twitter"></i></a>
<a href="https://www.facebook.com/socc2016"><i class="fa fa-facebook"></i></a> -->
</div><!-- /.icons -->
</div><!-- /.social -->
</div><!-- /.footer-inner -->
</div><!-- /.container -->
</section><!-- /#footer-top -->
<section id="footer-bottom">
<div class="container">
<div class="footer-inner">
<div class="copyright"></div><!-- /.copyright -->
</div><!-- /.footer-inner -->
</div><!-- /.container -->
</section><!-- /#footer-bottom -->
</footer>
<!-- end Footer -->
</div>
</body>
<script type="text/javascript" src="assets/js/jquery-2.1.0.min.js"></script>
<script type="text/javascript" src="assets/js/jquery-migrate-1.2.1.min.js"></script>
<script type="text/javascript" src="assets/bootstrap/js/bootstrap.min.js"></script>
<script type="text/javascript" src="assets/js/selectize.min.js"></script>
<script type="text/javascript" src="assets/js/owl.carousel.min.js"></script>
<script type="text/javascript" src="assets/js/jquery.validate.min.js"></script>
<script type="text/javascript" src="assets/js/jquery.placeholder.js"></script>
<script type="text/javascript" src="assets/js/jQuery.equalHeights.js"></script>
<script type="text/javascript" src="assets/js/icheck.min.js"></script>
<script type="text/javascript" src="assets/js/jquery.vanillabox-0.1.5.min.js"></script>
<script type="text/javascript" src="assets/js/retina-1.1.0.min.js"></script>
<script type="text/javascript" src="assets/js/custom.js"></script>
<script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+"://platform.twitter.com/widgets.js";fjs.parentNode.insertBefore(js,fjs);}}(document,"script","twitter-wjs");</script>
<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-39874729-4', 'auto');
ga('send', 'pageview');
</script>
</html>