Is it acceptable to list URIs that don't have public specifications? For example:

  • origin & origin2 - Interact with Origin: install, purchase, and run games.
  • sfb - Launch meeting in Skype for Business
  • x-github-client - Open Git repository in GitHub Desktop.

--Stevoisiak (talk) 21:10, 23 July 2019 (UTC)Reply

Empty spans


Is there any reason why in the "Scheme" column every scheme is followed by an empty span code similar to this?

<span id="aaa:"></span>

Sabbut (talk) 09:45, 24 May 2020 (UTC)Reply

This is so each scheme on this list can be directly linked directly to.
The id attribute of an HTML tag identifies a unique element on a page and allows it to become an "anchor target", which can be linked to directly using URL fragment or hash segments .
To access an anchor target on a webpage, append # followed by the value of the target id attribute (known as a "fragment identifier") to the end of the destination page's URL. When a URL that includes a fragment identifier is followed in a web browser, it will automatically scroll down to the location of the specified anchor target on the page.
As with basic URLs, "anchor origin" elements (i.e. <a href="">...</a>) are used in HTML to link to anchor targets. "Relative" links that jump to an anchor target on the current page can be created by omitting the rest of the URL before the #, e.g. <a href="#fragment_identifier">Jump to section</a>.

A span element is generally used to create anchor targets as it is inline and does not inherently apply visual changes to a rendered webpage or any content between its tags.
The prefered Wikitext template to use instead of the HTML <span> tag is {{anchor}}, which can make the source code of articles a bit easier to read with less HTML tag clutter.

Syntax to create an anchor point/target
Markup Language Code
HTML <span id="fragment_identifier"></span>
Wikitext {{anchor|fragment_identifier}}

Example syntax for linking to HTML anchors
Anchor Destination Rendered Example Markup Language Code
On current page Go to section HTML <a href="#Looking_for_coffee_scheme">Go to section</a>
Wikitext [[#Looking_for_coffee_scheme|Go to section]]
On different page
(same website)
callto URI scheme HTML <a href="/wiki/List_of_URI_schemes#callto:">callto URI scheme</a>
Wikitext [[List of URI schemes#callto:|callto URI scheme]]
On different website List of URI schemes HTML <a href="">IANA List of URI schemes</a>
Wikitext [|IANA List of URI schemes]

TamsinM (talk) 13:53, 16 October 2022 (UTC)Reply

Looking for coffee scheme


The HTCPCP (coffee protocol) is supposed to be here. Google search says is is and wikiblame says it is, but I can't find it here.--Auric talk 19:07, 6 December 2020 (UTC)Reply

Looks like you need to add it (again) by yourself.
There is not an older revision than "14:35, 19 March 2019‎ Zyksnowy talk contribs‎ 71,168 bytes +71,168‎ Tag: nowiki added".
I think figuring out why it happened cost more time than adding it. --RoestVrijStaal (talk) 20:12, 6 December 2020 (UTC)Reply



Readers of this page may be interested in thw following discussion:

--Guy Macon (talk) 22:37, 1 June 2021 (UTC)Reply

This article should be removed if it can't be kept up to date


The upstream official registry is at IANA. It contains many registrations that are not reflected here. Would it not be safer simply to have a pointer to the official accurate source, as opposed to presenting inaccurate information? Tim Bray (talk) 18:16, 28 November 2023 (UTC)Reply

Proposed deletion of List of URI schemes


I talked to an ICANN person who suggested that the list of unofficial schemes was useful so the article shouldn't be deleted. So I replaced the out-of-date copy of the registry with a pointer to the authoritative upstream version and removed the marked-for-deletion.