moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-12-21 15:18:51 -05:00
Code Issues Releases Wiki Activity

XMPP URI reference

Browse Source 
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1782 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2008-04-18 16:50:48 +00:00
parent b79ff6f5e5
commit 02d05fea73
1 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
xep-0147.xml
View File

@ -16,7 +16,7 @@
<approver>Council</approver>
<dependencies>
<spec>XMPP Core</spec>
<spec>RFC 4622</spec>
<spec>RFC 5122</spec>
<spec>XEP-0053</spec>
</dependencies>
<supersedes/>
@ -52,19 +52,19 @@
<version>0.6</version>
<date>2005-12-01</date>
<initials>psa</initials>
<remark><p>Updated to reflect RFC 4622-03; modified file transfer query operations to handle both send and receive use cases.</p></remark>
<remark><p>Updated to reflect draft-saintandre-xmpp-iri-03; modified file transfer query operations to handle both send and receive use cases.</p></remark>
</revision>
<revision>
<version>0.5</version>
<date>2005-09-05</date>
<initials>psa</initials>
<remark><p>Updated to reflect RFC 4622-01; added file querytype for file transfer.</p></remark>
<remark><p>Updated to reflect draft-saintandre-xmpp-iri-01; added file querytype for file transfer.</p></remark>
</revision>
<revision>
<version>0.4</version>
<date>2005-06-06</date>
<initials>psa</initials>
<remark><p>Updated to reflect RFC 4622-00.</p></remark>
<remark><p>Updated to reflect draft-saintandre-xmpp-iri-00.</p></remark>
</revision>
<revision>
<version>0.3</version>
@ -86,8 +86,8 @@
</revision>
</header>
<section1 topic='Introduction' anchor='intro'>
<p>&rfc4622; defines a Uniform Resource Identifier (URI) scheme for use in forming URIs and Internationalized Resource Identifiers (IRIs) <note>On the difference between IRIs and URIs, see <cite>RFC 3987</cite>.</note> from the addresses of entities that can communicate using the Extensible Messaging and Presence Protocol (see &xmppcore;). Such identifiers enable identification of and interaction with XMPP entities by non-native applications such as databases and web browsers.</p>
<p>However, <cite>RFC 4622</cite> intentionally leaves the potential values of the query component open-ended, does not provide a list of common "actions" for queries (e.g., send message or join chatroom), and does not specify recommended "key-value" pairs to be used in the context of such actions. Therefore, this document defines a registry of such actions and key-value pairs (to be maintained by the &REGISTRAR;) and specifies a set of initial values for that registry.</p>
<p>&rfc5122; defines a Uniform Resource Identifier (URI) scheme for use in forming URIs and Internationalized Resource Identifiers (IRIs) <note>On the difference between IRIs and URIs, see <cite>RFC 3987</cite>.</note> from the addresses of entities that can communicate using the Extensible Messaging and Presence Protocol (see &xmppcore;). Such identifiers enable identification of and interaction with XMPP entities by non-native applications such as databases and web browsers.</p>
<p>However, <cite>RFC 5122</cite> intentionally leaves the potential values of the query component open-ended, does not provide a list of common "actions" for queries (e.g., send message or join chatroom), and does not specify recommended "key-value" pairs to be used in the context of such actions. Therefore, this document defines a registry of such actions and key-value pairs (to be maintained by the &REGISTRAR;) and specifies a set of initial values for that registry.</p>
<p>This document is organized as follows:</p>
<ul>
<li>The registry is defined in the <link url='#registrar-querytype'>XMPP IRI/URI Querytype Registry</link> section.</li>
@ -95,10 +95,10 @@
<li>A corresponding initial submission to the registry is specified in the <link url='#registrar-querytype-init'>Initial Registration</link> section.</li>
<li>The process for submitting additional values to the registry is specified in the <link url='#registrar-querytype-process'>Registration Process</link> section.</li>
</ul>
<p>Note: The format of the XMPP URI scheme, including the format of the query component, is fully specified and formally defined in <cite>RFC 4622</cite>; this document does not modify the xmpp URI scheme in any way and assumes that the reader is familiar with all aspects of <cite>RFC 4622</cite>.</p>
<p>Note: The format of the XMPP URI scheme, including the format of the query component, is fully specified and formally defined in <cite>RFC 5122</cite>; this document does not modify the xmpp URI scheme in any way and assumes that the reader is familiar with all aspects of <cite>RFC 5122</cite>.</p>
</section1>
<section1 topic='Terminology' anchor='terms'>
<p>This document inherits terminology from &rfc3986;, &rfc3987;, and <cite>RFC 4622</cite>.</p>
<p>This document inherits terminology from &rfc3986;, &rfc3987;, and <cite>RFC 5122</cite>.</p>
</section1>
<section1 topic='Query Actions' anchor='actions'>
<p>The range of actions that might be triggered by interaction with an XMPP entity by means of an XMPP IRI/URI is potentially as wide as the range of extensions to XMPP. This document does not seek to exhaustively define all such potential actions. However, the following actions might be of general interest:</p>
@ -114,7 +114,7 @@
<li>Registering with another entity via &xep0077;.</li>
<li>Initiating a file transfer with another entity (see &xep0096;).</li>
</ol>
<p>For each such action, the XMPP Registrar maintains a RECOMMENDED "querytype" (this can be thought of as an action name or "verb"; see <cite>RFC 4622</cite> for syntax and semantics) as well as an OPTIONAL list of keys to be used in key-value pairs if appropriate.</p>
<p>For each such action, the XMPP Registrar maintains a RECOMMENDED "querytype" (this can be thought of as an action name or "verb"; see <cite>RFC 5122</cite> for syntax and semantics) as well as an OPTIONAL list of keys to be used in key-value pairs if appropriate.</p>
<p>The querytypes and key-value pairs related to <cite>RFC 3920</cite> and <cite>RFC 3921</cite> are defined herein; the querytypes and key-value pairs related to protocols defined in the XMPP Standards Foundation's XEP series are defined in the relevant XMPP Extension Protocol specifications.</p>
<section2 topic='Message Action' anchor='actions-message'>
<p>It may desirable for an XMPP IRI/URI to trigger a specialized interface for sending an XMPP message stanza. The RECOMMENDED querytype for this action is "message". If no key-value pair is provided, interacting with an XMPP IRI/URI that contains a querytype of "message" SHOULD trigger an interface that enables the user to input the text of an XMPP message and other relevant parameters (e.g., a message subject or &xep0071; markup).</p>
@ -225,11 +225,11 @@ xmpp:romeo@montague.net?unsubscribe
</section2>
</section1>
<section1 topic='Internationalization Considerations' anchor='i18n'>
<p>Internationalization considerations for XMPP IRIs/URIs are specified in <cite>RFC 4622</cite>; the reader is referred to that document for a complete discussion of the relevant issues.</p>
<p>Internationalization considerations for XMPP IRIs/URIs are specified in <cite>RFC 5122</cite>; the reader is referred to that document for a complete discussion of the relevant issues.</p>
<p>Localization of application-specific data presented to a human user (e.g., as encapsulated in key-value pairs) is the responsibility of the "using protocol".</p>
</section1>
<section1 topic='Security Considerations' anchor='security'>
<p>Security considerations for XMPP IRIs/URIs are specified in <cite>RFC 4622</cite>.</p>
<p>Security considerations for XMPP IRIs/URIs are specified in <cite>RFC 5122</cite>.</p>
<p>Completion of some of the actions defined herein will cause changes to an entity's account, subscriptions to information, registration with services, communication with other entities, completion of ad-hoc commands, and the like. Naturally, such changes, information, services, and communications are potentially undesirable (e.g., joining a chatroom whose discussion topic is not of interest to, or even patently offensive to, the joining user). The invoked application SHOULD appropriately warn a human user regarding the potential consequences of the action about to be completed.</p>
</section1>
<section1 topic='IANA Considerations' anchor='iana'>