Skip to content
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
69 lines (59 sloc) 3.93 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_I3 a fair:FAIR-Metric ;
foaf:primaryTopic fair:I3 .
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 Qualified References" ;
rdfs:comment "FAIR Metric for Fair Principle I3" ;
dcat:distribution sub:_1 , sub:_2 ;
prov:wasGeneratedBy "FAIR Metrics Working Group" ;
fm:comments "None" ;
fm:examples "None" ;
fm:measuring "Relationships within (meta)data, and between local and third-party data, have explicit and 'useful' semantic meaning" ;
fm:procedure """The linksets must have qualified references
At least one of the links must be in a different Web domain (or the equivalent of a different namespace for non-URI identifiers)""" ;
fm:rationale """One of the reasons that HTML is not suitable for machine-readable knowledge representation is that the hyperlinks between one document and another do not explain the nature of the relationship - it is 'unqualified'. For Interoperability, the relationships within and between data must be more semantically rich than 'is (somehow) related to'.
Numerous ontologies include richer relationships that can be used for this purpose, at various levels of domain-specificity. For example, the use of skos for terminologies (e.g. exact matches), or the use of SIO for genomics (e.g. 'has phenotype' for the relationship between a variant and its phenotypic consequences). The semantics of the relationship do not need to be 'strong' - for example, 'objectX wasFoundInTheSameBoxAs objectY' is an acceptable qualified reference
Similarly, dbxrefs must be predicated with a meaningful relationship what is the nature of the cross-reference?
Finally, data silos thwart interoperability. Thus, we should reasonably expect that some of the references/relations point outwards to other resources, owned by third-parties; this is one of the requirements for 5 star linked data.""" ;
fm:relevance "All" ;
fm:requirements "Linksets (in the formal sense) representing part or all of your resource" ;
fm:validation """- References are qualified
- Qualities are beyond 'Xref' or 'is related to'
- One of the cross-references points outwards to a distinct namespace
""" .
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.