URI scheme 2767915 223389294 2008-07-03T21:34:18Z 128.187.0.164 /* Unofficial but common URI schemes */ In the field of [[computer networking]], a '''URI scheme''' is the top level of the [[Uniform Resource Identifier]] (URI) naming structure. All URIs and absolute URI references are formed with a scheme name, followed by a [[Colon (punctuation)|colon character]] (":"), and the remainder of the URI called (in the outdated [[Request for Comments|RFCs]] 1738 and 2396, but not the current STD 66/RFC 3986) ''the scheme-specific part''. The syntax and semantics of the scheme-specific part are left largely to the specifications governing individual schemes, subject to certain constraints such as reserved characters and how to "[[Escape character|escape]]" them. URI schemes are sometimes erroneously referred to as "protocols", or specifically as '''URI protocols''' or '''[[URL]] protocols''', since most were originally designed to be used with a particular [[protocol (computing)|protocol]], and often have the same name. The <code>http</code> scheme, for instance, is generally used for interacting with [[Resource (Web)|Web resources]] using [[HyperText Transfer Protocol]]. Today, URIs with that scheme are also used for other purposes, such as [[Resource Description Framework|RDF]] resource identifiers and [[XML namespaces]], that are not related to the protocol. Furthermore, some URI schemes are not associated with any specific protocol (e.g. "<code>[[file URI scheme|file]]</code>") and many others do not use the name of a protocol as their prefix (e.g. "<code>[[Usenet newsgroup|news]]</code>"). URI schemes should be registered with [[Internet Assigned Numbers Authority|IANA]], although non-registered schemes are used in practice. RFC 4395 describes the procedures for registering new URI schemes. ==Generic syntax== [[Internet standard]] [http://rfc.net/std0066.html STD 66] (also RFC 3986) defines the generic syntax to be used in all URI schemes. Every URI is defined as consisting of four parts, as follows: <code><nowiki><scheme name> : <hierarchical part> [ ? <query> ] [ # <fragment> ]</nowiki></code> The '''scheme name''' consist of a letter followed by any combination of letters, digits, and the plus ("+"), period ("."), or hyphen ("-") characters; and is terminated by a colon (":"). The '''hierarchical part''' of the URI is intended to hold identification information hierarchical in nature. Usually this part begins with a double forward slash ("//"), followed by an authority part and an optional path. The authority part holds an optional user information part terminated with "@" (e.g. <code><nowiki>username:password@</nowiki></code>), a hostname (i.e. [[domain name]] or [[IP address]]), and an optional [[TCP and UDP port|port number]] preceded by a colon ":". The path part is a sequence of segments (conceptually similar to [[Directory (file systems)|directories]], though not necessarily representing them) separated by a forward slash ("/"). Each segment can contain parameters separated from it using a semicolon (";"), though this is rarely used in practice. The '''query''' is an optional part separated with a question mark, which contains additional identification information which is not hierarchical in nature. The [[query string]] syntax is not generically defined, but is commonly organized as a sequence of <code><nowiki><key>=<value></nowiki></code> pairs separated by an ampersand, e. g. <code><nowiki>key1=value1&key2=value2&key3=value3</nowiki></code>. The '''fragment''' is an optional part separated from the front parts by a hash ("#"). It holds additional identifying information that provides direction to a secondary resource, e.g. 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 a named [[anchor tag]]. ===Examples=== The following are two example URIs and their component parts (taken loosely from RFC 3986 — STD 66): foo://username:password@example.com:8042/over/there/index.dtb;type=animal?name=ferret#nose \ / \________________/\_________/ \__/\_________/ \___/ \_/ \_________/ \_________/ \__/ | | | | | | | | | | scheme userinfo hostname port path filename extension parameter(s) query fragment | \_______________________________/ | authority | ________________________ / \ / \ urn:example:animal:ferret:nose ==Official IANA-registered schemes== The official URI schemes registered with the [[Internet Assigned Numbers Authority|IANA]] follow. {| class="wikitable" |- ! Scheme ! Purpose ! width=60 | Defined by ! General format ! Notes |- | ''aaa'' <span id="aaa:"></span> | [[Diameter (protocol)|Diameter Protocol]] | RFC 3588 | <code><nowiki>aaa://<host>[:<port>][;transport=<transport>][;protocol=<protocol>]</nowiki></code> example: <br> <code><nowiki>aaa://host.example.com:1813;transport=udp;protocol=radius</nowiki></code> | |- | ''aaas'' <span id="aaas:"></span> | Secure equivalent of ''aaa'' | RFC 3588 | <code><nowiki>aaas://<host>[:<port>][;transport=<transport>][;protocol=<protocol>]</nowiki></code> | |- | ''acap'' <span id="acap:"></span> | [[Application Configuration Access Protocol]] | RFC 2244 | <code><nowiki>acap://[<user>[;AUTH=<type>]@]<host>[:<port>]/<entry></nowiki></code> | URL scheme used within the ACAP protocol for the "subdataset" attribute, referrals and inheritance |- | ''cap'' <span id="cap:"></span> | Calendar access protocol | RFC 4324 | ''generic syntax'' | URL scheme used to designate both calendar stores and calendars accessible using the CAP protocol |- | ''cid'' <span id="cid:"></span> | Referencing individual parts of an [[SMTP]]/[[MIME]] message | RFC 2392 | <code><nowiki>cid:<content-id></nowiki></code> | e.g. referencing an attached image within a formatted e-mail. (See also [[#mid:|mid:]]) |- | ''crid'' <span id="cid:"></span> | TV-Anytime Content Reference Identifier | RFC 4078 | <code><nowiki>crid://<host>/<data></nowiki></code> | Allow references to scheduled publications of broadcast media content. |- | [[data URI scheme|''data'']] | Inclusion of small data items inline | RFC 2397 | <code><nowiki>data:<mediatype>[;base64],<data></nowiki></code> | |- | ''dav'' | HTTP Extensions for Distributed Authoring ([[WebDAV]]) | RFC 2518 | <code><nowiki>dav:</nowiki></code> | Used for internal identifiers only; WebDAV itself addresses resources using the <code><nowiki>http:</nowiki></code> and <code><nowiki>https:</nowiki></code> schemes. [http://article.gmane.org/gmane.org.w3c.uri/808] |- | ''dict'' | Dictionary service protocol | RFC 2229 | <code><nowiki>dict://<user>;<auth>@<host>:<port>/d:<word>:<database>:<n></nowiki></code> <br> <code><nowiki>dict://<user>;<auth>@<host>:<port>/m:<word>:<database>:<strat>:<n></nowiki></code> | refer to definitions or word lists available using the DICT protocol |- | ''dns'' | [[Domain Name System]] | RFC 4501 | <code><nowiki>dns:[//<host>[:<port>]/]<dnsname>[?<dnsquery>]</nowiki></code> examples: <br> <code><nowiki>dns:example?TYPE=A;CLASS=IN</nowiki></code> <br> <code><nowiki>dns://192.168.1.1/ftp.example.org?type=A</nowiki></code> | designates a DNS resource record set, referenced by domain name, class, type, and, optionally, the authority |- | ''fax'' | Used for [[Fax|telefacsimile]] numbers | RFC 2806 | <code><nowiki>fax:<phonenumber></nowiki></code> | Seems to be deprecated in RFC 3966 in favour of [[#tel:|tel:]] |- | ''[[file URI scheme|file]]'' | Addressing files on local or network [[file system]]s | RFC 1738 | ''generic syntax'' <br> (often appears as <code><nowiki>file:///path</nowiki></code>, the 3<sup>rd</sup> '/' is the final delimiter when no host (authority) is specified between) | Unusual in not being bound to any network protocol, and not usable in an Internet context. |- | ''ftp'' | [[File Transfer Protocol|FTP]] resources | RFC 1738 | ''generic syntax'' | |- | ''go'' | Common Name Resolution Protocol | RFC 3368 | <code><nowiki>go://[<host>]?[<common-name>]*[;<attribute>=[<type>,]<value>]</nowiki></code> or <br> <code><nowiki>go:<common-name>*[;<attribute>=[<type>,]<value>]</nowiki></code> | |- | ''gopher'' | Used with [[Gopher (protocol)|Gopher protocol]] | RFC 4266 | <code><nowiki>gopher://<host>:<port>/<item type>/<path></nowiki></code> | |- | ''h323'' | Used with [[H.323]] multimedia communications | RFC 3508 | <code><nowiki>h323:[<user>@]<host>[:<port>][;<parameters>]</nowiki></code> | |- | ''http'' | [[HyperText Transfer Protocol|HTTP]] resources | RFC 2616 | ''generic syntax'' | |- | ''[[https]]'' | HTTP connections secured using [[Transport Layer Security|SSL/TLS]] | RFC 2817 | ''generic syntax'' | |- | ''icap'' | Internet Content Adaptation Protocol | RFC 3507 | | |- | ''im'' | [[Instant messaging]] protocol | RFC 3860 RFC 4622 | <code><nowiki>im:<username>[@<host>]</nowiki></code> | Works as <code>xmpp:</code> URI for single user chat sessions. |- | ''imap'' | Accessing e-mail resources through [[IMAP]] | RFC 2192 | <code><nowiki>imap://[<user>[;AUTH=<type>]@]<host>[:<port>]/<command></nowiki></code> | |- | ''info'' | Information Assets with Identifiers in Public Namespaces | RFC 4452 | | |- | ''ipp'' | [[Internet Printing Protocol]] | RFC 3510 | | |- | ''iris''<br />''iris.beep''<br />''iris.xpc''<br />''iris.xpcs''<br />''iris.lws'' | Internet Registry Information Service | RFC 3981 RFC 3983 RFC 4992 RFC 4992 RFC 4993 | | |- | ''ldap'' | [[Lightweight Directory Access Protocol|LDAP]] directory request | RFC 2255 <br> RFC 4516 | <code><nowiki>ldap://[<host>[:<port>]][/<dn> [?[<attributes>][?[<scope>][?[<filter>][?<extensions>]]]]]</nowiki></code> example: <br> <code><nowiki>ldap://ldap1.example.net:6666/o=University%20of%20Michigan, c=US??sub?(cn=Babs%20Jensen)</nowiki></code> | |- | ''mailto'' | [[Simple Mail Transfer Protocol|SMTP]] [[e-mail]] addresses and default content | RFC 2368 | <code><nowiki>mailto:<address>[?<header1>=<value1>[&<header2>=<value2>]]</nowiki></code> example: <br> <code><nowiki>mailto:jsmith@example.com?subject=A%20Test&body=My%20idea%20is%3A%20%0A</nowiki></code> | Headers are optional, but often include <code><nowiki>subject=</nowiki></code>; <code><nowiki>body=</nowiki></code> can be used to pre-fill the body of the message. |- | ''mid'' <span id="mid:"></span> | Referencing [[SMTP]]/[[MIME]] messages, or parts of messages. | RFC 2392 | <code><nowiki>mid:<message-id>[/<content-id>]</nowiki></code> | (See also [[#cid:|cid:]]) |- | ''modem'' | modem | RFC 3966 | | |- | ''msrp''<br />''msrps'' | Message Session Relay Protocol | RFC 4975 | | |- | ''mtqp'' | Message Tracking Query Protocol | RFC 3887 | | |- | ''mupdate'' | Mailbox Update Protocol | RFC 3656 | | |- | ''news'' | ([[Usenet]]) newsgroups and postings | RFC 1738 | <code><nowiki>news:<newsgroupname></nowiki></code> or <br> <code><nowiki>news:<message-id></nowiki></code> | References a particular ''resource'', regardless of location. |- | ''nfs'' | [[Network File System (protocol)|Network File System]] resources | RFC 2224 | ''generic syntax'' | |- | ''nntp'' | Usenet [[Network News Transfer Protocol|NNTP]] | RFC 1738 | <code><nowiki>nntp://<host>:<port>/<newsgroup-name>/<article-number></nowiki></code> | Referencing a specific host is often less useful than referencing the resource generically, as NNTP servers are not always publicly accessible |- | ''opaquelocktoken'' | opaquelocktoken | RFC 4918 | | |- | ''pop'' | Accessing mailbox through [[POP3]] | RFC 2384 | <code><nowiki>pop://[<user>[;AUTH=<auth>]@]<host>[:<port>]</nowiki></code> | |- | ''pres'' | Used in Common Profile for Presence (CPP) to identify presence | RFC 3859 | <code><nowiki>pres:<address>[?<header1>=<value1>[&<header2>=<value2>]]</nowiki></code> | Similar to "mailto:" |- | ''prospero'' | Prospero Directory Service | RFC 4157 | | Listed as "Historical" by IANA. |- | ''rtsp'' | [[Real Time Streaming Protocol]] | RFC 2326 | | |- | ''service'' | | RFC 2609 | | |- | ''shttp'' | Secure [[HTTP]] | RFC 2660 | | Largely superseded by [[HTTPS]]. |- | ''sip'' | Used with [[Session Initiation Protocol]] (SIP) | RFC 3969 <br> RFC 3261 | <code><nowiki>sip:<user>[:<password>]@<host>[:<port>][;<uri-parameters>][?<headers>]</nowiki></code> examples: <br> <code><nowiki>sip:alice@atlanta.com?subject=project%20x&priority=urgent</nowiki></code> <br> <code><nowiki>sip:+1-212-555-1212:1234@gateway.com;user=phone</nowiki></code> | |- | ''[[sips URI scheme|sips]]'' | Secure equivalent of ''sip'' | RFC 3969 <br> RFC 3261 | <code><nowiki>sips:<user>[:<password>]@<host>[:<port>][;<uri-parameters>][?<headers>]</nowiki></code> | |- | ''snmp'' | Simple Network Management Protocol | RFC 4088 | <code><nowiki>snmp://[user@]host[:port][/[<context>[;<contextEngineID>]][/<oid>]]</nowiki></code> examples: <br> <code><nowiki>snmp://example.com//1.3.6.1.2.1.1.3+</nowiki></code> <br> <code><nowiki>snmp://tester5@example.com:8161/bridge1;800002b804616263</nowiki></code> | |- | ''soap.beep''<br />''soap.beeps'' | | RFC 3288 | | |- | ''tag'' | | RFC 4151 | | |- | ''tel'' <span id="tel:"></span> | Used for telephone numbers | RFC 3966 <br> RFC 2806 | <code><nowiki>tel:<phonenumber></nowiki></code> | |- | ''telnet'' | Used with [[telnet]] | RFC 4248 | <code><nowiki>telnet://<user>:<password>@<host>[:<port>/]</nowiki></code> | |- | ''tftp'' | Trivial File Transfer Protocol | RFC 3617 | | |- | ''thismessage'' | multipart/related relative reference resolution | RFC 2557 | | |- | ''tip'' | Transaction Internet Protocol | RFC 2371 | | |- | ''tv'' | TV Broadcasts | RFC 2838 | | |- | ''urn'' | [[Uniform Resource Name]]s | RFC 2141 | <code><nowiki>urn:<namespace>:<specificpart></nowiki></code> | |- | ''vemmi'' | '''Ve'''rsatile '''M'''ulti'''m'''edia '''I'''nterface | RFC 2122 | | |- | ''wais'' | Used with [[Wide area information server]] (WAIS) | RFC 4156 | <code><nowiki>wais://<host>:<port>/<database>[?<search>]</nowiki></code> or <code><nowiki>wais://<host>:<port>/<database>/<wtype>/<wpath></nowiki></code> | Listed as "Historical" by IANA. |- | ''xmlrpc.beep''<br />''xmlrpc.beep'' | | RFC 3529 | | |- | ''xmpp'' | [[XMPP]] ([[Jabber]]) | RFC 5122 | <code><nowiki>xmpp:<user>@<host>[:<port>]/[<resource>][?<query>]</nowiki></code> | |- | ''z39.50r'' | [[Z39.50]] retrieval | RFC 2056 | <code><nowiki>z39.50r://<host>[:<port>]/<database>?<docid>[;esn=<elementset>][;rs=<recordsyntax>]</nowiki></code> |- | ''z39.50s'' | Z39.50 session | RFC 2056 | <code><nowiki>z39.50s://<host>[:<port>]/[<database>][?<docid>][;esn=<elementset>][;rs=<recordsyntax>]</nowiki></code> |} == Unofficial but common URI schemes == {| class="wikitable" |- ! Scheme ! Purpose ! width=90 | Defined by ! General format ! Notes |- | ''[[about URI scheme|about]]'' | Displaying product information and internal information | colspan=2 align=center | Un-standardised<br>about:blank is commonly used to display a blank page. | Widely used by [[web browser]]s, sometimes even providing interactive resources. The [[Opera (web browser)|Opera web browser]] uses <code>opera:</code> instead. |- | ''[[AOL Instant Messenger#URI scheme|aim]]'' | Controlling [[AOL Instant Messenger]]. | [[AOL]] | <code><nowiki>aim:<function>?<parameters></nowiki></code> | Functions include <code>goim</code>, <code>addbuddy</code>, and <code>buddyicon</code>. |- | ''[[Active Worlds|aw]]'' | Link to an Active Worlds world | [[Activeworlds Inc.]] | <code><nowiki>aw://<worldserver host>:<worldserver port>/<worldname></nowiki></code> | Mostly found in HTTP referers when users open a website from within a Active Worlds world. |- | ''callto'' <span id="callto:"></span> | Launching [[Skype]] call (+And in Hungary the KLIP Software call too) (unofficial; see also [[#skype:|skype:]]) | [[Skype]] | <code><nowiki>callto:<screenname></nowiki></code> or <br> <code><nowiki>callto:<phonenumber></nowiki></code> [http://daringfireball.net/2005/12/callto_uris_safari] | Introduced with [[Microsoft NetMeeting]]. Works with current version of [[Skype]] with [[Firefox]], [[Internet Explorer]] and [[Safari (web browser)|Safari]] |- | ''chrome'' <span id="chrome:"></span> | Specifies user interfaces built using XUL in Mozilla-based browsers. | [[Mozilla]] |<code><nowiki>chrome://<package>/<section>/<path></nowiki></code> (Where <code><section></code> is either "<code>content</code>", "<code>skin</code>" or "<code>locale</code>") | Works only in Mozilla-based browsers such as Firefox, SeaMonkey and Netscape. |- | ''cvs'' <span id="cvs:"></span> | Provides a link to a [[Concurrent Versions System]] (CVS) Repository | [[Concurrent Versions System]] |<code><nowiki>cvs://<method:logindetails>@<repository>/<modulepath>;[date=date to retrieve | tag=tag to retrieve] </nowiki></code> | |- | ''[[ed2k URI scheme|ed2k]]'' | Resources available using the [[eDonkey2000]] network | eDonkey2000 | <code><nowiki>ed2k://|file|<filename>|<size of file>|<hash of file>|/</nowiki></code> or <br> <code><nowiki>ed2k://|server|<host>|<port>|/</nowiki></code> | Links to servers are also possible, as are additional parameters. Official documentation from {{wayback|http://www.edonkey2000.com/documentation/distro.html|eDonkey2000 website}} |- | ''[[feed URI scheme|feed]]'' | [[web feed]] subscription | | <code><nowiki>feed:<absolute_uri></nowiki></code> or <br> <code><nowiki>feed://<hierarchical part></nowiki></code> examples: <br> <code><nowiki>feed://example.com/rss.xml</nowiki></code> <br> <code><nowiki>feed:https://example.com/rss.xml</nowiki></code> | See [[Feed URI scheme]] for a detailed overview of common implementations, supported software, and critics. |- | ''fish'' | Accessing another computer's files using the [[Secure Shell|SSH]] protocol | [http://docs.kde.org/stable/en/kdebase/kioslave/fish.html fish KDE kioslave] | <code><nowiki>fish://[<username>[:<password>]@]<hostname>[:<port>]</nowiki></code> | See [[Files transferred over shell protocol]] for details about the protocol. |- | ''gg'' | Starting chat with [[Gadu-Gadu]] user | [[Gadu-Gadu]] | <code><nowiki>gg:<userid></nowiki></code> | |- | ''gizmoproject'' | [[Gizmo Project]] calling link. | | <code><nowiki>gizmoproject://call?id=<gizmo_id></nowiki></code> | May use sip:// instead of gizmoproject:// in recent versions of Gizmo. |- | ''iax2'' | [[Inter-Asterisk eXchange]] protocol version 2 | [http://tools.ietf.org/id/draft-guy-iax-03.txt IETF Draft] | <code><nowiki>iax2:[<username>@]<host>[:<port>][/<number>[?<context>]]</nowiki></code> examples: <br> <code><nowiki>iax2:[2001:db8::1]:4569/alice?friends</nowiki></code> <br> <code><nowiki>iax2:johnQ@example.com/12022561414</nowiki></code> |- | ''irc'' | Connecting to a server to join a channel. | [http://tools.ietf.org/html/draft-butcher-irc-url-04 IETF Draft] <br> [http://tools.ietf.org/html/draft-mirashi-url-irc-01 Old IETF Draft] | <code><nowiki>irc://<host>[:<port>]/[<channel>[?<password>]]</nowiki></code> | Assuming the client knows a server associated with the name, "host" may optionally be an IRC network name. |- | ''ircs'' | Secure equivalent of ''irc'' | [http://tools.ietf.org/html/draft-butcher-irc-url-04 IETF Draft] | <code><nowiki>ircs://<host>[:<port>]/[<channel>[?<password>]]</nowiki></code> | See ''irc'' |- | ''itms'' | Used for connecting to the [[iTunes Music Store]] | [[Apple Inc]] | <code><nowiki>itms:</nowiki></code> | |- | ''[[JAR (file format)|jar]]'' | Compressed archive member | [http://java.sun.com/javase/6/docs/api/java/net/JarURLConnection.html Java API] | <code><nowiki>jar:<url>!/[<entry>]</nowiki></code> | Works for any [[ZIP (file format)|ZIP]] based file. |- | ''javascript'' | Execute javascript code | [[Netscape]] | <code><nowiki>javascript:<javascript to execute></nowiki></code> | Works in any modern browser. |- | ''keyparc'' | Keyparc encrypt/decrypt resource. | | <code><nowiki>keyparc://encrypt/<username>/<uri></nowiki></code> or <code><nowiki>keyparc://decrypt/<username>/<uri></nowiki></code> |- | ''lastfm'' | Connecting to a [[radio stream]] from [[Last.fm]]. | [[Last.fm]] | <code><nowiki>lastfm://<radio_stream></nowiki></code> or <code><nowiki>lastfm://globaltags/<genre></nowiki></code> or <br> <code><nowiki>lastfm://user/<username>/<stuff></nowiki></code> | |- | ''ldaps'' | Secure equivalent of ''ldap'' | | <code><nowiki>ldaps://[<host>[:<port>]][/<dn> [?[<attributes>][?[<scope>][?[<filter>][?<extensions>]]]]]</nowiki></code> | Not an IETF standard, but commonly used in applications. |- | ''[[magnet URI scheme|magnet]]'' | "magnet links" | [http://magnet-uri.sourceforge.net/ Magnet-URI Project] | <code><nowiki>magnet:?xt=urn:sha1:<hash of file>&dn=<display name></nowiki></code> <br> (other parameters are also possible) | Used by various [[peer-to-peer]] clients, usually providing the hash of a file to be located on the network. |- | ''[[Microsoft Media Services|mms:]]'' | Windows streaming media | | <code><nowiki>mms://<host>:<port>/<path></nowiki></code> | Used by Windows Media Player to stream audio and/or video. |- | ''msnim'' | Adding a contact, or starting a conversation in Windows Live Messenger | [[Windows Live Messenger]] | Add a contact to the buddy list <br> <code><nowiki>msnim:add?contact=nada@nowhere.com</nowiki></code> <br> Start a conversation with a contact <br> <code><nowiki>msnim:chat?contact=nada@nowhere.com</nowiki></code> <br> Start a voice conversation with a contact <br> <code><nowiki>msnim:voice?contact=nada@nowhere.com</nowiki></code> <br> Start a video conversation with a contact <br> <code><nowiki>msnim:video?contact=nada@nowhere.com</nowiki></code> | Can be invoked from a web page or via a run command or an ie browser URL (won't work with firefox 2.0.0.8). For web pages use this HTML: <code><nowiki><a href="chat?contact=nada@nowhere.com">Click to chat!</a></nowiki></code> |- | ''mvn'' | Access [[Apache Maven]] repository artifacts | [[OPS4J]] | <code><nowiki>mvn:org.ops4j.pax.web.bundles/service/0.2.0-SNAPSHOT</nowiki></code><br><code><nowiki>mvn:http://user:password@repository.ops4j.org/maven2!org.ops4j.pax.web.bundles/service/0.2.0</nowiki></code> | |- | ''notes'' | Open a [[Lotus Notes]] document or database | [[Lotus Notes]] | <code><nowiki>notes://<address></nowiki></code> | Used by IBM Lotus Notes to refer to documents and databases stored within the Lotus Notes system. When clicked in a browser on a computer with Lotus Notes client installed, Notes will open the document link as if a Notes DocLink were clicked within Notes. |- | ''nsfw'' | [[Not Safe For Work]] | N/A {{Fact|date=March 2008}} | <code><nowiki>nsfw://<address></nowiki></code> | NSFW is not an official URI and is not known to be in use by any programs. Using an "NSFW" address will result in a browser error. However, "nsfw://" indicates that the address which follows may be objectionable in nature, containing explicit material unsuitable for work or school environments. To view the address, the "nsfw://" tag must be replaced by the user with "http://". |- | ''psyc'' | Used to identify or locate a person, group, place or a service and specify its ability to communicate | [[PSYC]] | <code><nowiki>psyc:[//<host>[:[<port>][<transport>]]/[<object-name>][#<channel-name>]</nowiki></code> | Official documentation from [http://www.psyc.eu/unl.html PSYC website] |- | ''rsync'' | [[Rsync]] | | <code><nowiki>rsync://<host>[:<port>]/<path></nowiki></code> | |- | ''secondlife'' | Open the Map floater in Second Life application to teleport the resident to the location. | [[Linden Lab]] | <code><nowiki>secondlife://<region name>/<x position>/<y position>/<z position></nowiki></code> <!-- Simil Miles --> | Used by [http://slurl.com/ SLurl.com]. [http://secondlife.com/knowledgebase/article.php?id=360 Knowledge base article]. |- | ''sgn'' | Social Graph Node Mapper | [[Google]] | example: <br> <code><nowiki>sgn://social-network.example.com/?ident=bob</nowiki></code> | Official documentation from [http://code.google.com/p/google-sgnodemapper/ sgnodemapper project]. |- | ''skype'' <span id="skype:"></span> | Launching [[Skype]] call (official; see also [[#callto:|callto:]]) | [[Skype]] | <code><nowiki>skype:<username|phonenumber>[?[add|call|chat|sendfile|userinfo]]</nowiki></code> | Official documentation from [http://www.skype.com/share/buttons/advanced.html Skype website]. |- | ''ssh'' | [[Secure Shell|SSH]] connections (like telnet:) and | [http://tools.ietf.org/html/draft-ietf-secsh-scp-sftp-ssh-uri-04 IETF Draft] | <code><nowiki>ssh://[<user>[;fingerprint=<host-key fingerprint>]@]<host>[:<port>]</nowiki></code> | |- | ''sftp'' | [[SSH file transfer protocol|SFTP]] file transfers (not be to confused with [[FTPS]] (FTP/SSL)) | [http://tools.ietf.org/html/draft-ietf-secsh-scp-sftp-ssh-uri-04 IETF Draft] | <code><nowiki>sftp://[<user>[;fingerprint=<host-key fingerprint>]@]<host>[:<port>]/<path>/<file></nowiki></code> | |- | ''smb'' | Accessing [[Server Message Block|SMB]]/CIFS shares | [http://tools.ietf.org/html/draft-crhertel-smb-url-11 IETF Draft] | <code><nowiki>smb://[<user>@]<host>[:<port>][/[<path>]][?<param1>=<value1>[;<param2>=<value2>]]</nowiki></code> or <br> <code><nowiki>smb://[<user>@]<workgroup>[:<port>][/]</nowiki></code> | |- | ''sms'' | Interact with [[SMS]] capable devices for composing and sending messages. | [http://tools.ietf.org/html/draft-wilde-sms-uri-12 IETF draft] | <code><nowiki>sms:<phone number>?<action></nowiki></code> | Should be used as a subset to the <code>tel:</code> schema. {{Fact|date=August 2007}} |- | ''soldat'' | Joining servers | [[Soldat]] | <code><nowiki>soldat://<host>:<port>/</nowiki></code> example: <br> <code><nowiki>soldat://127.0.0.1:23073/</nowiki></code> | Official note in [http://www.soldat.pl/man/manual-en.html Manual] |- | ''steam'' | Interact with Steam: install apps, purchase games, run games, etc. | [[Steam (content delivery)|Steam]], [[Valve Corporation]] | <code><nowiki>steam:<command line arguments></nowiki></code> or <br> <code><nowiki>steam://<action>/<id, addon, IP, hostname, etc.></nowiki></code> | Official documentation from [http://developer.valvesoftware.com/wiki/Steam_browser_protocol Valve Developer Community website] |- | ''svn'' <span id="svn:"></span> | Provides a link to a Subversion (SVN) source control repository | [[Subversion (software)]] |<code><nowiki>svn[+ssh]://<logindetails>@<repository><:port>/<modulepath></nowiki></code> | |- | ''teamspeak'' | Joining a server. | [[TeamSpeak]] | <code><nowiki>teamspeak://<server>[:<port>]/[?<parameter1>=<value1>[&<parameter2>=<value2>]]</nowiki></code> | Official documentation from [http://www.goteamspeak.com/?page=faq&cat=client&rate=46#howto_connect_via_browser TeamSpeak Website] |- | ''unreal'' | Joining servers | [[Unreal]] | <code><nowiki>unreal://<server>[:<port>]/</nowiki></code> | Unreal legacy "protocol" |- | ''ut2004'' | Joining servers | [[Unreal Tournament 2004]] | <code><nowiki>ut2004://<server>[:<port>][/<map>?<options>]</nowiki></code> | Documentation from [http://udn.epicgames.com/Two/IniFilesTutorial Unreal Developer Network] |- | ''ventrilo'' | Joining a server. | [[Ventrilo]] | <code><nowiki>ventrilo://<server>[:<port>]/[?<parameter1>=<value1>[&<parameter2>=<value2>]]</nowiki></code> | Official documentation from [http://www.ventrilo.com/setup.php#Web_Links Ventrilo Website] |- | ''[[view-source]]'' | Shows a web page as code 'in the raw'. | [[Mozilla]] | <code><nowiki>view-source:<URI></nowiki></code> example:<br /> <code><nowiki>view-source:http://en.wikipedia.org/wiki/URI_scheme</nowiki></code> | See ??? for details. |- | ''webcal'' | Subscribing to calendars in [[iCalendar]] format | [[iCalendar]] | <code><nowiki>webcal://<hierarchical part></nowiki></code> example:<br /> <code><nowiki>webcal://example.com/calendar.ics</nowiki></code> | [[HTTP]] as a transport protocol is assumed.<br />See [[Webcal]] for details. |- | ''wyciwyg'' | What You Cache Is What You Get [[WYCIWYG]] | [[Mozilla]] | <code><nowiki>wyciwyg://<URI></nowiki></code> | See [[WYCIWYG]] for details. |- | ''xfire'' | Adding friends and servers, joining servers, changing status text. | [[Xfire]] | <code><nowiki>xfire:<function>[?<parameter1>=<value1>[&<parameter2>=<value2>]]</nowiki></code> | Official documentation from [http://www.xfire.com/xfire_urls/?name=XFire&file=xfireurls Xfire website] |- | ''xri'' | eXtensible Resource Identifier ([[XRI]]) | [[OASIS_(organization)|OASIS]] [http://www.oasis-open.org/committees/xri XRI Technical Committee] | <code><nowiki>xri://<authority>[/[<path>]][?<query>][#fragment]</nowiki></code> | Official documentation from [http://www.oasis-open.org/committees/xri OASIS XRI Technical Committee] |- | ''ymsgr'' | Sending an instant message to a Yahoo! Contact. | [[Yahoo! Messenger]] | <code><nowiki>ymsgr:sendIM?<screenname></nowiki></code> | |} == External links == *[http://www.iana.org/assignments/uri-schemes.html Official IANA Registry of URI Schemes] *[http://esw.w3.org/topic/UriSchemes/ More information, including many more schemes] {{URI scheme}} [[Category:URI scheme| ]] [[de:URI]]