@prefix this: . @prefix sub: . @prefix dbpedia: . @prefix latest: . @prefix icc: . @prefix fair: . @prefix rdfs: . @prefix xsd: . @prefix dct: . @prefix pav: . @prefix np: . @prefix orcid: . sub:Head { this: np:hasAssertion sub:assertion; np:hasProvenance sub:provenance; np:hasPublicationInfo sub:pubinfo; a np:Nanopublication . } sub:assertion { dbpedia:Hypertext_Transfer_Protocol rdfs:label "Hypertext Transfer Protocol" . rdfs:label "Suber 2008" . icc:A1.1-Explanation a icc:Explanation; rdfs:comment "The protocol (mechanism) by which a digital resource is accessed (e.g. queried) should not pose any bottleneck. It describes an access process, hence does not directly pertain to restrictions that apply to using the resource. The protocols underlying the World-Wide Web, such as HTTP, are an archetype for an open, free, and universally implementable protocol. Such protocols reduce the cost of gaining access to digital resources, because they are well defined and open and allow any individual to create their own standards-compliant implementation. That the use of the protocols is free ensures that those lacking monetary means can equitably access the resource. That it is universally implementable ensures that the technology is available to all (and not restricted, for instance, by country or a sub-community), thus encompassing both the \"gratis\" and \"libre\" meaning of \"free\" (https://dash.harvard.edu/handle/1/4322580)."; rdfs:isDefinedBy latest:; rdfs:label "A1.1 Explanation"; rdfs:seeAlso dbpedia:Hypertext_Transfer_Protocol, ; icc:explains-principle fair:A1.1; icc:implementation-considerations "Current challenges are to explicitly and fully document access protocols that are not open/free (for example, access only after personal contact) and make those protocols available as a clearly identified facet of the machine-readable metadata. Current choices are for communities to choose standardized communication protocols that are open, free and universally implementable. "; icc:implementation-examples "The most common example of a compliant protocol is the HTTP protocol that underlies the majority of Web traffic. It has additional useful features, including the ability to request metadata in a preferred format, and/or to inquire as to the formats that are available. It is also widely supported by software and common programming languages." . fair:A1.1 rdfs:label "A1.1" . } 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 ; . }