PRO Research: An ontology for describing RDM-Policies in a structured way.
language en

PRO Research: An ontology for describing RDM-Policies in a structured way.

Release: 2025-10-14

Modified on: 2025-11-04
This version:
http://w3id.org/nfdi4ing/pro-research/1.0.0/
Revision:
v1.0.0
Issued on:
2025-11-04
Authors:
Tobias Hamann
Contributors:
Tobias Hamann, RWTH Aachen University
Publisher:
National Research Data Infrastructure for Engineering Sciences (NFDI4ING)
Imported Ontologies:
m4i
biro
cr
dcat
dcc
dcterms
foaf
owl
prov
qudt
rdf
rdfs
schema
sio
skos
ssn
xsd
Extended Ontologies:
emmo
obo
pims-ii
sirp
sis
Funder:
https://ror.org/018mejw64
Download serialization:
JSON-LD RDF/XML N-Triples TTL
License:
https://creativecommons.org/licenses/by/4.0/ License
Visualization:
Visualize with WebVowl
Evaluation:
Evaluate with OOPS!
Cite as:
Hamann, Tobias (2025). PRO Research: An ontology for describing RDM-Policies in a structured way. v1.0.0. http://w3id.org/nfdi4ing/pro-research/1.0.0 [ttl, jsonld, nt, rdf/xml].
DOI:
https://doi.org/10.5281/zenodo.17523317
Vocabulary maintained at:
https://git.rwth-aachen.de/nfdi4ing/pro-research/pro-research-ontology
Provenance of this page
active

Abstract

