ACM SIGs may authorize the posting of Tables of Contents of their scheduled upcoming sponsored conference proceedings with Author-Ized links enabling free full-text downloads from the ACM Digital Library.
Effective as of 2014, these OpenTOCs may be kept permanently on the conference site or the SIG site. The SIG must decide which site(s) to use.
The sponsoring SIGs may choose OpenTOC for the upcoming volume (rolling off after 12 months), or a permanent OpenTOC that remains permanently on the chosen site(s) to build up a local series archive, or no OpenTOC at all.
For co-sponsored conferences, all co-sponsors must agree to the posting and each co-sponsor may choose its site(s).
ACM HQ will be informed of the site(s), prepare the OpenTOC, and deliver it to the designated contact person for each conference.
If the SIG authorizes posting the OpenTOC, the designated conference leader should carry out that decision for each given volume of proceedings.
If a SIG authorizes a permanent OpenTOC for a given volume, rather than a rolling annual OpenTOC, it is advisable to place it on the site where it is most likely to be maintained.
Full-text downloads from the ACM Digital Library via OpenTOCs, Author-Izer, OpenSurround, OA, SIG membership, and Free articles are all being tracked and will be regularly reported to the SGB separately from downloads via subscription.
Updated March 2016
Policy Adopted May 2015
ACM is a volunteer-led and member-driven organization. Everything ACM accomplishes is through the efforts of people like you. A wide range of activities keep ACM moving, including organizing conferences, editing journals, reviewing papers and participating on boards and committees, to name just a few. Find out all the ways that you can volunteer with ACM.
Why I Belong to ACM
Hear from Bryan Cantrill, vice president of engineering at Joyent, Ben Fried chief information officer at Google, and Theo Schlossnagle, OmniTI founder on why they are members of ACM.
Written by leading domain experts for software engineers, ACM Case Studies provide an in-depth look at how software teams overcome specific challenges by implementing new technologies, adopting new practices, or a combination of both. Often through first-hand accounts, these pieces explore what the challenges were, the tools and techniques that were used to combat them, and the solution that was achieved.