Skip to content
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
79 lines (70 sloc) 4.4 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_I2 a fair:FAIR-Metric ;
foaf:primaryTopic fair:I2 .
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 "Use FAIR Vocabularies" ;
rdfs:comment "FAIR Metric for Fair Principle I2" ;
dcat:distribution sub:_1 , sub:_2 ;
prov:wasGeneratedBy "FAIR Metrics Working Group" ;
fm:comments """michel: there must be a syntax and associated semantics for that language. This is sufficient
mark: there needs to be some identity or denotation in the language; ('vanilla') xml and json are not FAIR, so should fail this test
*** can you (i) identify elements and (ii) make statements about them, and iii) is there a formally defined interpretation for that -> HTML fails; PDF fails
-> that there are many users of the language
. acknowledged within your community
-> hard to prove.
. could we use google to query for your filetype (can't discriminate between different models)
-> has a media type
--> This SHOULD be stated as a IANA code [IANA-MT]
standardization of at least this listing process is a good measure of 'sharedness'
broadly applicable
. that the language is extensible to a domain of interest
. you can define your own elements in accordance with the semantics of the language
gff3 is not in the IANA list -> what steps would the community need to execute to be listed here? cases like GFF, PDB are not broadly applicable
biopax -> is defined vnd.biopax.rdf+xml and built on rdf -> allows users to create new elements and relate them
jpg -> widely used, registered, but primarily for image content
pdf -> registered, enables users to create their own dictionary.
""" ;
fm:examples "None" ;
fm:measuring "The metadata values and qualified relations should themselves be FAIR, for example, terms from open, community-accepted vocabularies published in an appropriate knowledge-exchange format." ;
fm:procedure "Resolve IRIs, check FAIRness of the returned document(s)." ;
fm:rationale "It is not possible to unambiguously interpret metadata represented as simple keywords or other non-qualified symbols. For interoperability, it must be possible to identify data that can be integrated like-with-like. This requires that the data, and the provenance descriptors of the data, should (where reasonable) use vocabularies and terminologies that are, themselves, FAIR." ;
fm:relevance "All" ;
fm:requirements "IRIs representing the vocabularies used for (meta)data " ;
fm:validation "Successful resolution; document is amenable to machine-parsing and identification of terms within it. It may be possible to use FAIRSharing to validate these vocabularies." .
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.