@prefix this: <https://w3id.org/fair/icc/np/A1.2-Explanation/RArg_clopv_e4aBuF6lFkQ94sQ4GsPQPBwC0fN6h1L73s> .
@prefix sub: <https://w3id.org/fair/icc/np/A1.2-Explanation/RArg_clopv_e4aBuF6lFkQ94sQ4GsPQPBwC0fN6h1L73s#> .
@prefix latest: <https://w3id.org/fair/icc/latest/A1.2-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_00029> rdfs:label "Brewster et al. 2019" .
  icc:A1.2-Explanation a icc:Explanation ;
    rdfs:comment "This principle clearly demonstrates that FAIR is not equal to ‘open’. Some digital resources, such as data that have access restrictions based on ethical, legal or contractual constraints, require additional measures to be accessed. This often pertains to assuring that the access requester is indeed that requester (authentication), that the requester’s profile and credentials match the access conditions of the resource (authorization), and that the intended use matches permitted use cases (e.g. non-commercial purposes only) (see also R1.1, where there are requirements to provide explicit documentation about who may use the data, and for what purposes). At the level of technical implementation, an additional authentication and authorization procedure must be specified, if it is not already defined by the protocol (see A1.1). A requester can be a human or a machine agent. In the latter case it is probably a proxy for a human or an organization to which the authentication and authorization protocol should be applied, in which case, the machine should be expected to present the appropriate credentials. The principle requires that a FAIR resource must provide such a protocol, but the protocol itself is not further specified. In practice, an Internet of FAIR Data and Services cannot function without implementing Authentication and Authorization Infrastructure (AAI, see also https://doi.org/10.1162/dint_a_00029)." ;
    rdfs:isDefinedBy latest: ;
    rdfs:label "A1.2 Explanation" ;
    rdfs:seeAlso <https://dash.harvard.edu/handle/1/4322580> , <https://doi.org/10.1162/dint_a_00029> ;
    icc:explains-principle fair:A1.2 ;
    icc:implementation-considerations "Current choices are for communities to choose protocols to use when controlling access of agents to meta(data). Preferably these should be as generic as possible and as domain specific as necessary. Attempts to harmonize AAI approaches are numerous, but not covered in this article." ;
    icc:implementation-examples "Again, the most common example of a compliant protocol is the HTTP protocol. Another example is the life science AAI protocol. Brewster et al. (https://doi.org/10.1162/dint_a_00029) describe an early implementation of an ontology-based approach to this challenge." .
  fair:A1.2 rdfs:label "A1.2" .
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.2-Explanation/RA3Hr_3Jus0_C0exBw9rFxwq7IzZvyPxYEzuUzkRpsOLo> .