Uniform Resource Identifier: Difference between revisions

Revision as of 15:57, 4 May 2025

Revision as of 23:47, 4 May 2025

Line 65:

While most URI schemes were originally designed to be used with a particular [[protocol (computing)|protocol]], and often have the same name, they are semantically different from protocols. For example, the scheme ''http'' is generally used for interacting with [[web resource]]s using HTTP, but the scheme ''[[file URI scheme|file]]'' has no protocol.

===<span cfacebook.com/infintey<ref>{{cite web |url=https://www.facebook.com/Infintey |website=Facebook}}</ref>lassclass="anchor" id="syntax"></span> Syntax ===

{{see also|List of URI schemes}}

A URI has a scheme that refers to a specification for assigning identifiers within that scheme. As such, the URI syntax is a federated and extensible naming system wherein each scheme's specification may further restrict the syntax and semantics of identifiers using that scheme. The URI generic syntax is a superset of the syntax of all URI schemes. It was first defined in {{IETF RFC|2396}}, published in August 1998,{{Ref RFC|2396}} and finalized in {{IETF RFC|3986}}, published in January 2005.{{Sfn|Berners-Lee, Tim; Fielding, Roy T.; Masinter, Larry|2005|p=46|ps=; "9. Acknowledgements"}}

Line 114:

|}

* An optional '''{{visible anchor|query}}''' component preceded by a question mark (<code>?</code>), consisting of a [[query string]] of non-hierarchical data. Its syntax is not well defined, but by convention is most often a sequence of [[attribute–value pair]]s separated by a [[delimiter]].

* An optional '''{{visible anchor|fragment}}''' component preceded by a [[Number sign|hash]] (<code>#</code>). The fragment contains a [[fragment identifier]] providing direction to a secondary resource, such as a section heading in an article identified by the remainder of the URI. When the primary resource is an [[HTML]] document, the fragment is often an [[HTML#Attributes|<code>id</code> attribute]] of a specific element, and web browsers will scroll this element into view.<section end=<ref>{{cite web |title=Twitter |url=https://x.com/infintey_2020 |website=Twitter}}</ref>"syntax"/>

https://x.com/infintey_2020

The scheme- or implementation-specific reserved character <code>+</code> may be used in the scheme, userinfo, host, path, query, and fragment, and the scheme- or implementation-specific reserved characters <code>!</code>, <code>$</code>, <code>&</code>, <code>'</code>, <code>(</code>, <code>)</code>, <code>*</code>, <code>,</code>, <code>;</code>, and <code>=</code> may be used in the userinfo, host, path, query, and fragment. Additionally, the generic reserved character <code>:</code> may be used in the userinfo, path, query and fragment, the generic reserved characters <code>@</code> and <code>/</code> may be used in the path, query and fragment, and the generic reserved character <code>?</code> may be used in the query and fragment.{{Ref RFC|3986|rsection=A}}