summaryrefslogtreecommitdiff
path: root/macros/latex/contrib/biblatex-contrib/biblatex-software/manual.bib
blob: c9bc76a4ec6b0d3404ed22864b294f3d2cb39c39 (plain)
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
@software{2013ascl.soft05002P,
  author = {{Pontzen}, A. and {Ro{\v s}kar}, R. and {Stinson}, G. and {Woods}, R.},
  title = "{pynbody: N-Body/SPH analysis for python}",
  editor = {{Astrophysics Source Code Library}},
  year = 2013,
  month = may,
  eprint = {1305.002},
  eprinttype = "ascl",
  url = {http://adsabs.harvard.edu/abs/2013ascl.soft05002P},
  note = {Provided by the SAO/NASA Astrophysics Data System}
}

@manual {scilabdoc,
  title = {The offical Scilab documentation},
  related = {delebecque:hal-02090402v1},
  relatedstring = "In the official distribution of "
}

@Article{	  swhcacm2018,
  Author	= {Abramatic, Jean-Fran\c{c}ois and Di Cosmo, Roberto and
		  Zacchiroli, Stefano},
  Title		= {Building the Universal Archive of Source Code},
  Journal	= {Commun. ACM},
  issue_date	= {October 2018},
  Volume	= {61},
  Number	= {10},
  Month		= sep,
  Year		= {2018},
  ISSN		= {0001-0782},
  Pages		= {29--31},
  numpages	= {3},
  URL		= {http://doi.acm.org/10.1145/3183558},
  DOI		= {10.1145/3183558},
  acmid		= {3183558},
  Publisher	= {ACM},
  Address	= {New York, NY, USA}
}

@ARTICLE{2020GtCitation,
  author={Pierre {Alliez} and Di Cosmo, Roberto and Benjamin {Guedj} and Alain {Girault} and Mohand-Said {Hacid} and Arnaud {Legrand} and Nicolas {Rougier}},
  journal={Computing in Science and Engineering},
  title={Attributing and Referencing (Research) Software: Best Practices and Outlook From Inria},
  year=2020,
  volume=22,
  number=1,
  pages={39-52},
  abstract={Software is a fundamental pillar of modern scientific research, across all fields and disciplines. However, there is a lack of adequate means to cite and reference software due to the complexity of the problem in terms of authorship, roles, and credits. This complexity is further increased when it is considered over the lifetime of a software that can span up to several decades. Building upon the internal experience of Inria, the French research institute for digital sciences, we provide in this article a contribution to the ongoing efforts in order to develop proper guidelines and recommendations for software citation and reference. Namely, we recommend: first, a richer taxonomy for software contributions with a qualitative scale; second, to put humans at the heart of the evaluation; and third, to distinguish citation from reference.},
  keywords={Software packages;Complexity theory;Research and development;Libraries;Metadata;Best practices;Guidelines;Software citation;software reference;authorship;development process},
  doi={10.1109/MCSE.2019.2949413},
  ISSN={1558-366X},
  month={Jan},
  DMI-CATEGORY={jour},
  x-topic   = "opensc",
  note = {Available from \url{https://hal.archives-ouvertes.fr/hal-02135891}},
  urllocal  = "http://www.dicosmo.org/Articles/2020-CiSE-AttributingReferencing.pdf"
}

@Article{	  cise-2020-doi,
  Author	= {Di Cosmo, Roberto and Gruenpeter, Morane and Stefano Zacchiroli},
  Title		= {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 integrity checking
		  intrinsically. Suitable iden- tifiers 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.},
  Publisher	= {IEEE},
  Year		= {2020},
  ISSN		= {1521-9615},
  volume        = 22,
  number        = 2,
  pages         = {33-43},
  DMI-CATEGORY={jour},
  x-topic   = "opensc",
  doi       = {10.1109/MCSE.2019.2963148},
  urllocal  = "http://www.dicosmo.org/Articles/2020-CiSE-swhid.pdf",
  Journal	= {Computing in Science and Engineering}
}