@prefix this: <https://w3id.org/fair/icc/np/A1-Explanation/RAPc_iF-f961V2yRDHAZ5oDqM9-1G6d6t2lLcz3jeosjE> .
@prefix sub: <https://w3id.org/fair/icc/np/A1-Explanation/RAPc_iF-f961V2yRDHAZ5oDqM9-1G6d6t2lLcz3jeosjE#> .
@prefix latest: <https://w3id.org/fair/icc/latest/A1-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 {
  icc:A1-Explanation a icc:Explanation ;
    rdfs:comment "A primary purpose of identifying a digital resource is to simultaneously provide the ability to retrieve the record of that digital resource, in some format, using some clearly-defined mechanism: hence the retrievability is a facet of FAIR Accessibility. Here, the emphasis is on 'ability': there should be no additional barrier retrieval of the record by some agent when its access protocol (A1.1) results in permitted access to that record. Note that the agent may be a machine working behind a firewall, if that agent has been permitted access. For fully mechanized access, this requires that the identifier (F1) follows a globally-accepted schema that is tied to a standardized, high-level communication protocol. The 'standardized communication protocol' is critical here. Its purpose is to provide a predictable way for an agent to access a resource, regardless of whether unrestricted access to the content of the resource is granted or not." ;
    rdfs:isDefinedBy latest: ;
    rdfs:label "A1 Explanation" ;
    rdfs:seeAlso icc:A1.1-Explanation , icc:A1.2-Explanation , <https://www.w3.org/Protocols/> ;
    icc:explains-principle fair:A1 ;
    icc:implementation-examples "An example of a standardized access protocol is the Hypertext Transfer Protocol (HTTP1); however, FAIR does not preclude non-mechanized access protocols, such as a verbal request to the data holder in the case of highly sensitive data, so long as the access protocol is explicit and clearly defined. Conditions of compliance are further specified in sub-principles A1.1 and A1.2." .
  fair:A1 rdfs:label "A1" .
  <https://www.w3.org/Protocols/> rdfs:label "HTTP - Hypertext Transfer Protocol" .
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/A1-Explanation/RAheXRabbcfujKMIKQdbsWyRitg3Z0qV9Y-_yYa5R_6UI> .