@prefix this: <https://w3id.org/fair/icc/np/F1-Explanation/RAIz8InxR_p9Dh5-j3SI6MHT-6gHu7AGBuh_m6L56USSg> .
@prefix sub: <https://w3id.org/fair/icc/np/F1-Explanation/RAIz8InxR_p9Dh5-j3SI6MHT-6gHu7AGBuh_m6L56USSg#> .
@prefix latest: <https://w3id.org/fair/icc/latest/F1-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/> .
@prefix dbpedia: <http://dbpedia.org/resource/> .
sub:Head {
  this: np:hasAssertion sub:assertion ;
    np:hasProvenance sub:provenance ;
    np:hasPublicationInfo sub:pubinfo ;
    a np:Nanopublication .
}
sub:assertion {
  dbpedia:Digital_object_identifier rdfs:label "Digital object identifier" .
  <https://doi.org/10.1371/journal.pbio.2001414> rdfs:label "McMurry et al. 2017" .
  <https://doi.org/10.5281/zenodo.3267434> rdfs:label "Juty et al. 2019" .
  icc:F1-Explanation a icc:Explanation ;
    rdfs:comment "Principle F1 states that digital resources, i.e. data and metadata, must be assigned a globally unique and persistent identifier in order to be found and resolved by computers. This is the most fundamental of the FAIR principles, as globally unique and persistent identifiers are essential elements found in all of the other FAIR principles. Globally unique means that the identifier is guaranteed to unambiguously refer to exactly one resource in the world. Therefore, it is insufficient for it to be unique only locally (e.g. unique within a single, local database). Persistence refers to the requirement that this globally unique identifier is never reused in another context, and continues to identify the same resource, even if that resource no longer exists, or moves. In practice, this often involves using a third-party to generate an identifier that has guaranteed longevity and is project/organization-independent." ;
    rdfs:isDefinedBy latest: ;
    rdfs:label "Explanation of FAIR principle F1" ;
    rdfs:seeAlso dbpedia:Digital_object_identifier , <https://doi.org/10.1371/journal.pbio.2001414> , <https://doi.org/10.5281/zenodo.3267434> ;
    icc:explains-principle fair:F1 ;
    icc:implementation-considerations "Current challenges relate to ensuring the longevity of identifiers - in particular, that identifiers created by a project/community should survive the termination of the project or the dissolution of the community. Obtaining a persistent identifier, therefore, may require reliance on a third-party organization that promises longevity, and maintains these identifiers independently of the project/community. Current choices are for each community to choose, for all appropriate digital resources (i.e. data and metadata), identifier registration service(s) such as these that ensure global uniqueness and that also comply with the community-defined criteria for identifier persistence and resolvability." ;
    icc:implementation-examples "A common example of a useful identifier is the Digital Object Identifier (DOI) which is guaranteed by the DOI specification to be globally unique and persistent. DOIs provide an additional service, under principle A1, of being able to direct calls to the source data to the location of that data, even if the identified data moves. This ensures that identifiers are stable and valid beyond the project that generated them. In some circumstances, again with DOIs being an example, third-party persistent identifiers may also provide support for principle A2 (that metadata exists beyond the lifespan of the data) since these identifiers may still be responsive to Web calls, and be capable of providing metadata, even if the source resource is no longer active. For a discussion on identifiers see doi:10.1371/journal.pbio.2001414 and doi:10.5281/zenodo.3267434 ." .
  fair:F1 rdfs:label "F1" .
}
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/> ;
    <http://purl.org/nanopub/x/supersedes> <https://w3id.org/fair/icc/np/F1-Explanation/RA1HikSxbrsdMhHF5_TTqnKpd4eQ3RGoHDW-NL4JiPch8> .
}
https://np.petapico.org/RAIz8InxR_p9Dh5-j3SI6MHT-6gHu7AGBuh_m6L56USSg
np.petapico.org
CC-MAIN-2023-23
11164
application/http; msgtype=response
sha1:AGUMCU4INBKNN3J6HACKV2Y5ACNQCQ7X
<urn:uuid:59b3bb05-ce0a-438e-8548-808e93db5763>
2023-06-01T00:02:26Z
89.40.8.83
text/html
sha1:JONYYSXQYETFQDP6EP5IW5DSGFWROZS6
<urn:uuid:4932d484-147b-4290-8161-5c9bdb876bcc>
https://np.petapico.org/RAIz8InxR_p9Dh5-j3SI6MHT-6gHu7AGBuh_m6L56USSg
response
<urn:uuid:d4aa1a10-ec0c-45ba-8d07-ec419e21b7c7>
isPartOf: CC-MAIN-2023-23
publisher: Common Crawl
description: Wide crawl of the web for May/June 2023
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-77
software: Apache Nutch 1.19 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.4-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/