The ontology PRO Research provides a framework for the semantic description of research data management policies, research data management and of the whole data generation process based on the PRO research process (https://preprints.inggrid.org/repository/view/57/). The structure and application of the ontology are based on the principles of modularity and inheritance.

Introduction back to ToC

## Motivation The PRO Research (Project- and RDM-Oriented Research) Ontology provides an ontology to describe research processes along with corresponding policies. In this way, institutional and project-specific policies and guidelines related to Research Data Management (RDM) can be described sematically. Furthermore, the ontology describes the [PRO Research Process](https://preprints.inggrid.org/repository/view/57/) as designed by Hamann et al. [[1](#1)] Between the process and the policies, connections are drawn, mapping the different RDM tasks to the individual steps in research. Its primary goal is to represent how policies, and research processes are formally connected within research. It sets the foundation of the formal description of RDM policies, research processes and research outputs. This approach focusses on project-oriented research. The ontology is developed within the NFDI4Ing consortium as part of the ongoing effort to standardize and harmonize RDM-related documentation and policies across institutions. It evolves continuously through collaboration with research institutions, policy experts, and metadata specialists, ensuring alignment with community needs and interoperability with existing ontologies such as [Metadata4Ing](http://w3id.org/nfdi4ing/metadata4ing/1.3.1/). [[2](#2)] ## Usage The PRO Research Ontology defines a controlled vocabulary of classes and properties that enable machine-readable representation of research data policies, guidelines, and their relationships, as well as their connection to the research process and its outputs. In this way, research projects, their requirements regarding RDM and their results can be enriched with semantic and machine-readable metadata, in order to annotate it or to integrate it in a database or a larger knowledge graph. It can be used to: - Define institutional or project-related RDM policies in a standardized, FAIR-compliant format. - Integrate policy information into metadata of research projects and research data. - Support automated reasoning about compliance, responsibilities, and requirements in the context of research data management. The ontology supports serializations in - [JSON-LD](https://www.w3.org/TR/json-ld11/), - [YAML-LD](https://json-ld.github.io/yaml-ld/spec/) or - [Turtle](https://www.w3.org/TR/turtle/). There are four mayor use cases for the PRO Research Ontology, depicted in figure [1](#figure-1-the-use-cases-of-the-pro-research-ontology). 1. The standardised and formal description of RDM-guidelines in a machine-actionable format. 2. The querying of these formalised RDM guidelines by researchers. 3. The documentation of the actual research and RDM performed by researchers. 4. The querying for documented research projects, datasets and research results. #### Figure 1: The use cases of the PRO Research Ontology ![Use Cases of the PRO Research Ontology](visualizations/UseCases.png) ## Design The ontology is structured around a custom RDM policy model and the [PRO Research Process](https://preprints.inggrid.org/repository/view/57/). It can be used to formally describe any project-oriented research project or RDM guideline. Along with that, also the connections between the results of one research project and the reuse of these in another research project can be described by the PRO Research Ontology. Core classes represent entities such as: - RDM-Guidelines as regulatory documents by funding organisations, universities or institutes - RDM-Policies as a formal and semantic description of RDM Guidelines - RDM-Activities as detailled definition of activities performed to manage research data - Classes for phases, steps and tasks in the research process of projects. The properties describe relationships and connect those classes to each other. The ontology reuses established terms and structures from relevant standards such as Dublin Core, Schema.org, and SKOS, and introduces new terms in the namespace pro-research. Rather than importing entire external ontologies, the PRO Research Ontology selectively references and extends individual terms where needed to ensure clarity, usability, and domain relevance. When editorial adjustments (e.g. language-specific labels, harmonized definitions) were necessary, these were explicitly marked using skos:editorialNote at the entity level. --- ## General structure of an ontology The RDM Policy Ontology models the conceptual domain of research data management governance and project-oriented research processes. It does so by adapting the [Metadata4Ing](http://w3id.org/nfdi4ing/metadata4ing/1.3.1/) ontology [[2](#2)] and introducing classes and properties. A **class** stands for a group of individuals that all share some common properties. A **subclass** stands for a subset of this group. For example, the class [_RDM-Activity_](#RDMActivity) stands for the concept of an activty performed in RDM in general; [_Create DMP_](#CreateDMP) is a subclass of [_RDM-Activity_](#RDMActivity), representing only the creation of a DMP. If a specific procedure how a DMP should be created is formulated, than this is a policy-related **instance** of [_Create DMP_](#CreateDMP). If the DMP is created in a research project, than this is a project-related **instance** of [_Create DMP_](#CreateDMP). The first defines how the DMP should be created, the second one documents how it is actually done. In both instances, the tool recommended or used is documented. This documentation provides an overview of all classes, properties, and individuals defined or reused within the PRO Research Ontology, along with their intended semantics and interconnections. ---

Namespace declarations

Table 1: Namespaces used in the document
bibo<http://purl.org/ontology/bibo/>
dct<http://purl.org/dc/terms#>
doap<http://usefulinc.com/ns/doap#>
foaf<http://xmlns.com/foaf/0.1/>
metadata4ing<http://w3id.org/nfdi4ing/metadata4ing#>
obo<http://purl.obolibrary.org/obo#>
obo1<http://purl.obolibrary.org/obo/>
owl<http://www.w3.org/2002/07/owl#>
pror<http://w3id.org/nfdi4ing/pro-research#>
prov<http://www.w3.org/ns/prov#>
rdf<http://www.w3.org/1999/02/22-rdf-syntax-ns#>
rdfs<http://www.w3.org/2000/01/rdf-schema#>
resource<http://semanticscience.org/resource/>
schema<https://schema.org/>
skos<http://www.w3.org/2004/02/skos/core#>
terms<http://purl.org/dc/terms/>
v3<http://www.loc.gov/premis/rdf/v3/>
vann<http://purl.org/vocab/vann/>
xml<http://www.w3.org/XML/1998/namespace>
xsd<http://www.w3.org/2001/XMLSchema#>

PRO Research: Overview back to ToC

This ontology has the following classes and properties.

Classes

Object Properties

Data Properties

Named Individuals

PRO Research: Description back to ToC

General process model

One of the main use cases of the PRO Research Ontology is the mapping of [_Research activities_](#ResearchActivity) onto a project-oriented research process, namely the [PRO Research Process](https://preprints.inggrid.org/repository/view/57/) as designed by Hamann et al. [[1](#1)] (see figure [2](#figure-2-the-pro-research-process-as-designed-by-hamann-et-al-1)). #### Figure 2: The [PRO Research Process](https://preprints.inggrid.org/repository/view/57/) as designed by Hamann et al. [[1](#1)] ![The PRO Research Process](visualizations/ResearchProcessImage.png) This process is modelled within the PRO Research Ontology, which enables researchers to document the provenance of artefacts created or findings discovered during the research project. The process has three levels that directly correlate to the output they generate. On the top level, also called the [_Project-Level_](#Project-Level), the research project is conducted from start to finish. Once this level is completed, the project ist completed. On the middle level, also called the [_Finding-Level_](#Finding-Level), findings are compiled from aquired information. As the information is semantically conected, these findings represent knowledge as by definition. [[3](#3)] On the lowest level, also called [_Artefact-Level_](#Artefact-Level), data is collected and annotated with metadata. This creates artefacts (data + metadata), which is information by definition. [[3](#3)] The methods or tools used in the research process can be described in separate classes that can be linked to their corresponding step in the process. Simmilarly, RDM-Activities that have to be conducted in a certain way can both be given as input to a process step as well as be documented that way. Figure [3](#figure-3-the-pro-research-process-as-modelled-in-the-pro-research-ontology) depicts the implementation of the process in the ontology. #### Figure 3: The [PRO Research Process](https://preprints.inggrid.org/repository/view/57/) as modelled in the PRO Research Ontology ![The PRO Research Process as modelled in the PRO Research Ontology](visualizations/ProcessGraph.png) Figure [4](#figure-4-the-connection-of-the-research-project-the-process-and-the-phases) shows the exemplar connection of the research project, the process within and the phases. #### Figure 4: The connection of the research project, the process and the phases. ![The connection of the research project, the process and the phases](visualizations/ProcessPhasesExample.png) Figure [5](#figure-5-the-connection-of-the-research-project-the-process-and-the-steps) shows the exemplar connection of the research project, the process within and the phases. #### Figure 5: The connection of the research project, the process and the steps. ![The connection of the research project, the process and the steps](visualizations/ProcessStepsExample.png) Figure [6](#figure-6-the-connection-of-the-research-project-the-process-and-the-steps) shows the exemplar connection of the research project, the process within and the tasks. #### Figure 6: The connection of the research project, the process and the tasks. ![The connection of the research project, the process and the tasks](visualizations/ProcessTasksExample.png)

Processing step as central element

Simmilarly to the [Metadata4Ing](http://w3id.org/nfdi4ing/metadata4ing/1.3.1/) ontology [[2](#2)], the [processing step](https://nfdi4ing.pages.rwth-aachen.de/metadata4ing/metadata4ing/#ProcessingStep) is a central element to the PRO Research Ontology. However, unlike [Metadata4Ing](http://w3id.org/nfdi4ing/metadata4ing/1.3.1/) ontology [[2](#2)] it can not be used to describe all kinds of processes as it distinguishes between different types of processing steps. It introduces two new subclasses, namely the [_RDM-Activity_](#RDMActivity) and the [_Research activity_](#ResearchActivity), both shown in figure [7](#figure-7-the-correlation-of-processing-steps-rdm-activites-and-rdm-guidelines-and--policies). #### Figure 7: The correlation of Processing steps, RDM-Activites and RDM-Guidelines and -Policies ![The correlation of Processing steps, RDM-Activites and RDM-Guidelines and -Policies](visualizations/ProcessingStepVSGuideline_Image.png) [_RDM-Activity_](#RDMActivity) is intentionally general: it can represent any policy-governed RDM-activity (Creating a DMP, Document data collection, archiving, setting a license etc.). For these specific RDM-activities, seperate subclasses are defined. These also relate to specific aspects of the corresponding policy. For example, [_Set PID_](#SetPID) is a [_RDM-Activity_](#RDMActivity) that, among others, is part of the [_Publication Aspect_](#PublicationAspect) of an [_RDM-Policy_](#RDM-Policy).

General RDM-Policy model

A key role of the PRO Research Ontology is to connect governed [_RDM-Activities_](#RDMActivity) to the [processing step](#ProcessingStep) that contain them. For this, a general RDM-Policy model exists within the PRO Research Ontology. It consists of: - the [_RDM-Guideline_](#RDM-Guideline) , which represents the actual document of a funding organisation, university, institute or project - the [_RDM-Policy_](#RDM-Policy), which represents a formalised version of a RDM-guideline - aspects of the [_RDM-Policy_](#RDM-Policy) that relate to different kinds of [_RDM-Activities_](#RDMActivity) - [_RDM-Activities_](#RDMActivity), that describe the actual RDM-Activities to be conducted throughout the research It shall be noted that while a [_RDM-Guideline_](#RDM-Guideline) should always have a formalised version of itself, namely the [_RDM-Policy_](#RDM-Policy), the inverse of this restraint does not neccessarily apply. This means that not every formalised [_RDM-Policy_](#RDM-Policy) needs an [_RDM-Guideline_](#RDM-Guideline) as counterpart. Furthermore, the aspects of the [_RDM-Policy_](#RDM-Policy) help to structure the the [_RDM-Policy_](#RDM-Policy) by topics, making it easier for RDM-Teams or scientific supporting staff to fill out the standardised and formal description of RDM-guidelines in a machine-actionable format. On the left hand side, figure [8](#figure-8-the-correlation-of-the-research-project-rdm-activites-rdm-guidelines-and--policies) shows the relation of the research project, its process and activities, processing steps and [_RDM-Activities_](#RDMActivity). On the right hand side, it depicts the correlation between the [_RDM-Guideline_](#RDM-Guideline) and a correlating [_RDM-Policy_](#RDM-Policy) as well as one exemplar aspect of the [_RDM-Policy_](#RDM-Policy), in this case the [_Publication Aspect_](#PublicationAspect). In the middle, different exemplar RDM-Activities that are part of the example aspect ([_Publication Aspect_](#PublicationAspect)) are displayed. #### Figure 8: The correlation of the Research project, RDM-Activites, RDM-Guidelines and -Policies ![The correlation of the Research project, RDM-Activites, RDM-Guidelines and -Policies](visualizations/Policy_ProcessAndRDMActivitiesAndPolicy.png) The connection of the example [_RDM-Activity_](#RDMActivity) [_Set PID_](#SetPID) and its corresponding aspects is shown in figure [9](#figure-9-the-correlation-of-rdm-activites-and-different-aspects-of-the-rdm-policies-and-the-rdm-policies-themselves). For instance, [_Set PID_](#SetPID) is part of the aspects [_Archiving Aspect_](#ArchivingAspect), [_Documentation Aspect_](#DocumentationAspect), [_Metadata Aspect_](#MetadataAspect) and [_Publication Aspect_](#PublicationAspect). #### Figure 9: The correlation of RDM-Activites and different aspects of the RDM-Policies and the RDM-Policies themselves ![The correlation of RDM-Activites and different aspects of the RDM-Policies and the RDM-Policies themselves](visualizations/Policy_RDMActivitiesAndAspectsAndPolicy.png)

Specifying in- and output as artefacts

As in [Metadata4Ing](http://w3id.org/nfdi4ing/metadata4ing/1.3.1/) [[2](#2)], the [_processing step_](#ProcessingStep) is used to connect data and material objects to the processing step they were created in or modified by. However, in the PRO Research Ontology, the way of describing data and material objects is by instanciating them as [_Artefacts_](#Artefact). These are created on the [_Artefact-Level_](#Artefact-Level) by firstly conducting a [_Generation setup_](#Generation-Setup), then the actual [_Generation_](#Generation) of the artefact itself, a [_Check_](#Check) for correct data generation (Note: This is no validation of the data!), and [_Storing_](#Store). The last step creates the artefact. As metadata is recorded alongside the data generation, the data is automatically enriched. Hence, an artefacht is data with context (metadata) rendering it information. Each Processing step and therefore each [_Research-Activity_](#Research-Activity) and [_RDM-Activity_](#RDM-Activity) can have no, one or more inputs in the form of artefacts. Hence, the artefacts can be specified via [_has input_](#http://purl.obolibrary.org/obo/RO_0002233), whereas the resulting output of the corresponding processing step can be modelled as a new instance that is specified via [_has output_](#http://purl.obolibrary.org/obo/RO_0002234), e.g. a DMP. As in [Metadata4Ing](http://w3id.org/nfdi4ing/metadata4ing/1.3.1/) [[2](#2)], [_has input_](#http://purl.obolibrary.org/obo/RO_0002233) can also be used to indicate other things that acted as input in a processing step, e.g. chemical substances or datasets (cf. [Section "Specifying datasets"](#3-10-specifying-datasets)). Still, all of them have to be considered an [_Artefact_](#Artefact), either reused or generated. [_Artefacts_](#Artefact) can refer to all kinds of entites, regardless of whether they are material (e.g. physical objects) or immaterial (e.g. datasets). However, simmilarly to [Metadata4Ing](http://w3id.org/nfdi4ing/metadata4ing/1.3.1/) [[2](#2)], [_Artefacts_](#Artefact) should not be used for specifying tools used in a processing step or the investigated object (e.g. for a measurement), both of which can be indicated with more specific properties described in the next subsections (cf. [_has employed tool_](#hasEmployedTool) and [_investigates_](#investigates)).

Specifying the research results as findings

Many processes (e.g. measurements or simulations) performed during research aim to generate new knowledge. As knowledge is semantically connected information [3](#3), semantically connected [_Artefacts_](#Artefact) form new knowledge. In the PRO Research Ontology, this knowledge is represented by [_Findings_](#Finding). These are created by compiling [_Artefacts_](#Artefact) in the [_Finding compilation_](#Finding-compilation) step.

Specifying the RDM-requirements as RDM-Policies

In the PRO Research Ontology, requirements brought up by funding organisations, universities, institute or consortia in research projects can be formalised by using [_RDM-Policies_](#RDM-Policy). These contain [_RDM-Activities_](#RDM-Activity). These are atomic parts of the RDM, containing specifications on how these [_RDM-Activities_](#RDM-Activity) are to be performed. If these are part of a policy, they contain a recommendation degree (mandatory, recommended, optional). Furthermore, they contain information on the tools to be used, the settings for those tools, and other information, both needed or helpful. For instance, [_Create DMP_](#CreateDMP) may feature information on tools to be used as well as templates to be used for the DMP.

Specifying the RDM conducted as RDM-Activites

In the PRO Research Ontology, the documentation of the RDM performed in research projects can be also formalised by using [_RDM-Policies_](#RDM-Policy). These contain [_RDM-Activities_](#RDM-Activity). These are atomic parts of the RDM, containing specifications on how these [_RDM-Activities_](#RDM-Activity) have been performed. If the [_RDM-Activities_](#RDM-Activity) describe the RDM actually conducted in a research project, the same sturcture of the RDM-Policy applies. However, there is no recommendation degree. Instead, the actual solution is instanciated along with the tools, settings and other information.

Specifying complex RDM-requirements as multiple RDM-Policies

In many research projects, more than one RDM-Guideline applies. For example every DFG-funded project on every of the TU9 universities both has to adhere to the DFG's RDM-Guideline as well as the universities guideline. Even more guidelines may be relevant for a single project, e.g. an institute or project guideline. To account for this, the PRO Research ontologie models these guidelines as individual instances of guidelines independently from the project along with their corresponding policies. When it comes to a project to be conducted, the individual policies are querried. From the results of this query, researchers get all currenty relevant RDM-Policies. This means, that for a single [_RDM-Activity_](#RDM-Activity) in the process multiple instances of this [_RDM-Activity_](#RDM-Activity) can apply to the research project. The researchers can then decide on the options they have based on the recommendation degree (mandatory, recommended, optional). The options chosen for this [_RDM-Activity_](#RDM-Activity) are then documented as new instances of the [_RDM-Activity_](#RDM-Activity)in the research project. This might even mean, that there are multiple instances of a single [_RDM-Activity_](#RDM-Activity) in a project. This occurs if two contradicting RDM-Policies both need to be adhered for that specific [_RDM-Activity_](#RDM-Activity).

Specifying the publication process and related publications

The publication of data, software, manuscripts in journals or even science communication in the form of e.g. newspaper articles, social media posts etc. can be supported and documented with the PRO Research Ontology. Figure [10](#figure-10-the-publication-process-its-steps-and-exemplar-rdm-activities-conntected) shows the publication process, its steps and some exemplar RDM-Activities conntected. These are part of different steps in the publication process and can be demanded by RDM-Policies and documented for the individual publication jst like every other element of the PRO Research Ontology. #### Figure 10: The publication process, its steps and exemplar RDM-Activities conntected ![The publication process, its steps and exemplar RDM-Activities conntected](visualizations/PublicationProcessExample.png)

Cross-reference for PRO Research classes, object properties and data properties back to ToC

This section provides details for each class and property defined by PRO Research.

Classes

Accessibility Aspectc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#AccessibilityAspect

All research data management activities that fall under the aspect of accessibility of research data.
has super-classes
RDM-Policy c

Acquire funding for RDMc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#AcquireFundingForRDM

Acquire funding for RDM.
has super-classes
RDM-Activity c

Adhere to citation rulesc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#AdhereToCitationRules

Adhere to citation rules.
has super-classes
RDM-Activity c

Adhere to export controlsc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#AdhereToExportControls

Adhere to export controls.
has super-classes
RDM-Activity c

Adhere to GWPc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#AdhereToGWP

Good scientific practice (GWP, https://www.dfg.de/en/basics-topics/basics-and-principles-of-funding/good-research-practice) must be adhered to.
has super-classes
RDM-Activity c

Adhere to licensesc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#AdhereToLicenses

Adhere to licenses for reused data.
has super-classes
RDM-Activity c

Adhere to patent lawc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#AdhereToPatentLaw

Adhere to patent law
has super-classes
RDM-Activity c

Allow Open Access for Datac back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#AllowOpenAccessForData

Enable Open Access for research data.
has super-classes
RDM-Activity c

Allow Open Source for Softwarec back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#AllowOpenSourceForSoftware

Enable Open Source for research software.
has super-classes
RDM-Activity c

Anonymize datac back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#AnonymizeData

Anonymize data.
has super-classes
RDM-Activity c

Archive unique/expensive datac back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#ArchiveUniqueExpensiveData

Archive unique/expensive data.
has super-classes
RDM-Activity c

Archiving Aspectc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#ArchivingAspect

All research data management activities that fall under the aspect of archiving of research data.
has super-classes
RDM-Policy c

Artefactc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#Artefact

The result of one iteration of the artefact level. An artefact is planned, contextualised and validated research data in its smallest unit. It may be a result of primary data collection or the implementation of source code. It was generated by creating a generation setup, generating the data and performing a check to ensure the correct recording and, if valid, storing the data. An artefact is data with meaning and is therefore information.
has super-classes
Creative Work c

Artefact-Levelc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#Artefact-Level

The level on which artefacts are generated. It contains the tasks generation setup, generate, check and store. It has a straight forward structure with distinct tasks following one after another.
has super-classes
Level c

Checkc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#Check

Check the generated data for corruption. This task ensures data correctness with a check to ensure the correct recording of data. If the data was correctly recorded, it is stored. If the data was not correctly recorded, it is deleted.
has super-classes
Task c

Clarify rights ownershipc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#ClarifyRightsOwnership

Clarify which project partners have which rights to which research data and research software.
has super-classes
RDM-Activity c

Comply with retention periodsc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#ComplyWithRetentionPeriods

Complying with retention periods: usually 10 years after PID or completion of research projects (later date)
has super-classes
RDM-Activity c

Comply with the general legal frameworkc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#ComplyWithGeneralLegalFramework

Complying with general legal frameworks (data protection, copyright, etc.).
has super-classes
RDM-Activity c

Conduct anonymizationc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#ConductAnonymization

Conduct anonymization.
has super-classes
RDM-Activity c

Conduct archivingc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#ConductArchiving

The actual execution of archiving according to previously defined criteria.
has super-classes
RDM-Activity c

Conduct backupc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#ConductBackup

Conduct backup.
has super-classes
RDM-Activity c

Conduct communicationc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#ConductCommunication

Conduct communication.
has super-classes
RDM-Activity c

Conduct deletion of Datac back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#ConductDeletionOfData

Conduct deletion of unused or no longer needed data, e.g. after project completion for non-archived data. Data may only be deleted if everything has been taken into account, e.g. stakeholder consideration.
has super-classes
RDM-Activity c

Conduct deletion of personal datac back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#ConductDeletionOfPersonalData

Conduct deletion of personal data.
has super-classes
RDM-Activity c

Conduct ethical considerationsc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#ConductEthicalConsiderations

Conduct and document ethical considerations.
has super-classes
RDM-Activity c

Conduct long-term archivingc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#ConductLongTermArchiving

Conduct long-term archiving for more than 10 years.
has super-classes
RDM-Activity c

Conduct publicationc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#ConductPublication

Conduct publication, i.e. publish research results in appropriate channels.
has super-classes
RDM-Activity c

Conduct storagec back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#ConductStorage

Conduct storage.
has super-classes
RDM-Activity c

Consider applicable codes of conductc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#ConsiderApplicableCodesOfConduct

Consider applicable codes of conduct.
has super-classes
RDM-Activity c

Consider contractual framework conditionsc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#ConsiderContractualFrameworkConditions

Consider contractual framework conditions.
has super-classes
RDM-Activity c

Consider domain-specific metadata standardsc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#ConsiderDomainSpecificMetadataStandards

Consider domain-specific metadata standards.
has super-classes
RDM-Activity c

Consider economic framework conditionsc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#ConsiderEconomicFrameworkConditions

Consider economic framework conditions.
has super-classes
RDM-Activity c

Consider other university policiesc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#ConsiderOtherUniversityPolicies

Beyond the university's FDM guidelines, other policies may apply, such as Open Access policies.
has super-classes
RDM-Activity c

Consider professional standardsc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#ConsiderProfessionalStandards

Consider professional standards. The specifics of these standards depend on the discipline. This includes subject-specific requirements. These can include specialised documentation.
has super-classes
RDM-Activity c

Consider sensitive datac back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#ConsiderSensitiveData

Take sensitive data into account, e.g. by anonymizing the data.
has super-classes
RDM-Activity c

Consider software as research datac back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#ConsiderSoftwareAsResearchData

Software shall be considered as research data.
has super-classes
RDM-Activity c

Convert Data To Formats For Archivingc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#ConvertDataToFormatsForArchiving

Convert data to formats for archiving.
has super-classes
RDM-Activity c

Create DMPc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#CreateDMP

Creating a Data Management Plan (DMP).
has super-classes
RDM-Activity c

Create or Reusec back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#Create-Or-Reuse

The step of creating a new artefact or reusing an existing one by importing it into the current project. The creation of a new artefact can be done by using any amount of existing artefacts.
has super-classes
Step c

Create README filec back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#CreateReadmeFile

Create README file.
has super-classes
RDM-Activity c

Data Minimisation Aspectc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#DataMinimisationAspect

All RDM activities of an RDM policy that fall under the aspect of data minimization during collection and storage of research data.
has super-classes
RDM-Policy c

Decide on the publication of datac back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#DecideOnPublicationOfData

Decide on the publication of data.
has super-classes
RDM-Activity c

Define formal and substantive quality standardsc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#DefineFormalAndSubstantiveQualityStandards

Define formal and substantive quality standards.
has super-classes
RDM-Activity c

Definition of research datac back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#ResearchDataDefinition

The specifically applicable definition of research data.
has super-classes
RDM-Activity c

Deletion Aspectc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#DeletionAspect

All RDM activities of an RDM policy that fall under the aspect of data deletion.
has super-classes
RDM-Policy c

Determine liabilityc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#DetermineLiability

Determine liability.
has super-classes
RDM-Activity c

Determine the start of planningc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#DetermineStartOfPlanning

Determine the start of planning of RDM measures. Usually at the beginning of the proposal writing.
has super-classes
RDM-Activity c

Deviation from RDM-Specifications with other guidelinesc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#DeviationsFromRDMSpecifications

Permitted deviations from the RDM: Deviation from the RDM guideline is only permitted in justified exceptional cases. Other guidelines remain in place (e.g. contracts in contract research or data protection law) or a planned commercial utilisation conflicts with the RDM. Other applicable requirements must be observed.
has super-classes
RDM-Activity c

Disseminationc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#Dissemination

Last of the five publication process phases. Dissemination includes all activities that promote the distribution of a publication, such as inclusion in the personal, publicly accessible publication list, social media posts or even personal recommendations via mailing lists.
has super-classes
Publications Process c

Dissemination Aspectc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#DisseminationAspect

All RDM activities of an RDM policy that fall under the aspect of data dissemination and communication.
has super-classes
RDM-Policy c

Document anonymizationc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#DocumentAnonymization

Document anonymization.
has super-classes
RDM-Activity c

Document Archivingc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#DocumentArchiving

The archiving of research data must be documented. In particular, it should be documented where the data is stored, how long it is retained, and who has access to the data.
has super-classes
RDM-Activity c

Document data analysisc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#DocumentDataAnalysis

Document data analysis
has super-classes
RDM-Activity c

Document data collectionc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#DocumentDataCollection

Document data collection including boundary/external conditions
has super-classes
RDM-Activity c

Document data deletionc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#DocumentDataDeletion

Document data deletion.
has super-classes
RDM-Activity c

Document data interpretationc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#DocumentDateninterpretation

Document data interpretation
has super-classes
RDM-Activity c

Document data processingc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#DocumentDataProcessing

Document data processing.
has super-classes
RDM-Activity c

Document embargo periodc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#DocumentEmbargoPeriod

Document, if an embargo period exists, and how long it is.
has super-classes
RDM-Activity c

Document reused datac back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#DocumentReusedData

Documentation of reused data (from external sources).
has super-classes
RDM-Activity c

Document storagec back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#DocumentStorage

Document storage.
has super-classes
RDM-Activity c

Document used toolsc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#DocumentUsedTools

Document used tools, tools or services that were used during the research.
has super-classes
RDM-Activity c

Documentation Aspectc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#DocumentationAspect

All RDM activities of an RDM policy that fall under the aspect of data documentation.
has super-classes
RDM-Policy c

Editingc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#Editing

The third of the five publication process phases. Can only be started if the topic and scoping phase is finished. Includes all activities that revolve around the actual production of text.
has super-classes
Publications Process c

ELS Aspectc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#ELSAspect

All RDM activities of an RDM policy that concern ethical, legal or social aspects of research data.
has super-classes
RDM-Policy c

Ensure data accuracyc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#EnsureDataAccuracy

Ensure data accuracy. Compliance with data accuracy. Differs from data correctness in that the data has sufficient resolution.
has super-classes
RDM-Activity c

Ensure data authenticityc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#EnsureDataAuthenticity

Ensure data authenticity. This means that the data comes from a trusted source, is genuine, and has been collected in a traceable manner.
has super-classes
RDM-Activity c

Ensure data completenessc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#EnsureDataCompleteness

Ensure data completeness. This means that all data is present and no data has been withheld. If data is withheld, this must be justified and documented. Withholding data must not change the research results.
has super-classes
RDM-Activity c

Ensure data correctnessc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#EnsureDataCorrectness

Ensure data correctness. This means that the data was collected correctly and without distortion. It makes no statement about the resolution of the data or whether the data collection method was appropriate.
has super-classes
RDM-Activity c

Ensure data integrityc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#EnsureDataIntegrity

Ensure data integrity. Ensure that the data is unaltered. Dies bedeutet, dass die Daten in ihrer ursprünglichen Form erhalten bleiben und nicht nachträglich verändert werden.
has super-classes
RDM-Activity c

Ensure data reliabilityc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#EnsureDataReliability

Ensure data reliability. This means that the data was collected in the right way. It does not necessarily mean that the data is also correct.
has super-classes
RDM-Activity c

Ensure FAIRnessc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#EnsureFAIRness

Ensure FAIRness.
has super-classes
RDM-Activity c

Ensure reproducibilityc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#EnsureReproducibility

Ensure reproducibility.
has super-classes
RDM-Activity c

Ensure reusabilityc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#EnsureReusability

Ensure reusability
has super-classes
RDM-Activity c

Ensuring scientific integrityc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#EnsureScientificIntegrity

Ensure scientific integrity.
has super-classes
RDM-Activity c

Executionc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#Execution-Phase

The second of the three research project phases. Can only be started if the research proposal is accepted.
has super-classes
Phase c
is disjoint with
Project Completion c, Project Planning c

Findingc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#Finding

The result of one iteration of the finding level. It may be the result of one work package or the answer to one research question. It was generated by planning what should be found out, creating or reusing one or several artefacts, compiling them and hereby deriving new knowledge from this compilation. A finding is composed of networked artefacts, which are information. As a finding is semantically interconnected information, it is knowledge.
has super-classes
Creative Work c

Finding compilationc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#Finding-compilation

Compile a finding from artefacts. In this way, new knowledge is generated.
has super-classes
Step c

Finding-Levelc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#Finding-Level

The level on which findings are generated. It contains the steps plan approach to finding, create or reuse and finding compilation.
has super-classes
Level c

Formal Preparationc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#FormalPreparation

Second of the five publication process phases. Formal preparation includes all activities that relate to the formal framework conditions of the publication process and trigger corresponding planning.
has super-classes
Publications Process c

Generatec back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#Generate

In the generate task, new artefacts are brought into existence. This can happen by using existing artefacts or without them. New data is generated, gathered or gained by processing of existing artefacts. Due to the annotation of the data with metadata, meaning is provided, adding meaning to the data and therefore turning it into information.
has super-classes
Task c

Generation setupc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#Generation-Setup

The data generation setup happens immediately before the generate task. It is the planning and affirmation of the exact procedure of data generation. Furthermore, input artefacts are selected.
has super-classes
Task c

Implement criteria for (immediate) data deletionc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#ConsiderCriteriaForImmediateDataDeletion

Implement criteria for (immediate) data deletion.
has super-classes
RDM-Activity c

Implement criteria for selecting data for archivingc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#ExecuteDataSelectionCriteriaArchiving

Implement data selection criteria for archiving
has super-classes
RDM-Activity c

Implement criteria for selecting data for publicationc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#ExecuteDataSelectionCriteriaPublishing

Implement data selection criteria for publication
has super-classes
RDM-Activity c

Implement defined access processc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#ImplementAccessProcess

Implement defined access process.
has super-classes
RDM-Activity c

Levelc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#Level

The research process takes place on several levels. These differ in terms of the level of detail of the information that is collected, processed, and compiled.
has super-classes
B F O 0000015 c
has sub-classes
Artefact-Level c, Finding-Level c, Project-Level c

Make access conditions to research data transparentc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#MakeAccessConditionsTransparent

Make access conditions to research data transparent, e.g. through licenses.
has super-classes
RDM-Activity c

Metadata Aspectc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#MetadataAspect

All RDM activities of an RDM policy that fall under the aspect of metadata of data.
has super-classes
RDM-Policy c

Organisational Aspectc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#OrganisationalAspect

All RDM activities of an RDM policy that fall under the aspect of the organization of RDM.
has super-classes
RDM-Policy c

Phasec back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#Phase

A single main component of the research process. A phase is always separated from the other phases. A transition between phases can only occur if the previous phase has been successfully completed.
has super-classes
B F O 0000015 c
has sub-classes
Execution c, Project Completion c, Project Planning c

Plan approach to findingc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#Plan-approach-to-finding

When the supervisors trigger the investigation of a specific topic, a corresponding research question is either selected (if existent, e.g. in the proposal) or defined (if not existent yet). Additionally, needed sub-steps to answer the research question are defined.
has super-classes
Step c

Plan archiving infrastructurec back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#PlanArchivingInfrastructure

Plan archiving system or archiving infrastructure
has super-classes
RDM-Activity c

Plan backup strategyc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#PlanBackupStrategy

Plan backup strategy.
has super-classes
RDM-Activity c

Plan communicationc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#PlanCommunication

Plan communication of scientific results.
has super-classes
RDM-Activity c

Plan copyrights and rights of usec back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#PlanCopyrightAndUsageRights

Plan copyrights and rights of use for data to be published.
has super-classes
RDM-Activity c

Plan criteria for (immediate) data deletionc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#PlanCriteriaForImmediateDataDeletion

Plan criteria for (immediate) data deletion.
has super-classes
RDM-Activity c

Plan criteria for selecting data for archivingc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#PlanDataSelectionCriteriaArchiving

Plan criteria for selecting data for archiving
has super-classes
RDM-Activity c

Plan criteria for selecting data for publishingc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#PlanDataSelectionCriteriaPublication

Plan criteria for selecting data for publishing.
has super-classes
RDM-Activity c

Plan data formatsc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#PlanDataFormats

Planning the data formats to be used and generated in research.
has super-classes
RDM-Activity c

Plan data volumec back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#PlanDataVolume

Make an approximate estimate of the amount of data to be expected in the project.
has super-classes
RDM-Activity c

Plan economical use of resourcesc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#PlanEconomicalUseOfResources

Plan economical use of resources.
has super-classes
RDM-Activity c

Plan FAIRnessc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#PlanFAIRness

Planning the desired FAIRness in the project. In projects with a strong economic focus, FAIRness may be less important than confidentiality. In publicly funded projects, maximum FAIRness is usually sought.
has super-classes
RDM-Activity c

Plan licensesc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#PlanLicenses

Plan licensing of data and software.
has super-classes
RDM-Activity c

Plan long-term responsibilities for archivingc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#PlanLongTermResponsibilitiesForArchiving

Plan long-term responsibilities for archiving
has super-classes
RDM-Activity c

Plan required resources for archivingc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#PlanRequiredResourcesForArchiving

Plan required resources for archiving
has super-classes
RDM-Activity c

Plan resources for storagec back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#PlanRessourcesForStorage

Plan resources for storage.
has super-classes
RDM-Activity c

Plan retention period for datac back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#PlanRetentionPeriodForData

Plan retention period for data
has super-classes
RDM-Activity c

Planning Aspectc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#PlanningAspect

All RDM activities of an RDM policy that fall under the aspect of planning of RDM.
has super-classes
RDM-Policy c

Project Completionc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#Project-Completion-Phase

The last of the three research project phases. Can only be started if the execution phase is finished.
has super-classes
Phase c
is disjoint with
Execution c, Project Planning c

Project Planningc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#Project-Planning-Phase

The first of the three research project phases. The research project starts with this phase.
has super-classes
Phase c
is disjoint with
Execution c, Project Completion c

Project-Levelc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#Project-Level

The level on which projects are conducted. It contains the phases project planning, execution and project completion. It has a waterfall-like structure with distinct phases.
has super-classes
Level c

Publication Aspectc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#PublicationAspect

All RDM activities of an RDM policy that fall under the aspect of the publication of research data and research results.
has super-classes
RDM-Policy c

Publications Processc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#PublicationProcess

Independently running process that can start at any given stage of the research project. Its result is a publication that partly or fully contains the knowledge generated during the finding compilation. Publication process according to https://preprints.inggrid.org/repository/view/57/.
has super-classes
B F O 0000015 c
has sub-classes
Dissemination c, Editing c, Formal Preparation c, Submission c, Topic and Scoping c

Publish data documentationc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#PublishDataDocumentation

Publish data documentation.
has super-classes
RDM-Activity c

Publish metadatac back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#PublishMetadata

Publish research metadata. Increases the findability of data. This should also enable the findability of data without having to publish the data itself.
has super-classes
RDM-Activity c

Publish research datac back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#PublishResearchData

Publish research data.
has super-classes
RDM-Activity c

Quality Aspectc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#QualityAspect

All RDM activities of an RDM policy that fall under the aspect of data quality.
has super-classes
RDM-Policy c

RDM-Activityc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#RDMActivity

Specific RDM-action undertaken during RDM
has super-classes
Processing Step c
has sub-classes
Acquire funding for RDM c, Adhere to GWP c, Adhere to citation rules c, Adhere to export controls c, Adhere to licenses c, Adhere to patent law c, Allow Open Access for Data c, Allow Open Source for Software c, Anonymize data c, Archive unique/expensive data c, Clarify rights ownership c, Comply with retention periods c, Comply with the general legal framework c, Conduct anonymization c, Conduct archiving c, Conduct backup c, Conduct communication c, Conduct deletion of Data c, Conduct deletion of personal data c, Conduct ethical considerations c, Conduct long-term archiving c, Conduct publication c, Conduct storage c, Consider applicable codes of conduct c, Consider contractual framework conditions c, Consider domain-specific metadata standards c, Consider economic framework conditions c, Consider other university policies c, Consider professional standards c, Consider sensitive data c, Consider software as research data c, Convert Data To Formats For Archiving c, Create DMP c, Create README file c, Decide on the publication of data c, Define formal and substantive quality standards c, Definition of research data c, Determine liability c, Determine the start of planning c, Deviation from RDM-Specifications with other guidelines c, Document Archiving c, Document anonymization c, Document data analysis c, Document data collection c, Document data deletion c, Document data interpretation c, Document data processing c, Document embargo period c, Document reused data c, Document storage c, Document used tools c, Ensure FAIRness c, Ensure data accuracy c, Ensure data authenticity c, Ensure data completeness c, Ensure data correctness c, Ensure data integrity c, Ensure data reliability c, Ensure reproducibility c, Ensure reusability c, Ensuring scientific integrity c, Implement criteria for (immediate) data deletion c, Implement criteria for selecting data for archiving c, Implement criteria for selecting data for publication c, Implement defined access process c, Make access conditions to research data transparent c, Plan FAIRness c, Plan archiving infrastructure c, Plan backup strategy c, Plan communication c, Plan copyrights and rights of use c, Plan criteria for (immediate) data deletion c, Plan criteria for selecting data for archiving c, Plan criteria for selecting data for publishing c, Plan data formats c, Plan data volume c, Plan economical use of resources c, Plan licenses c, Plan long-term responsibilities for archiving c, Plan required resources for archiving c, Plan resources for storage c, Plan retention period for data c, Publish data documentation c, Publish metadata c, Publish research data c, Record metadata c, Select data for archiving c, Select data for reuse c, Select metadata standards/ontologies c, Select storage technology c, Set PID c, Set RDM responsibility c, Set access permissions during the project c, Set access rights c, Set copyrights and rights of use c, Set data formats for archiving c, Set embargo period c, Set legal responsibilities c, Set licence c, Set selection criteria for the defined storage c, Set storage location c, Specify publication medium c, Take confidentiality and secrecy into account c, Take copyright into account c, Take data protection into account c, Update DMP c, Use defined vocabulary c, Use ontology c

RDM-Guidelinec back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#RDM-Guideline

An unstructured FDM guideline (usually in the form of a document), which may contain specifications or recommendations for the FDM.
has super-classes
Creative Work c
is in domain of
Guideline Document U R L dp, is referenced by policy op
is in range of
refers to guideline op
has members
RWTH Aachen University RDM-Guideline ni

RDM-Policyc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#RDM-Policy

A structured FDM guideline, which may contain specifications or recommendations for the FDM.
has super-classes
Creative Work c
has sub-classes
Accessibility Aspect c, Archiving Aspect c, Data Minimisation Aspect c, Deletion Aspect c, Dissemination Aspect c, Documentation Aspect c, ELS Aspect c, Metadata Aspect c, Organisational Aspect c, Planning Aspect c, Publication Aspect c, Quality Aspect c, Reuse Aspect c, Storage Aspect c
is in domain of
refers to guideline op
is in range of
is referenced by policy op
has members
RWTH Aachen University RDM-Policy ni

Record metadatac back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#RecordMetadata

Record metadata
has super-classes
RDM-Activity c

Research Activityc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#ResearchActivity

Specific research-action undertaken during Research
has super-classes
Processing Step c

Reuse Aspectc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#ReuseAspect

All RDM activities of an RDM policy that fall under the aspect of data reuse.
has super-classes
RDM-Policy c

Select data for archivingc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#SelectDataForArchiving

Select data for archiving. In the case of large volumes, a justified selection must be made. For example, research data that forms the basis of a publication.
has super-classes
RDM-Activity c

Select data for reusec back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#SelectDataForReuse

Select external data for reuse in your own project.
has super-classes
RDM-Activity c

Select metadata standards/ontologiesc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#SelectMetadataStandardsOntologies

Select appropriate metadata standards or ontologies.
has super-classes
RDM-Activity c

Select storage technologyc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#SelectStorageTechnology

Select storage technology.
has super-classes
RDM-Activity c

Set access permissions during the projectc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#SetAccessPermissionsDuringProject

Set access permissions during the project.
has super-classes
RDM-Activity c

Set access rightsc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#SetAccessRightsForArchivedData

Define access rights for the archived data.
has super-classes
RDM-Activity c

Set copyrights and rights of usec back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#SetCopyrightAndUsageRights

Plan copyrights and rights of use for data to be published
has super-classes
RDM-Activity c

Set data formats for archivingc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#SetDataFormatsForArchiving

Set data formats for archiving.
has super-classes
RDM-Activity c

Set embargo periodc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#SetEmbargoPeriod

Set embargo period or blocking periods.
has super-classes
RDM-Activity c

Set legal responsibilitiesc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#SetLegalResponsibilities

Set legal responsibilities.
has super-classes
RDM-Activity c

Set licencec back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#SetLicence

Set licence, e.g. with the help of https://ufal.github.io/public-license-selector/ or https://tu-dresden.de/gsw/phil/irget/jfbimd13/ressourcen/dateien/dateien/DataJus/Entscheidungsbaum-DataJusPDFAA2.pdf?lang=de.
has super-classes
RDM-Activity c

Set PIDc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#SetPID

Assign persistent identifier (PID), e.g. DOI.
has super-classes
RDM-Activity c

Set RDM responsibilityc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#SetRDMResponsibility

Define RDM responsibilities, e.g. who is responsible for the documentation of data collection or who bears long-term responsibility.
has super-classes
RDM-Activity c

Set selection criteria for the defined storagec back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#SetSelectionCriteriaForDataToBeStoredInDefinedStorage

Set selection criteria for data to be stored in the defined storage.
has super-classes
RDM-Activity c

Set storage locationc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#SetStorageLocation

Set dedicated storage location for research data during the project.
has super-classes
RDM-Activity c

Specify publication mediumc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#SpecifyPublicationMedium

Specify publication medium.
has super-classes
RDM-Activity c

Stepc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#Step

Activity during the execution phase. This can be planning the approach to knowledge acquisition, generating or reusing artefacts, and compiling insights.
has super-classes
B F O 0000015 c
has sub-classes
Create or Reuse c, Finding compilation c, Plan approach to finding c

Storage Aspectc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#StorageAspect

All RDM activities of an RDM policy that fall under the aspect of data storage.
has super-classes
RDM-Policy c

Storec back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#Store

When the artefact was checked successfully, it can be stored. Ideally, it is stored in a way that project members can access it.
has super-classes
Task c

Submissionc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#Submission

This phase comprises the activities surrounding the submission of the publication, e.g. to the publisher. The core is the peer review, which ensures scientific quality.
has super-classes
Publications Process c

Take confidentiality and secrecy into accountc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#TakeConfidentialityAndSecrecyIntoAccount

Take confidentiality and secrecy into account.
has super-classes
RDM-Activity c

Take copyright into accountc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#TakeCopyrightIntoAccount

Take copyright into account.
has super-classes
RDM-Activity c

Take data protection into accountc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#DataProtection

Data protection, e.g. GDPR must be taken into account, especially when using personal data. Compliance with data protection regulations must be ensured.
has super-classes
RDM-Activity c

Taskc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#Task

Activity during the create or reuse step. This can include preparing the generation of artefacts, generating the artefacts themselves, reviewing the generated data, or storing them.
has super-classes
B F O 0000015 c
has sub-classes
Check c, Generate c, Generation setup c, Store c

Topic and Scopingc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#TopicAndScoping

This phase is triggered by either a self-motivated publication trigger or a externally motivated publication trigger. The availability of a finding is regardless of this crucial. In this phase, the content of the publication is determined.
has super-classes
Publications Process c

Update DMPc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#UpdateDMP

Updating a Data Management Plan (DMP) with the most recent information.
has super-classes
RDM-Activity c

Use defined vocabularyc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#UseDefinedVocabulary

Use defined vocabulary.
has super-classes
RDM-Activity c

Use ontologyc back to ToC or Class ToC

IRI: http://w3id.org/nfdi4ing/pro-research#UseOntology

Use ontology.
has super-classes
RDM-Activity c

Object Properties

followsop back to ToC or Object Property ToC

IRI: http://w3id.org/nfdi4ing/pro-research#follows

x follows y if and only if the time point at which x starts is after or equivalent to the time point at which y ends. Formally: x follows y iff ω(x) >= α(y), where α is a function that maps a process to a start point, and ω is a function that maps a process to an end point.

has characteristics: transitive

has sub-properties
immediately follows op

has activityop back to ToC or Object Property ToC

IRI: http://w3id.org/nfdi4ing/pro-research#hasActivity

X has the activity Y
has super-properties
top Object Property op
has sub-properties
has processing step op

has phaseop back to ToC or Object Property ToC

IRI: http://w3id.org/nfdi4ing/pro-research#has-phase

X has the phase Y
has super-properties
B F O 0000051 op

has processop back to ToC or Object Property ToC

IRI: http://w3id.org/nfdi4ing/pro-research#has-process

X has the process Y
has super-properties
B F O 0000051 op

has processing stepop back to ToC or Object Property ToC

IRI: http://w3id.org/nfdi4ing/pro-research#hasProcessingStep

X has the processing step Y
has super-properties
has activity op
has sub-properties
has RDM processing step op, has research processing step op

has RDM processing stepop back to ToC or Object Property ToC

IRI: http://w3id.org/nfdi4ing/pro-research#hasRDMActivity

X has the RDM processing step Y
has super-properties
has processing step op

has research processing stepop back to ToC or Object Property ToC

IRI: http://w3id.org/nfdi4ing/pro-research#hasResearchActivity

X has the research processing step Y
has super-properties
has processing step op

has resultop back to ToC or Object Property ToC

IRI: http://w3id.org/nfdi4ing/pro-research#hasResult

X has the result Y
is inverse of
is result of op

has taskop back to ToC or Object Property ToC

IRI: http://w3id.org/nfdi4ing/pro-research#has-task

X has the task Y
has super-properties
B F O 0000051 op

immediately followsop back to ToC or Object Property ToC

IRI: http://w3id.org/nfdi4ing/pro-research#immediately-follows

X immediately follows Y iff: start(X) simultaneous_with end(Y)

has characteristics: asymmetric, irreflexive

has super-properties
follows op

immediately precedesop back to ToC or Object Property ToC

IRI: http://w3id.org/nfdi4ing/pro-research#immediately-precedes

X immediately precedes Y iff: start(Y) simultaneous_with end(X)

has characteristics: asymmetric, irreflexive

has super-properties
precedes op

is referenced by policyop back to ToC or Object Property ToC

IRI: http://w3id.org/nfdi4ing/pro-research#isReferencedByPolicy

Indicates that an RDM guideline is referenced by an RDM policy.
has domain
RDM-Guideline c
has range
RDM-Policy c
is inverse of
refers to guideline op

is result ofop back to ToC or Object Property ToC

IRI: http://w3id.org/nfdi4ing/pro-research#isResultOf

X is the result of Y
is inverse of
has result op

part of processop back to ToC or Object Property ToC

IRI: http://w3id.org/nfdi4ing/pro-research#part-of-process

X is part of process Y
has super-properties
B F O 0000050 op

part of projectop back to ToC or Object Property ToC

IRI: http://w3id.org/nfdi4ing/pro-research#part-of-project

X is part of project Y
has super-properties
B F O 0000050 op

part of stepop back to ToC or Object Property ToC

IRI: http://w3id.org/nfdi4ing/pro-research#part-of-step

X is part of step Y
has super-properties
B F O 0000050 op

R O 0002090op back to ToC or Object Property ToC

IRI: http://purl.obolibrary.org/obo/RO_0002090

refers to guidelineop back to ToC or Object Property ToC

IRI: http://w3id.org/nfdi4ing/pro-research#refersToGuideline

has domain
RDM-Policy c
has range
RDM-Guideline c
is inverse of
is referenced by policy op
is also defined as
annotation property

represented byop back to ToC or Object Property ToC

IRI: http://w3id.org/nfdi4ing/pro-research#represented_by

A is represented by B if B serves as a sign, symbol or model of A
has super-properties
S I O 000628 op

Data Properties

Guideline Document U R Ldp back to ToC or Data Property ToC

IRI: http://w3id.org/nfdi4ing/pro-research#GuidelineDocumentURL

has super-properties
url dp
has domain
RDM-Guideline c
has range
any U R I

is project-relateddp back to ToC or Data Property ToC

IRI: http://w3id.org/nfdi4ing/pro-research#isProjectRelated

If true, X is a specific expression as part of a project rather than a general rule.

has characteristics: functional

has range
boolean

Named Individuals

0000 0002 8021 5524ni back to ToC or Named Individual ToC

IRI: https://orcid.org/0000-0002-8021-5524

belongs to
Person c
has facts
name ap "Tobias Hamann"
affiliation ap 04xfq0f34 ep

RWTH Aachen University RDM-Guidelineni back to ToC or Named Individual ToC

IRI: http://w3id.org/nfdi4ing/pro-research#RWTH_Aachen_Research_Data_Management_Guidelines

belongs to
RDM-Guideline c
has facts
is referenced by policy op RWTH Aachen University RDM-Policy ni
Guideline Document U R L dp https://www.rwth-aachen.de/global/show_document.asp?id=aaaaaaaacsciovn
pref Label ap "RWTH Aachen University RDM-Guideline"@en

RWTH Aachen University RDM-Policyni back to ToC or Named Individual ToC

IRI: http://w3id.org/nfdi4ing/pro-research#RWTH_Aachen_Research_Data_Policy

belongs to
RDM-Policy c
has facts
refers to guideline op RWTH Aachen University RDM-Guideline ni
is project-related dp "false"^^boolean
pref Label ap "RWTH Aachen University RDM-Policy"@en

Legend back to ToC

c: Classes
op: Object Properties
dp: Data Properties
ni: Named Individuals
ep: External Properties

References back to ToC

# References #### 1 T. Hamann, M. Robrecht, M. A. Galdino, A. Abdelrazeq, and H. R. Schmitt, "PRO Research Process 4Ing: Project- and RDM-Oriented Research Process for Engineering Sciences: Validation of a Newly Prosed Process to Combine Data Life Cycles andProject-Oriented Research Processes in Engineering Science," ing.grid preprints, 2025. [Online]. Available: https://preprints.inggrid.org/repository/view/57/ ##### 2 D. Iglezakis et al., "Metadata4Ing: An ontology for describing the generation of research data within a scientific activity," 2025. Available: http://w3id.org/nfdi4ing/metadata4ing/1.3.1/ ##### 3 Qualitätsmanagementsysteme: Grundlagen und Begriffe (ISO 9000:2015), 9000, DIN Deutsches Institut für Normung e. V., Berlin, Sep. 2015. [Online]. Available: https://nautos.de/7TE/search/item-detail/DE30062915 Reused Ontologies: * m4i = [metadata4ing](http://w3id.org/nfdi4ing/metadata4ing/1.3.1/) * BIBO = [Bibliographic Ontology](https://www.dublincore.org/specifications/bibo/) * BIRO = [Bibliographic Reference Ontology](http://purl.org/spar/biro) * CR = [Croissant](http://mlcommons.org/croissant/) * DCAT = [Data Catalog](http://www.w3.org/ns/dcat) * DCC = [Digital Calibration Certificate](https://ptb.de/dcc/) * DCTERMS = [Dublin Core Terms](http://purl.org/dc/terms/) * EMMO = [European Materials and Modelling Ontology](http://emmo.info/emmo) * FOAF = [Friend of a Friend](http://xmlns.com/foaf/0.1/) * OBO = Open Biological and Biomedical Ontologies: * BFO = [Basic Formal Ontology](https://basic-formal-ontology.org/) * RO = [Relation Ontology](https://obofoundry.org/ontology/ro.html) * OWL = [Web Ontology Language](https://www.w3.org/TR/owl-overview/) * PIMS-II = [PIMS Interoperability Infrastructure](http://www.molmod.info/semantics/pims-ii.ttl) * PROV = [Provenance Namespace](https://www.w3.org/TR/2013/REC-prov-o-20130430/) * QUDT = [Quantities, Units, Dimensions and Types](http://www.qudt.org/2.1/catalog/qudt-catalog.html) * RDF = [Resource Description Framework](https://www.w3.org/TR/rdf11-concepts/) * RDFS = [RDF Schema](https://www.w3.org/TR/rdf-schema/) * SCHEMA = [schema.org](https://schema.org/) * SIO = [Semanticscience Integrated Ontology](http://semanticscience.org/resource/) * SIRP = [SI Reference Point](http://si-digital-framework.org/SI#) * SIS = [Digital System of Units Ontology](https://ptb.de/sis/) * SIX = [Digital System of Units Schema](https://ptb.de/si/) * SKOS = [Simple Knowledge Organization System](https://www.w3.org/TR/skos-reference/) * SSN = [Semantic Sensor Network Ontology](https://www.w3.org/TR/vocab-ssn/) * VANN = [Vocabulary for Annotating vocabulary descriptions](https://vocab.org/vann/) * XSD = [XML Schema Definition](https://www.w3.org/TR/xmlschema11-1/)

Acknowledgments back to ToC

The author would like to thank the [m4i](https://nfdi4ing.pages.rwth-aachen.de/metadata4ing/metadata4ing/) team for developing the m4i ontology on which this ontology builds upon. The author would like to thank [Dorothea Iglezakis](https://orcid.org/0000-0002-8524-0569) for helping out with questions during development. The author would like to thank [Silvio Peroni](http://www.essepuntato.it/) for developing [LODE](http://www.essepuntato.it/lode), a Live OWL Documentation Environment, which is used for representing the Cross Referencing Section of this document and [Daniel Garijo](https://w3id.org/people/dgarijo) for developing [Widoco](https://github.com/dgarijo/Widoco), the program used to create the template used in this documentation. The author would like to thank the Federal Government and the Heads of Government of the Länder, as well as the Joint Science Conference (GWK), for their funding and support within the framework of the [NFDI4ING consortium](https://nfdi4ing.de), which was funded by the [German Research Foundation](https://www.dfg.de/) (DFG) under the project number [442146713](https://gepris.dfg.de/gepris/projekt/442146713).