@prefix this: <https://w3id.org/fair/icc/np/F3-Explanation/RAIIlDCGrUvI6nbPP4gZ6I6QacqqXsiCd5gM90HWDb3D0> .
@prefix sub: <https://w3id.org/fair/icc/np/F3-Explanation/RAIIlDCGrUvI6nbPP4gZ6I6QacqqXsiCd5gM90HWDb3D0#> .
@prefix latest: <https://w3id.org/fair/icc/latest/F3-Explanation> .
@prefix icc: <https://w3id.org/fair/icc/terms/> .
@prefix fair: <https://w3id.org/fair/principles/terms/> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix dct: <http://purl.org/dc/terms/> .
@prefix pav: <http://purl.org/pav/> .
@prefix np: <http://www.nanopub.org/nschema#> .
@prefix orcid: <https://orcid.org/> .
sub:Head {
  this: np:hasAssertion sub:assertion ;
    np:hasProvenance sub:provenance ;
    np:hasPublicationInfo sub:pubinfo ;
    a np:Nanopublication .
sub:assertion {
  <https://doi.org/10.1162/dint_a_00031> rdfs:label "Thompson et al. 2019" .
  icc:F3-Explanation a icc:Explanation ;
    rdfs:comment "Principle F3 states that any description of a digital resource must contain the identifier of that resource being described. For instance, the description of a computational workflow, should explicitly contain the identifier for that workflow in a manner that is unambiguous. This is especially important where the resource and its metadata are stored independently, but persistently linked, which is generally considered good practice in FAIR. The purpose of this principle is twofold. First, it is perhaps trivial to say that a descriptor should explicitly say what object it is describing; however, there is a second, less-obvious reason for this principle. Many digital objects (such as workflows, as mentioned above) have well-defined structures that may disallow the addition of new fields, including fields that could point to the metadata about that digital object. Therefore, if you have one of these digital objects in-hand, the only way to discover its metadata is through a search using the identifier of that digital object. Thus, by requiring that a metadata descriptor contains the identifier of the thing being described, that identifier may then successfully be used as the search term to discover its metadata record." ;
    rdfs:isDefinedBy latest: ;
    rdfs:label "Explanation of FAIR principle F3" ;
    rdfs:seeAlso <https://doi.org/10.1162/dint_a_00031> , <https://www.w3.org/TR/vocab-dcat/> ;
    icc:explains-principle fair:F3 ;
    icc:implementation-considerations "It is a challenge to each community to choose a machine-actionable metadata model that explicitly links a resource and its metadata." ;
    icc:implementation-examples "An example of a technology that provides this link is FAIR Data Point (doi:10.1162/dint_a_00031), which is based on the Data Catalogue model (DCAT, https://www.w3.org/TR/vocab-dcat/) that provides not only unique identifiers for potentially multiple layers of metadata, but also provides a single, predictable, and searchable path through these layers of descriptors, down to the data object itself." .
  fair:F3 rdfs:label "F3" .
  <https://www.w3.org/TR/vocab-dcat/> rdfs:label "Data Catalogue model (DCAT)" .
sub:provenance {
  sub:assertion pav:authoredBy icc:FAIR-Principles-Explained-Working-Group .
sub:pubinfo {
  this: dct:created "2019-11-22T18:41:24.945+01:00"^^xsd:dateTime ;
    dct:creator orcid:0000-0001-8888-635X , orcid:0000-0002-1267-0234 , orcid:0000-0003-4818-2360 ;
    dct:license <https://creativecommons.org/publicdomain/zero/1.0/> .