A new article by Arfon M. Smith (GitHub, Inc.), Daniel S. Katz (University of Illinois at Urbana-Champaign), Kyle E. Niemeyer (Oregon State University), and the FORCE11 Software Citation Working Group posted on PeerJ lays out six priciples of software citation, arguing that “software should be cited on the same basis as any other research product.”
2016) Software citation principles. PeerJ Computer Science 2:e86 https://doi.org/10.7717/peerj-cs.86(
The abstract is reproduced below:
Software is a critical part of modern research and yet there is little support across the scholarly ecosystem for its acknowledgement and citation. Inspired by the activities of the FORCE11 working group focused on data citation, this document summarizes the recommendations of the FORCE11 Software Citation Working Group and its activities between June 2015 and April 2016. Based on a review of existing community practices, the goal of the working group was to produce a consolidated set of citation principles that may encourage broad adoption of a consistent policy for software citation across disciplines and venues. Our work is presented here as a set of software citation principles, a discussion of the motivations for developing the principles, reviews of existing community practice, and a discussion of the requirements these principles would place upon different stakeholders. Working examples and possible technical solutions for how these principles can be implemented will be discussed in a separate paper.
This post was produced through a cooperation between Caroline Barratt, Jennifer Dekker, Rachel DiCresce, Heather Hill, and Ashley Maynor (Editors-at-large for the week), Roxanne Shirazi (Editor for the week), Sarah Potvin (Site Editor), and Caitlin Christian-Lamb, Caro Pinto and Patrick Williams (dh+lib Review Editors).