Towards FAIR Principles for Research Software

The most viewed article in Data Science in the first half of 2020 focuses on FAIR principles in relation to research software. The position paper analyzes where the existing principles can directly be applied to software, where they need to be adapted or reinterpreted, and where the definition of additional principles is required. Here, we provide extracts from the article intoducing the four foundational FAIR principles in the context of research data. First, a little bit of background.


FAIR: Findable, Accessible, Interoperable, Reusable
In 2016, the FAIR guiding principles were first published in a paper by Barend Mons (corresponding author) and colleagues. The authors intended to provide guidelines to improve the findability, accessibility, interoperability, and reuse of digital assets. Since that article was published, the principles have been globally endorsed and widely adopted. As a consequence, the GO FAIR initiative was launched with an aim to implement the FAIR data principles, through events, implementation networks, workshops, and more. This also includes providing guidance on implementation areas for data stewardship.


Special Issue: FAIR Data, Systems and Analysis
The position paper extracted below has been published in Data Science in a new special issue entitled:"FAIR Data, Systems and Analysis." The co-Editors-in-Chief of the journal Michel Dumontier (Maastricht University) and Tobias Kuhn (VU University Amsterdam) were co-authors on the original FAIR guiding principles paper, as was Paul Groth (University of Amsterdam) who has joined Michel to guest edit the special issue. The editors comment in the editorial:

"The FAIR principles have established themselves as key focal point for encouraging the findability, accessibility, interoperability and reusability of data. Given this foundation, there is a need to develop concrete systems and tools that make the production and consumption of FAIR data possible. Likewise, there is a need to analyze, evaluate, measure and understand the ramifications of FAIR data. This special issue highlights research and systems tackling these challenges."



Position Paper: Towards FAIR Principles for Research Software

The following is extracted from the open access paper by Anna-Lena Lamprecht, et al., in the special issue "FAIR Data, Systems and Analysis" (guest editors: Paul Groth and Michel Dumontier) of Data Science, Vol.3, Iss.1, pp. 37–59, 2020.

The FAIR Guiding Principles were published and promoted to improve the reuse of scholarly data by making it more findable, accessible, interoperable, and reusable by humans and machines. Implementing FAIR helps researchers demonstrate the impact of their work by enabling the reuse and citation of the data they produce, and can promote collaboration among them. It also helps publishers and funders to define policies for data sharing, and to promote discoverability and reuse. In addition, it helps data stewards and managers to provide guidance on quality criteria for data deposits in digital repositories.

The authors' intention was that the principles not only apply to data, but also to other digital objects, e.g. algorithms, tools, and workflows, that led to that data, as all these elements must be available to ensure transparency, reproducibility and reusability. At the policy level, software is indeed seen as part of FAIR, with the European Commission expert group on FAIR data stating that “Central to the realisation of FAIR are FAIR Digital Objects, which may represent data, software or other research resources.” Applying the FAIR principles in a useful way to research software will provide similar benefits of enabling transparency, reproducibility and reusability of research, making it easier for industry, science, education and society to have effective access to software-based knowledge. In particular, FAIR software should facilitate making FAIR data.

However, software is data and software is not data. Over the last three years, numerous discussions have taken place with the aim of understanding how the FAIR principles relate to software. It is clear that the four foundational principles are intended to apply to software, but can we apply them in a practical and useful way? The terminology and detail used in the 15 FAIR Guiding Principles is focused on their application to data – particularly in the life sciences – and can be confusing if applied to software without translation. The drivers, stakeholders and incentives, whilst overlapping, are not identical. In addition, the variety of software and its distribution channels poses a challenge when adapting the current FAIR principles.

We understand the original 15 FAIR Guiding Principles as an instantiation of the four foundational FAIR principles in the context of research data.

