NFDI-RFC Standardisation Concept

Link to the service

 

Logo
Detailed description of the service 

One goal of the NFDI is to discuss, develop and disseminate technical specifications to advance the infrastructure for research data management. Technical publication is the process by which these results are disseminated to the general public. The technical editor of the FDM RFC is responsible for the final steps in the creation of the published technical specifications. The concept sets out the requirements for the tasks of the technical editor of the NFDI RFCs and describes how they work with the NFDI to produce these publications.

In order to quickly disseminate guidelines in research data management (RDM), it is proposed to set up a platform based on the Request For Comments (RFC) of the Internet Engineering Taskforce (IETF). This platform should make it easy to communicate new guidelines from the results of the NFDI initiatives and other developments in the field of RDM with the scientific community. The development of the RFC platform is part of the NFDI4Ing initiative. By establishing the platform across NFDI, visibility, benefits and acceptance should be increased. These guidelines present (discipline-specific) solutions for e.g. data formats and metadata standards, communication protocols between RDM systems, methods of handling research data, etc. The aim of this RFC platform is to quickly and easily convert the constantly changing state of knowledge in RDM and thus also the results from the NFDI initiatives into quasi-standards that build on one another and are implemented in the individual disciplines and also across disciplines. In the medium to long term, these can be elevated to established (DIN/ISO) standards. These standards will then already have been tried and tested in practice and will have received broad support from the specialist communities involved. By establishing the platform across the NFDI, visibility, benefits and acceptance are to be increased.

The NFDI RFC series is the archive series for documenting specifications for research data management, including general contributions from the areas of research data management and science as well as standardization documents. The starting point for creating RFCs is an initial structure that must adapt over time to developments in the area of RDM and NFDI. This also includes the development of organizational structures and policies. This is to be achieved through RFCs that build on one another. RFCs can complement one another over time or be replaced by revised versions.

Terms of use & restrictions

The NFDI RFCs are freely accessible to everyone via the Internet. Further information under preparation.

Contact 

Michael Selzer,  michael.selzer@kit.edu

Christian Langenbach, christian.langenbach@dlr.de

References

publications that reference (or report on using) the service

Link

#WhyNFDI

Standardization in research data management should be promoted to ensure the interoperability, reusability and long-term availability of data and thus increase the efficiency and quality of research.

Miscellaneous

 

Tags

NFDI4ING services may be relevant to different users according to varying requirements. To support filtering or sorting, we added a tag system outlining which archetype, phase of the data lifecycle, or degree of maturity a service corresponds to. By clicking on one of the tags below, you can get an overview of all services aligned with each tag.

This service has the following tags:

The tags correspond to:
The Archetypes: Services relevant to Alex – Bespoke Experiments, Betty – Research Software Engineering, Caden – Provenance Tracking, Doris – High Performance Computing, Ellen – Complex Systems, Fiona – Data Re-Use and Enrichment

The data lifecycle: Services related to Informing & Planning, Organising & Processing, Describing & Documenting, Storing & Computing,
Finding & Re-Using, Learning & Teaching

The maturity of the service: Services sorted according to their maturity and status of their integration into the larger NFDI service landscape. For this we use the Integration Readiness Level (IRL), ranging from IRL0 (no specifications, strictly internal use) up to IRL4 (fully integrated in the German research data landscape and the EOSC). Click here for a diagram outlining all Integration Readiness Levels.