Skip to main content


We are in the process of rolling out a soft launch of the RDA website, which includes a new member platform. Existing RDA members PLEASE REACTIVATE YOUR ACCOUNT using this link: Visitors may encounter functionality issues with group pages, navigation, missing content, broken links, etc. As you explore the new site, please provide your feedback using the UserSnap tool on the bottom right corner of each page. Thank you for your understanding and support as we work through all issues as quickly as possible. Stay updated about upcoming features and functionalities:


Dear all,
similar discussions have been taking place about software (that is not just a
special case of data), and the following short summary may be of interest for
your work in this area.
Of course, Bib(La)TeX entries are not meant to contain all relevant metadata
about software, there are other standards for that (like CodeMeta): for example,
we do not expect to find individual author roles or affiliations recorded there.
Nonetheless they are extremely useful when it comes to citing software in
publications, creating bibliographic reference lists, producing activity
reports, etc.
Hence the importance to have proper support for software entries in BibLaTeX,
but, like for @dataset, the @software entry in the stock BibLaTeX is just
another name for @misc, and does not fit the bill at all.
A significant amount of work has been done to determine:
– the fields needed to describe software in a bibliography
– the kind of entries needed for capturing the software facets
(@software alone is not enough)
– the best way to make these new fields and entries supported in existing stlyes
This has led to the development of the biblatex-software package, included in
all recent TeXLive distributions, and also separately available from CTAN at
This package is a /style extension/, that can be used to add to any existing
BibLaTeX bibliographic style support for the folloing four entries:
Biblatex-software supports inheritance between these entries, and provides a
broad set of parameters that allow to tweak the rendering of bibliographies as
desired, see the extensive documentation at [1] for more information.
It would be great to see a similar work done for @dataset, and I hope this
information about what we did for software (not only the technical
implementation, but also the process that led to it) may be of help
All the best

Roberto Di Cosmo
Computer Science Professor
(on leave at INRIA from IRIF/Université de Paris)
Software Heritage
Bureau C328 E-mail : ***@***.***
2, Rue Simone Iff Web page :
CS 42112 Twitter :
75589 Paris Cedex 12 Tel : +33 1 80 49 44 42
GPG fingerprint 2931 20CE 3A5A 5390 98EC 8BFC FCCA C3BE 39CB 12D3