Findability is a fundamental principle, since it is necessary to find a resource before any other consideration. The main concern of findability for research software is to ensure software can be identified unambiguously when looking for it using common search strategies. Such strategies include the use of keywords in general-purpose search engines like Google, as well as specialised registries (websites hosting software metadata) and repositories (websites hosting software source code and binaries). Findability can be improved by registering the software in a relevant registry, along with the provision of appropriate metadata, providing contextual information about the software. Registries typically render metadata in a web-findable way and can provide a DOI. Some registries and repositories allow annotating software using domain-agnostic or domain-specific controlled vocabularies, increasing findability via search engines further. In the following we discuss how the original four Findability principles apply to the findability of research software.

In the original FAIR Guiding Principles, accessibility translates into retrievability through a standardized communication protocol and accessibility of metadata even when the original resource is no longer accessible. These principles clearly also apply to software. Interpreting accessibility also as the ability to actually use the software (access its functionality), however, we found mere retrievability not enough. In order for anyone to use any research software, a working version of the software needs to be available. This is different from just archiving source code, even in comprehensive and long-term collections like the Software Heritage archive. To use software, a working version (binary or code) has to be either downloadable and/or accessible e.g., via a web interface, along with the required documentation and licensing information. Accessibility requirements depend on the software type, e.g., web-applications, command-line tools, etc. For example, software containers allow the use across different operating systems and environments, e.g., local computers, remote servers, and high-performance computing (HPC) installations. Cloud-based servers can execute existing pieces of code as a service, as software made available through a web interface or via Jupyter Notebooks. Notebooks allow others to see the results and the narrative alongside the code used to generate them.

When examining the FAIR data principles from a research software perspective, interoperability turns out to be the most challenging among the four high-level principles. This is not surprising given the complexity of the software interoperability challenges that form a research area of its own. Already for data and its associated metadata, interoperability has been found to be “the most challenging of the four FAIR principles. This, in part, is due to interoperability not being well understood.” In contrast to the rather static nature of data, research software are live digital objects that interact at different levels with other objects, e.g., other software, managed data, execution environments; and either directly and/or indirectly, as scripts or as part of a workflow (see Fig.1). The interoperability principles are therefore even more challenging to apply to software, some are not directly applicable, others need to be rephrased and even new principles need to be defined to appropriately address the dynamic nature of software.

Fig.1 Interoperability for research software can be understood in two dimensions: as part of workflows (horizontal dimension) and as stack of digital objects that need to work together at compilation and execution times (vertical dimension). Importantly, workflows do not need to use the same physical hardware or the same operating system, as long as there are agreed mechanisms for software to interoperate with one another.

Software interoperability can be defined from three different angles:

  • for a set of independent but interoperable objects to produce a runnable version of the software, including libraries, software source code, APIs and data formats, and any other resources for facilitating that task;
  • for a stack of digital objects that should work together for being able to execute a given task including the software itself, its dependencies, other indirect dependencies, the whole execution environment including runtime dependencies and the operating system, the execution environment, dependencies, and the software itself; and
  • for workflows, which interconnect different standalone software tools for transforming one or more data sets into one or more output data sets through agreed protocols and standards.

Thus, interoperability for software can be considered both for individual objects, which are the final product of a digital stack, and as part of broader digital ecosystems, which includes complex processes and workflows as well as their interaction. Different pieces of software can also work together independent of programming languages, operating systems and specific hardware requirements through the use of APIs and/or other communication protocols.

Reusability in the context of software has many dimensions. At its core, reusability aims for someone to be able to re-use software reproducibly. The context of this usage can vary and should cover different scenarios: (i) reproducing the same outputs reported by the research supported by the software, (ii) (re)using the code with data other than the test one provided to obtain compatible outputs, (iii) (re)using the software for additional cases other than those stated as supported, or (iv) extending the software in order to add to its functionality. Software reusability depends to a high degree on software maintainability, including proper documentation at various levels of detail. The legal framework, e.g., software licenses, is also important in terms of reusability as it determines how software can be built, modified, used, accessed and distributed. Furthermore, as research software is an integral part of the scientific process, credit attribution (citation) is another important aspect to consider with regard to (re)usability.



This is the second in a series of blog posts that will in future be found on the IOS Press Labs website (see post #1 here).

GET NEWS UPDATES: To receive news about IOS Press Labs, sign up for our newsletter here.

[Carmel McNamara | June 24, 2020]