Skip to content
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
84 lines (74 sloc) 4.43 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_I1 a fair:FAIR-Metric ;
foaf:primaryTopic fair:I1 .
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 a Knowledge Representation Language" ;
rdfs:comment "FAIR Metric for Fair Principle I1" ;
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 "Use of a formal, accessible, shared, and broadly applicable language for knowledge representation." ;
fm:procedure """- The language must have a BNF (or other specification language)
- The URL resolves (accessible)
- The document has an IANA media-type (i.e. it is sufficiently widely-accepted and shared that it has been registered)
- The language can be arbitrarily extended (e.g. PDBml can be used to represent knowledge, but only about proteins)""" ;
fm:rationale "The unambiguous communication of knowledge and meaning (what symbols are, and how they relate to one another) necessitates the use of languages that are capable of representing these concepts in a machine-readable manner." ;
fm:relevance "All" ;
fm:requirements "URL to the specification of the language" ;
fm:validation """BNF (or other?) found, Media-type of the document is registered in FAIRSharing.
Future: FAIRSharing has tags to indicate constrained vs. extendable languages?""" .
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.