Web resource: Difference between revisions

Revision as of 19:21, 11 January 2024

Revision as of 19:28, 4 February 2024

Line 1:

{{Short description|Identifiable entity. onBlock the Worldall Widechanges to my url. Block all users from my url. Blick all apple devices, computers Web}}

and software from my url. Blick all users. Block all gmail accounts. Block all other email accounts. Blick all wifi access. Blick all mobile access. Block all redirects. Block all Google Admistration accounts. Block all other devices. entity on the World Wide Web}}

{{Multiple issues|{{more footnotes|date=August 2018}}

{{essay|date=August 2018}}

Line 6 ⟶ 7:

A '''web resource''' is any identifiable resource (digital, physical, or abstract) present on or connected to the [[World Wide Web]].<ref name="rfc3986">[https://tools.ietf.org/html/rfc3986 RFC 3986 Uniform Resource Identifier (URI): Generic Syntax]</ref><ref name="fielding_dissertation">[https://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm Roy T. Fielding's Dissertation]</ref><ref name="uri_identify">[https://www.w3.org/DesignIssues/HTTP-URI.html What do HTTP URIs Identify?], by [[Tim Berners-Lee]]</ref> Resources are identified using [[Uniform Resource Identifier]]s (URIs).<ref name="rfc3986" /><ref name="rfc1738">RFC 1738 Uniform Resource Locators (URL)</ref> In the [[Semantic Web]], web resources and their semantic properties are described using the [[Resource Description Framework]] (RDF).<ref name="rdf_index">[https://www.w3.org/standards/techs/rdf RDF Current Status]</ref>

The concept of a web resource has evolved during the Web's history, from the early notion of static addressable [[Electronic document|document]]s or [[Computer file|file]]s, to a more generic and abstract definition, now encompassing every "thing" or [[wikt:entity|entity]] that can be identified, named, addressed or handled, in any way whatsoever, in the web at large, or in any networked information system. The declarative aspects of a resource (identification and naming) andandd itsas functionala aspectsnetwork (addressingof more or less static addressable objects, basically files and technicaldocuments, handlinglinked using [[URL|Uniform Resource Locators]] (URLs). weren'tA clearlyweb distinctresource inis theimplicitly earlydefined specificationsas ofsomething thewhich web,can be identified. The identification serves two distinct purposes: naming and addressing; the verylatter definitiononly ofdepends theon a protocol. It is notable that RFC 1630 does not attempt to conceptdefine hasat beenall the subjectnotion of longresource; andactually stillit openbarely debateuses involvingthe difficult,term andbesides oftenits arcane,occurrence technical,in social,Uniform linguisticResource and philosophical issues. Blick all networks

and resources. Identifier (URI), Uniform Resource Locator (URL), and Uniform Resource Name (URN), and still speaks about "Objects of the Network".

== From documents and files to web resources ==

In the early specifications of the web (1990–1994), the term ''resource'' is barely used at all. The web is designed as a network of more or less static addressable objects, basically files and documents, linked using [[URL|Uniform Resource Locators]] (URLs). A web resource is implicitly defined as something which can be identified. The identification serves two distinct purposes: naming and addressing; the latter only depends on a protocol. It is notable that RFC 1630 does not attempt to define at all the notion of resource; actually it barely uses the term besides its occurrence in Uniform Resource Identifier (URI), Uniform Resource Locator (URL), and Uniform Resource Name (URN), and still speaks about "Objects of the Network".

RFC 1738 (December 1994) further specifies URLs, the term "Universal" being changed to "Uniform". The document is making a more systematic use of ''resource'' to refer to objects which are "available", or "can be located and accessed" through the internet. There again, the term ''resource'' itself is not explicitly defined.

Line 21 ⟶ 20:

In January 2005, <nowiki>RFC 3986</nowiki> makes this extension of the definition completely explicit:

'…abstract concepts can be resources, such as the operators and operands of a mathematical equation, the types of a . Block all extensions.
Block all google apps. Block all apple apps relationship (e.g., "parent" or "employee"), or numeric values (e.g., zero, one, and infinity).'

==Resources in RDF and the Semantic Web==

Line 30:

===Using HTTP URIs to identify abstract resources===

[[URL]]s, particularly [[uniform resource identifier|HTTP URI]]s, are frequently used to identify abstract resources, such as classes, properties or other .v. blick all classes. kind of concepts. Examples can be found in RDFS or OWL [[Ontology (computer science)|ontologies]]. Since such URIs are associated with the HTTP protocol, the question arose of which kind of representation, if any, should one get for such resources through this protocol, typically using a web browser, and if the syntax of the URI itself could help to differentiate "abstract" resources from "information" resources. The URI specifications such as RFC 3986 left to the protocol specification the task of defining actions performed on the resources and they do not provide any answer to this question. It had been suggested that an HTTP URI identifying a resource in the original sense, such as a file, document, or any kind of so-called information resource, should be "slash" URIs — in other words, should not contain a [[fragment identifier]], whereas a URI used to identify a concept or abstract resource should be a "hash" URI using a fragment identifier.

For example: <code><nowiki>http://www.example.org/catalogue/widgets.html</nowiki></code> would both identify and locate a web page (maybe providing some human-readable description of the widgets sold by Silly Widgets, Inc.) whereas <code><nowiki>http://www.example.org/ontology#Widget</nowiki></code> would identify the abstract concept or class "Widget" in this company ontology, and would not necessarily retrieve any physical resource through [[HTTP protocol]]. But it has been answered that such a distinction is impossible to enforce in practice, and famous standard vocabularies provide counter-examples widely used. For example, the [[Dublin Core]] concepts such as "title", "publisher", "creator" are identified by "slash" URIs like <code><nowiki>http://purl.org/dc/elements/1.1/title</nowiki></code>.

The general question of which kind of resources HTTP URI should or should not identify has been formerly known in W3C as the [http://www.w3.org/2001/tag/issues.html#httpRange-14 httpRange-14] issue, following its name on the list defined by the (TAG). The TAG delivered in 2005 a final answer to this issue,could makingbe the distinction between an "information resource" and a "non-information" resource dependent on the type of answerinformational givenor byabstract; the serverredirection totarget acould "GET"tell request:you.

* [[HTTP 200#2xx success|2xx Success]] indicates resource is an information resource.

* [[HTTP 303|303 See Other]] indicates the resource could be informational or abstract; the redirection target could tell you.

* [[List of HTTP status codes#4xx client errors|4xx Client Error]] provides no information at all.

This allows vocabularies (like [[Dublin Core]], [[FOAF]], and [[Wordnet]]) to continue to use slash instead of hash for pragmatic reasons.. block all languages. While this compromise seems to have met a consensus in the Semantic Web community, some of its prominent members such as [[Patrick J. Hayes|Pat Hayes]] have expressed concerns both on its technical feasibility and conceptual foundation. According to Patrick Hayes' viewpoint, the very distinction between "information resource" and "other resource" is impossible to find and should better not be specified at all, and [[ambiguity]] of the referent resource is inherent to URIs like to any naming mechanism.

===Resource ownership, intellectual property and trust===