Skip to Main content Skip to Navigation
Journal articles

Referencing Source Code Artifacts: a Separate Concern in Software Citation

Abstract : Among the entities involved in software citation, software source code requires special attention, due to the role it plays in ensuring scientific reproducibility. To reference source code we need identifiers that are not only unique and persistent, but also support \emph{integrity} checking intrinsically. Suitable identifiers must guarantee that denoted objects will always stay the same, without relying on external third parties and administrative processes. We analyze the role of identifiers for digital objects (IDOs), whose properties are different from, and complementary to, those of the various digital identifiers of objects (DIOs) that are today popular building blocks of software and data citation toolchains. We argue that both kinds of identifiers are needed and detail the syntax, semantics, and practical implementation of the persistent identifiers (PIDs) adopted by the Software Heritage project to reference billions of software source code artifacts such as source code files, directories, and commits.
Complete list of metadata
Contributor : Morane Gruenpeter Connect in order to contact the contributor
Submitted on : Wednesday, January 22, 2020 - 4:46:47 PM
Last modification on : Friday, July 8, 2022 - 10:07:51 AM
Long-term archiving on: : Thursday, April 23, 2020 - 12:50:54 PM


Files produced by the author(s)





Roberto Di Cosmo, Morane Gruenpeter, Stefano Zacchiroli. Referencing Source Code Artifacts: a Separate Concern in Software Citation. Computing in Science and Engineering, Institute of Electrical and Electronics Engineers, In press, pp.1-9. ⟨10.1109/MCSE.2019.2963148⟩. ⟨hal-02446202⟩



Record views


Files downloads