@prefix dcterms: .
@prefix dc: .
@prefix this: .
@prefix sub: .
@prefix metrics: .
@prefix np: .
@prefix pav: .
@prefix prov: .
@prefix rdfs: .
@prefix xsd: .
@prefix fair: .
@prefix foaf: .
@prefix dcat: .
@prefix fm: .
sub:Head {
this: np:hasAssertion sub:assertion;
np:hasProvenance sub:provenance;
np:hasPublicationInfo sub:pubinfo;
a np:Nanopublication .
}
sub:assertion {
metrics:FM_F1B a fair:FAIR-Metric;
foaf:primaryTopic fair:F1 .
}
sub:provenance {
sub:_1 dc:format "application/x-texinfo";
a , dcat:Distribution;
dcat:downloadURL .
sub:_2 dc:format "application/pdf";
a , dcat:Distribution;
dcat:downloadURL .
sub:assertion dcterms:author "Erik Schultes", "Luiz Bonino", "Mark Wilkinson", "Michel Dumontier",
"Peter Doorn", "Susanna Sansone";
dcterms:title "Identifier persistence";
rdfs:comment "FAIR Metric for Fair Principle F1";
dcat:distribution sub:_1, sub:_2;
prov:wasGeneratedBy "FAIR Metrics Working Group";
fm:comments """A first version of this metric would focus on just checking a URL that resolves to a document. We can't verify that document.
A second version would indicate how to structure the data policy document with a particular section (similar to how the CC licenses now have a formal structure in RDF).
A third version would insist that that document and section is signed by an approved organization and made available in an appropriate repository.""";
fm:examples """for each of the 'canonical' data types, examples, if available.
@todo
FAIR principles (scholarly publication in Nature Scientific Data)
\\verb|https://www.doi.org/overview/DOI_article_ELIS3.pdf|
http://www.nature.com/developers/
documentation/metadata-resources/doi/
FAIR Principles (computable representation):
https://github.com/FAIRDataInitiative/
\\verb|FAIR-principles#fair-principles|
For DSA-certified repositories (example below of 3TU-Datacentre at Delft) the identifier persistence policy is described in the self assessment:
https://assessment.datasealofapproval.org/
\\verb|assessment_187/seal/pdf/|
DOI Handbook - ensuring persistence:
\\verb|http://www.doi.org/doi_handbook/|
\\verb|6_Policies.html#6.5}|""";
fm:measuring "Whether there is a policy that describes what the provider will do in the event an identifier scheme becomes deprecated.";
fm:procedure "Use an HTTP GET on URL provided.";
fm:rationale "The change to an identifier scheme will have widespread implications for resource lookup, linking, and data sharing. Providers of digital resources must ensure that they have a policy to manage changes in their identifier scheme, with a specific emphasis on maintaining/redirecting previously generated identifiers.";
fm:relevance "All";
fm:requirements "A URL that resolves to a document containing the relevant policy.";
fm:validation "Present (a 200,202,203 or 206 HTTP response after resolving all and any prior redirects. e.g. 301 -> 302 -> 200 OK) or Absent (any other HTTP code)" .
}
sub:pubinfo {
this: dcterms:created "2017-11-20T00:00:00.0Z"^^xsd:dateTime;
dcterms:rights ;
dcterms:rightsHolder ;
pav:authoredBy "Mark Wilkinson", ;
pav:versionNumber "1" .
}