@@ -4,9 +4,9 @@ Aus dem Abstract https://doi.org/10.5281/zenodo.4015201:
> "NFDI4Ing brings together the engineering communities and fosters the management of engineering research data. The consortium represents engineers from all walks of the profession. It offers a unique method-oriented and user-centred approach in order to make engineering research data FAIR – findable, accessible, interoperable, and re-usable."
Please click on  to join the discussion on the topics discussed in the sections!
Please click on  to join the discussion on the topics discussed in the sections!
## The Mission: [](https://git.rwth-aachen.de/nfdi4ing/mission-statement/-/issues/2)
## The Mission: [](https://git.rwth-aachen.de/nfdi4ing/mission-statement/-/issues/2)
NFDI4Ing builds the bridges
***to foster** quality-controlled measures for **research data management** in the engineering sciences by providing methodologies and services
...
...
@@ -19,27 +19,27 @@ NFDI4Ing builds the bridges
## NFDI4Ing is Guided by the Following Principles:
* all NFDI4Ing services are expected to be production-ready
***Practicability** and **feasibility**: [](https://git.rwth-aachen.de/nfdi4ing/mission-statement/-/issues/6)
***Practicability** and **feasibility**: [](https://git.rwth-aachen.de/nfdi4ing/mission-statement/-/issues/6)
* in all scales of organizational structures (from single scientists up to international organizations)
Based on New European Interoperability Framework, https://dx.doi.org/10.2799/78681
...
...
@@ -53,7 +53,7 @@ a. Linked Data and Research Object models (W3C RDF, OWL)
b. Microservice architecture (e.g. REST, SOAP)
c. Scientific workflows
### Problems and Needs [](https://git.rwth-aachen.de/nfdi4ing/mission-statement/-/issues/10)
### Problems and Needs [](https://git.rwth-aachen.de/nfdi4ing/mission-statement/-/issues/10)
At the level of technical interoperability, some of the usual problems should be considered:
...
...
@@ -70,7 +70,7 @@ As a result of this analysis, these are some of the needs that can be identified
* When searching for research data (or other research objects) that may be reusable across communities, such data may need to be discovered at different levels of granularity: high level / coarse-grained.
* There is a need to have a common and well-understood PID policy across communities.
Some of the recommendations that can be made in this respect are:
...
...
@@ -82,7 +82,7 @@ Some of the recommendations that can be made in this respect are:
* Make coarse-grained and fine-grained dataset (and other research object) search tools available. Consider a range of general-purpose and domain-specific/specialised search tools, exploiting general-purpose and domain-specific metadata.
* Create a clear NFDI4Ing PID policy, accommodating an appropriate PID usage, recognising that established practises are at different levels of maturity for different resources and new PID types may emerge.
Semantic interoperability can be defined as "the ability of computer systems to transmit data with unambiguous, shared meaning. Semantic interoperability is a requirement to enable machine computable logic, inferencing, knowledge discovery, and data federation between information systems". (FAIRsFAIR deliverable D2.1 Report on FAIR requirements for persistence and interoperability 2019. https://zenodo.org/record/3557381)
...
...
@@ -90,7 +90,7 @@ That is, semantic interoperability is achieved when the information transferred
Semantic interoperability is established by shared semantic artefacts (ontologies, thesauri) across the communities, which allow homogenising the interpretation and treatment of the exchanged data, and all of its associated resources.
### Problems and Needs [](https://git.rwth-aachen.de/nfdi4ing/mission-statement/-/issues/13)
### Problems and Needs [](https://git.rwth-aachen.de/nfdi4ing/mission-statement/-/issues/13)
At the level of semantic interoperability, some of the usual problems should be considered:
...
...
@@ -107,7 +107,7 @@ As a result of this analysis, these are some of the needs that can be identified
* Need for harmonisation across disciplines or types of data. It should be possible for a user of one community to add metadata to existing items (data and semantic artefacts) according to their own research discipline practices (e.g. a social scientist can add DDI-based metadata for a dataset coming from an environmental scientist). Allow a researcher from a discipline to transform metadata (or data) from one discipline's format/annotations to another.
* Need for federated access over existing research data repositories (both inside a discipline and across disciplines). How to support discovery of data on the basis of a high-level description, and possibly also on more details like concepts related to observations and variables?
