Skip to content
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
61 lines (53 sloc) 3.78 KB
@prefix this: <> .
@prefix sub: <> .
@prefix metrics: <> .
@prefix dcterms: <> .
@prefix dcelem: <> .
@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_R1.3 a fair:FAIR-Metric ;
foaf:primaryTopic fair:R1.3 .
sub:provenance {
sub:_1 dcelem:format "application/x-texinfo" ;
a <> , dcat:Distribution ;
dcat:downloadURL <> .
sub:_2 dcelem: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 "Meets Community Standards" ;
rdfs:comment "FAIR Metric for Fair Principle R1.3" ;
dcat:distribution sub:_1 , sub:_2 ;
prov:wasGeneratedBy "FAIR Metrics Working Group" ;
fm:comments """Such certification services may not exist, but this principle serves to encourage the community to create both the standard(s) and the verification services for those standards.
A potentially useful side-effect of this is that it might provide an opportunity for content-verification - e.g. the certification service provides a hash of the data, which can be used to validate that it has not been edited at a later date.""" ;
fm:examples "None" ;
fm:measuring "Certification, from a recognized body, of the resource meeting community standards." ;
fm:procedure "Validate the electronic signature as coming from a community authority (e.g. a verisign signature)" ;
fm:rationale "Various communities have recognized that maximizing the usability of their data requires them to adopt a set of guidelines for metadata (often in the form of 'minimal information about...' models). Non-compliance with these standards will often render a dataset 'reuseless' because critical information about its context or provenance is missing. However, adherence to community standards does more than just improve reusability of the data. The software used by the community for analysis and visualization often depends on the (meta)data having certain fields; thus, non-compliance with standards may result in the data being unreadable by its associated tools. As such, data should be (individually) certified as being compliant, likely through some automated process (e.g. submitting the data to the community's online validation service)" ;
fm:relevance "All" ;
fm:requirements "A certification saying that the resource is compliant" ;
fm:validation "Successful signature validation" .
sub:pubinfo {
this: dcterms:created "2017-11-21T00:00:00.0Z"^^xsd:dateTime ;
dcterms:rights <> ;
dcterms:rightsHolder <> ;
pav:authoredBy "Mark Wilkinson" , <> ;
pav:versionNumber "1" .
You can’t perform that action at this time.