https://w3id.org/fair/icc/np/A1.2-Explanation/RArg_clopv_e4aBuF6lFkQ94sQ4GsPQPBwC0fN6h1L73s#Head
https://w3id.org/fair/icc/np/A1.2-Explanation/RArg_clopv_e4aBuF6lFkQ94sQ4GsPQPBwC0fN6h1L73s
http://www.nanopub.org/nschema#hasAssertion
https://w3id.org/fair/icc/np/A1.2-Explanation/RArg_clopv_e4aBuF6lFkQ94sQ4GsPQPBwC0fN6h1L73s#assertion
https://w3id.org/fair/icc/np/A1.2-Explanation/RArg_clopv_e4aBuF6lFkQ94sQ4GsPQPBwC0fN6h1L73s
http://www.nanopub.org/nschema#hasProvenance
https://w3id.org/fair/icc/np/A1.2-Explanation/RArg_clopv_e4aBuF6lFkQ94sQ4GsPQPBwC0fN6h1L73s#provenance
https://w3id.org/fair/icc/np/A1.2-Explanation/RArg_clopv_e4aBuF6lFkQ94sQ4GsPQPBwC0fN6h1L73s
http://www.nanopub.org/nschema#hasPublicationInfo
https://w3id.org/fair/icc/np/A1.2-Explanation/RArg_clopv_e4aBuF6lFkQ94sQ4GsPQPBwC0fN6h1L73s#pubinfo
https://w3id.org/fair/icc/np/A1.2-Explanation/RArg_clopv_e4aBuF6lFkQ94sQ4GsPQPBwC0fN6h1L73s
http://www.w3.org/1999/02/22-rdf-syntax-ns#type
http://www.nanopub.org/nschema#Nanopublication
https://w3id.org/fair/icc/np/A1.2-Explanation/RArg_clopv_e4aBuF6lFkQ94sQ4GsPQPBwC0fN6h1L73s#assertion
https://doi.org/10.1162/dint_a_00029
http://www.w3.org/2000/01/rdf-schema#label
Brewster et al. 2019
https://w3id.org/fair/icc/terms/A1.2-Explanation
http://www.w3.org/1999/02/22-rdf-syntax-ns#type
https://w3id.org/fair/icc/terms/Explanation
https://w3id.org/fair/icc/terms/A1.2-Explanation
http://www.w3.org/2000/01/rdf-schema#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).
https://w3id.org/fair/icc/terms/A1.2-Explanation
http://www.w3.org/2000/01/rdf-schema#isDefinedBy
https://w3id.org/fair/icc/latest/A1.2-Explanation
https://w3id.org/fair/icc/terms/A1.2-Explanation
http://www.w3.org/2000/01/rdf-schema#label
A1.2 Explanation
https://w3id.org/fair/icc/terms/A1.2-Explanation
http://www.w3.org/2000/01/rdf-schema#seeAlso
https://dash.harvard.edu/handle/1/4322580
https://w3id.org/fair/icc/terms/A1.2-Explanation
http://www.w3.org/2000/01/rdf-schema#seeAlso
https://doi.org/10.1162/dint_a_00029
https://w3id.org/fair/icc/terms/A1.2-Explanation
https://w3id.org/fair/icc/terms/explains-principle
https://w3id.org/fair/principles/terms/A1.2
https://w3id.org/fair/icc/terms/A1.2-Explanation
https://w3id.org/fair/icc/terms/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.
https://w3id.org/fair/icc/terms/A1.2-Explanation
https://w3id.org/fair/icc/terms/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.
https://w3id.org/fair/principles/terms/A1.2
http://www.w3.org/2000/01/rdf-schema#label
A1.2
https://w3id.org/fair/icc/np/A1.2-Explanation/RArg_clopv_e4aBuF6lFkQ94sQ4GsPQPBwC0fN6h1L73s#provenance
https://w3id.org/fair/icc/np/A1.2-Explanation/RArg_clopv_e4aBuF6lFkQ94sQ4GsPQPBwC0fN6h1L73s#assertion
http://purl.org/pav/authoredBy
https://w3id.org/fair/icc/terms/FAIR-Principles-Explained-Working-Group
https://w3id.org/fair/icc/np/A1.2-Explanation/RArg_clopv_e4aBuF6lFkQ94sQ4GsPQPBwC0fN6h1L73s#pubinfo
https://w3id.org/fair/icc/np/A1.2-Explanation/RArg_clopv_e4aBuF6lFkQ94sQ4GsPQPBwC0fN6h1L73s
http://purl.org/dc/terms/created
2019-11-22T18:41:24.945+01:00
https://w3id.org/fair/icc/np/A1.2-Explanation/RArg_clopv_e4aBuF6lFkQ94sQ4GsPQPBwC0fN6h1L73s
http://purl.org/dc/terms/creator
https://orcid.org/0000-0001-8888-635X
https://w3id.org/fair/icc/np/A1.2-Explanation/RArg_clopv_e4aBuF6lFkQ94sQ4GsPQPBwC0fN6h1L73s
http://purl.org/dc/terms/creator
https://orcid.org/0000-0002-1267-0234
https://w3id.org/fair/icc/np/A1.2-Explanation/RArg_clopv_e4aBuF6lFkQ94sQ4GsPQPBwC0fN6h1L73s
http://purl.org/dc/terms/creator
https://orcid.org/0000-0003-4818-2360
https://w3id.org/fair/icc/np/A1.2-Explanation/RArg_clopv_e4aBuF6lFkQ94sQ4GsPQPBwC0fN6h1L73s
http://purl.org/dc/terms/license
https://creativecommons.org/publicdomain/zero/1.0/
https://w3id.org/fair/icc/np/A1.2-Explanation/RArg_clopv_e4aBuF6lFkQ94sQ4GsPQPBwC0fN6h1L73s
http://purl.org/nanopub/x/supersedes
https://w3id.org/fair/icc/np/A1.2-Explanation/RA3Hr_3Jus0_C0exBw9rFxwq7IzZvyPxYEzuUzkRpsOLo