Skip to content

Commit ce0fd89

Browse files
author
markwilkinson
committed
data identifier metric authored. others fixed or deleted if redundant
1 parent 0b9dedd commit ce0fd89

8 files changed

Lines changed: 137 additions & 315 deletions

docs/metric/general/FM_F1_M_IdentUnique.ttl

Lines changed: 25 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -19,11 +19,31 @@
1919
vivo:abbreviation "FM_F1_M_IdentUnique" ;
2020
dcat:landingPage <https://w3id.org/fair-metrics/general/FM_F1_M_IdentUnique> ;
2121

22-
dcterms:description """<p>This metric evaluates whether the identifier provided as input satisfies the EOSC-PID aligned [FAIRsharing definition](<a href="https://fairsharing.gitbook.io/fairsharing/record-sections-and-fields/general-information/globally-unique-persistent-and-resolvable-identifier-schemas)">https://fairsharing.gitbook.io/fairsharing/record-sections-and-fields/general-information/globally-unique-persistent-and-resolvable-identifier-schemas)</a> of resolvability.</p>
23-
24-
<p>F1 requires that metadata be assigned a globally unique, persistent and resolvable identifier. This metric is particularly concerned with the resolvability aspect of GUPRIs. For this metric, there must also be a known machine-actionable resolution protocol for the identifier. Although resolvability is not explicitly mentioned in the original Nature paper on the FAIR Principles, due to the relationship among global uniqueness, persistence and resolvability, please note that the [GO FAIR Foundation states](<a href="https://www.gofair.foundation/f1)">https://www.gofair.foundation/f1)</a> that FAIR implementations should require all three aspects. As such, some aspects of this metric overlap with FAIR A1. Resolvability is required so that identifiers are actionable for both humans and machines. In this metric, the definition of persistence follows the [FAIRsharing guidance](<a href="https://fairsharing.gitbook.io/fairsharing/record-sections-and-fields/general-information/globally-unique-persistent-and-resolvable-identifier-schemas)">https://fairsharing.gitbook.io/fairsharing/record-sections-and-fields/general-information/globally-unique-persistent-and-resolvable-identifier-schemas)</a> on Globally Unique, Persistent and Resolvable Identifier (GUPRI) schemas. This definition requires that humans and machines must be able to use the identifier to access information on the digital object. To make it globally resolvable as per the EOSC PID definition, it further needs to be part of a namespace defined by a syntax that is controlled by an Authority. There should be an established tombstoning or equivalent procedure. This metric evaluates whether the identifier provided as input satisfies the FAIRsharing definition of resolvability. The evaluation assesses whether the identifier schema supports the community definition provided by FAIRsharing.</p>
25-
26-
<p>For an in-depth understanding of the issues around identifiers, please see http://dx.plos.org/10.1371/journal.pbio.2001414">http://dx.plos.org/10.1371/journal.pbio.2001414
22+
dcterms:description """This metric evaluates whether the identifier provided as input
23+
satisfies the EOSC-PID aligned FAIRsharing definition of global uniqueness.
24+
<p/>Why should we measure it?
25+
<p/>FAIR Principle F1 requires that metadata be assigned a globally unique,
26+
persistent and resolvable identifier. This metric is particularly concerned
27+
with the globally uniqueness aspect of GUPRIs;
28+
global uniqueness is required to prevent identifier collision across institutions,
29+
systems and domains. Otherwise, an identifier shared by multiple resources
30+
will confound efforts to describe that resource, or to use the identifier to
31+
retrieve it. In this metric, the definition of global uniqueness follows
32+
the FAIRsharing guidance on Globally Unique,
33+
Persistent and Resolvable Identifier (GUPRI) schemas.
34+
This guidance requires that the identifier schema must use a
35+
controlled syntax/namespaces to avoid clashes; such syntax/namespaces must be
36+
governed by clearly defined Authorities. If there is any way the identifier
37+
could be created as part of another identifier system (e.g. if it
38+
is a structured series of alphanumeric characters such as P12345 (UniProt Accession Number)
39+
that could theoretically be used for other identifiers)
40+
then it is not globally unique. To fulfil this requirement in practice,
41+
it generally (but not always) requires a URL prefix of some kind.
42+
This metric evaluates whether the identifier provided as input
43+
satisfies the FAIRsharing definition of global uniqueness. The
44+
evaluation assesses whether the identifier schema operates
45+
within a governed namespace that prevents external collision
46+
and ensures unambiguous interpretation beyond the local database context.
2747
""" ;
2848
dcat:keyword "FAIR", "F1", "identifier", "metadata" ;
2949
dqv:inDimension <https://doi.org/10.25504/FAIRsharing.a2cea7> ;
Lines changed: 84 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,84 @@
1+
@prefix vcard: <http://www.w3.org/2006/vcard/ns#> .
2+
@prefix ftr: <https://w3id.org/ftr#> .
3+
@prefix dcterms: <http://purl.org/dc/terms/> .
4+
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
5+
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
6+
@prefix dcat: <http://www.w3.org/ns/dcat#> .
7+
@prefix dpv: <https://w3id.org/dpv#> .
8+
@prefix schema: <https://schema.org/> .
9+
@prefix vivo: <http://vivoweb.org/ontology/core#> .
10+
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
11+
@prefix dqv: <http://www.w3.org/ns/dqv#> .
12+
13+
<https://w3id.org/fair-metrics/general/FM_F3_M_DataIdent>
14+
a ftr:Metric, dcat:Dataset ;
15+
rdfs:isDefinedBy <https://fairmetrics.github.io/Metrics/metric/general/FM_F3_M_DataIdent.ttl> ;
16+
17+
ftr:identifier "https://w3id.org/fair-metrics/general/FM_F3_M_DataIdent"^^xsd:anyURI ;
18+
dcterms:title "FAIR Metric - F3 - Metadata - includes its own identifier" ;
19+
vivo:abbreviation "FM_F3_M_DataIdent" ;
20+
dcat:landingPage <https://w3id.org/fair-metrics/general/FM_F3_M_DataIdent> ;
21+
22+
dcterms:description """<p>This metric evaluates whether the metadata record explicitly includes the
23+
identifier of the research object(s) it describes.
24+
<p><p>
25+
F3 requires that metadata include the identifier(s) of the research object(s) it describes.
26+
To align with FAIR, if a metadata record is separated from its associated research object
27+
(which is common in harvesting and indexing), the connection between them must be
28+
explicitly preserved. This metric is concerned with the explicit linkage aspect
29+
of FAIR; F3 ensures that a machine-actionable relationship exists, allowing
30+
harvesters to unambiguously navigate from a descriptive metadata record
31+
back to the research object itself. Because many research objects cannot be
32+
arbitrarily extended to include references to their metadata, in many cases the
33+
only means to discover the metadata related to a research object will be
34+
to search based on the identifier of the research object itself.
35+
<p><p>
36+
While Principle F1 focuses on the qualities of the identifier schema
37+
being used (globally unique, persistent and resolvable), Principle F3
38+
relates to the linkage aspects of the research object identifier. It does not
39+
mandate that the identifier of the research object within the metadata record
40+
be immediately resolvable; rather, it requires that the identifier is present,
41+
and formally structured so that the relationship can be maintained and
42+
indexed by automated services.
43+
<p><p>
44+
The discovery of a research object should be possible
45+
from its metadata. For this to happen, the metadata must explicitly
46+
contain the identifier for the digital resource it describes, and this
47+
should be present in the form of a qualified reference. This metric
48+
evaluates whether the identifier provided as input resolves to
49+
metadata that contains a research object identifier. Further,
50+
that research object identifier must be distinguished
51+
from the numerous other fields and values that will be present in the metadata.
52+
""" ;
53+
dcat:keyword "FAIR", "F3", "identifier", "metadata" ;
54+
dqv:inDimension <https://doi.org/10.25504/FAIRsharing.820324> ;
55+
dcat:landingPage <https://w3id.org/fair-metrics/general/FM_F3_M_DataIdent> ;
56+
57+
58+
dcat:contactPoint [
59+
a vcard:Individual ;
60+
vcard:fn "Allyson L. Lister" ;
61+
vivo:orcidId <http://orcid.org/0000-0002-7702-4495> ;
62+
vcard:hasEmail <mailto:allyson.lister@oerc.ox.ac.uk> ;
63+
] ;
64+
65+
dcat:contactPoint [
66+
a vcard:Individual ;
67+
vcard:fn "Mark D. Wilkinson" ;
68+
vcard:organization-name "Wilkinson Laboratory, UPM, Madrid";
69+
vcard:hasEmail <mailto:mark.wilkinson@upm.es> ;
70+
] ;
71+
72+
ftr:status "Active"@en ;
73+
dcterms:issued "2026-05-13"^^xsd:date ;
74+
dcterms:modified "2026-05-13"^^xsd:date ;
75+
76+
dcat:version "Champion1.0" ;
77+
78+
ftr:applicationArea <http://www.fairsharing.org/ontology/subject/SRAO_0000401> ;
79+
dcterms:license <https://creativecommons.org/licenses/by/4.0/> ;
80+
81+
82+
ftr:supportedBy <https://w3id.org/FAIR-Champion> ;
83+
dpv:isApplicableFor schema:CreativeWork .
84+

docs/metric/general/FM_F3_M_MetaIdent.ttl

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ dqv:inDimension <https://doi.org/10.25504/FAIRsharing.820324> ;
5252
ftr:applicationArea <http://www.fairsharing.org/ontology/subject/SRAO_0000401> ;
5353
dcterms:license <https://creativecommons.org/licenses/by/4.0/> ;
5454

55-
ftr:hasPositiveValidation <https://doi.org/10.5281/zenodo.17901310(https://doi.org/10.5281/zenodo.17901310)> ;
55+
ftr:hasPositiveValidation <https://doi.org/10.5281/zenodo.17901310> ;
5656

5757
ftr:supportedBy <https://w3id.org/FAIR-Champion> ;
5858
dpv:isApplicableFor schema:CreativeWork .

docs/metric/general/FM_I2_M_FAIRVocabSemantic.jsonld

Lines changed: 0 additions & 94 deletions
This file was deleted.

docs/metric/general/FM_I2_M_FAIRVocabSemantic.ttl

Lines changed: 0 additions & 58 deletions
This file was deleted.

0 commit comments

Comments
 (0)