Skip to content
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
85 lines (76 sloc) 4.69 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_F1A a fair:FAIR-Metric ;
foaf:primaryTopic fair:F1 .
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 "Identifier Uniqueness" ;
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 """Ontology
- Gene Ontology: datatypes/MIR:00000022
- HISCO: [link]
This resource has not described or registered their identifier scheme. A recommended course of action would be to XXX.
Model/format - RDFS:
- JWS Online:
- ArrayExpress:
-> FAIRsharing will implement the FAIR Metric specification to provide a machine-readable link to the MIRIAM repository (for life science content)
- smartAPI's API
--> the smartAPI repository will provide accessible specification of the identifier scheme that is embedded in that metadata document.
--> the web site will have to provide a machine-readable pointer to the official DOI specification.
""" ;
fm:measuring "Whether there is a scheme to uniquely identify the digital resource." ;
fm:procedure """An identifier scheme is valid if and only if it is described in a repository that can register and present such identifier schemes (e.g.
Information about the identifier scheme must be presented with a machine-readable document containing the FM1 attribute with the URL to where the scheme is described. see specification for implementation.""" ;
fm:rationale "The uniqueness of an identifier is a necessary condition to unambiguously refer that resource, and that resource alone. Otherwise, an identifier shared by multiple resources will confound efforts to describe that resource, or to use the identifier to retrieve it. Examples of identifier schemes include, but are not limited to URN, IRI, DOI, Handle, trustyURI, LSID, etc. For an in-depth understanding of the issues around identifiers, please see" ;
fm:relevance "All" ;
fm:requirements "URL to a registered identifier scheme." ;
fm:validation "Present or Absent" .
sub:pubinfo {
this: dcterms:created "2017-11-20T00: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.