FAIR for Research Software WG Case Statement

11 May 2020

FAIR for Research Software WG Case Statement

One of the major challenges of data-driven research is to facilitate knowledge discovery by assisting humans and machines in their discovery of, access to, integration and analysis of data and their associated research objects, e.g., algorithms, software, and workflows. To address this, an initial effort to define a "DATA FAIRPORT"1 began in 2014 at the Lorentz workshop and transitioned into developing a set of FAIR data Guiding Principles in 2016. The details of the FAIR data principles2 strongly contribute to addressing this challenge with regard to research data, and the principles, at a high level, are intended to apply to all research objects; both those used in research and that form the outputs of research. Here we focus on the adaptation and adoption of the FAIR principles for the case of research software.

 

Software has become essential for research. To improve the findability, accessibility, interoperability, and reuse of research software3 , it is desirable to develop and apply a set of  FAIR Guiding Principles for software. Many of the high-level FAIR data principles can be directly applied to research software by treating software and data as similar digital research objects. However, specific characteristics of software — such as its executability, composite nature, and continuous evolution and versioning — make it necessary to revise and extend the original data principles.

 

Application of the FAIR principles to software will continue to advance the aims of the open science movement. The FAIR For Research Software Working Group (FAIR4RS WG) will be jointly convened as an RDA Working Group, FORCE11 Working Group, and Research Software Alliance (ReSA) Taskforce, in recognition of the importance of this work for the advancement of the research sector. FAIR4RS WG will enable coordination of a range of existing community-led discussions on how to define and effectively apply FAIR principles to research software, to achieve adoption of these principles.

 

The working group will deliver:

  • A document developed with community support defining FAIR principles for research software
  • A document providing guidelines on how to apply the FAIR principles for research software (based on existing frameworks)
  • A document summarising the definition of the FAIR principles for research software, implementation guidelines and adoption examples.

Please see https://www.rd-alliance.org/sites/default/files/case_statement/2020_RDA_... for the full Case Statement.


1 See also DTL, 2014; and Kok, 2014.

2 See also Wilkinson et al., 2016.

3 For further information refer to Clément-Fontaine et al., 2019.

 

 

Review period start: 
Monday, 11 May, 2020 to Thursday, 11 June, 2020
Documents : 
  • Daniel S. Katz's picture

    Author: Daniel S. Katz

    Date: 03 Jun, 2020

    This is just to make sure that comments can be seen

  • Daniel S. Katz's picture

    Author: Daniel S. Katz

    Date: 03 Jun, 2020

    This is just to make sure that comments can be seen - sorry for the duplicate...

  • Carlos Martinez-Ortiz's picture

    Author: Carlos Martinez...

    Date: 05 Jun, 2020

    On behalf of the Netherlands eScience center, we are very pleased to see the development of this working group and are very supportive of the group’s mission. In particular, we would like to express our support in specific topics in which we consider we could contribute to the WG.

    The working group will deliver a document with adoption examples of the FAIR principles for research software. The Netherlands eScience center could contribute to this document by providing adoption examples from our projects.

    We will for sure engage with the WG at various levels, given that Mateusz Kuzak sits in the steering committee, but we would also like to provide feedback as part of the feedback cohort.

    The WG will deliver also develop guidelines and promote adoption of guidelines. We could also contribute to these objectives, by different means. For example:

    • We could update the content of our fair-software.eu website to ensure recommendations in this website are in line with guidelines proposed by the WG.
    • As national center of expertise, we could stimulate national adoption of guidelines.
    • We could stimulate adoption of FAIR software guidelines in our own projects (make it a requirement on future calls).
    • We could use eScience supported events (such as WoSSS) as a forum for relevant parts of this work.

     

    We hope to be able to contribute to this WG and look forward to seeing the results coming from it.

     

submit a comment