From ea33e69a26721330a92400c9a742a9c36f402df0 Mon Sep 17 00:00:00 2001 From: Daniel Garijo Date: Mon, 17 Feb 2025 19:20:45 +0100 Subject: [PATCH] removed weird space --- docs/architecture/fair_if.rst | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/architecture/fair_if.rst b/docs/architecture/fair_if.rst index 6773679..0cf682e 100644 --- a/docs/architecture/fair_if.rst +++ b/docs/architecture/fair_if.rst @@ -12,7 +12,6 @@ Guided by the Compliance Assessment Toolkit [1], we have identified the set of d Detailed definitions of these components are work in progress as we examine use-cases emerging from the participating Pilots, to ensure that the identified FAIRness Reference Model components are a) complete, and b) match the requirements of the FAIR-IF, and the overall expectations of the OSTrails IF. Briefly, here are the current definitions of the components. The three Conceptual-level components involved in the FAIR Reference Model are: - * Dimensions (using W3C Data Quality Vocabulary dqv:Dimension) - a high-level objective that should be met by digital objects corresponding to one of the FAIR Principles (e.g. R1.1. all digital objects should have a licence). * Metrics: Narrative description that a Test must wholly implement * Benchmarks: a narrative definition of how to interpret the Test Result Set resulting from the application of one or more Metrics to a digital object.