<abstract>This document defines a registry of query components to be used in the context of XMPP IRIs/URIs and also specifies an initial submission of values to that registry.</abstract>
<remark><p>Added actions for roster removal, presence unsubscription, and cancellation of registration; moved querytypes related to XMPP extensions from this document to the relevant XMPP Extension Protocol specifications.</p></remark>
<remark><p>Per a vote of the Jabber Council, advanced to Active.</p></remark>
</revision>
<revision>
<version>0.7</version>
<date>2006-03-16</date>
<initials>psa</initials>
<remark><p>Added actions for ad-hoc commands and vCard retrieval; clarified some explanatory text.</p></remark>
</revision>
<revision>
<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>
</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>
</revision>
<revision>
<version>0.4</version>
<date>2005-06-06</date>
<initials>psa</initials>
<remark><p>Updated to reflect RFC 4622-00.</p></remark>
</revision>
<revision>
<version>0.3</version>
<date>2005-02-28</date>
<initials>psa</initials>
<remark><p>Updated to reflect draft-saintandre-xmpp-uri-08 and subsequent XMPP WG discussion; removed use cases for editing roster items, removing roster items, leaving chatrooms, unsubscribing, and unregistering (these make more sense from within a dedicated client); added use case for simultaneously joining a room and inviting other participants; further specified security considerations.</p></remark>
</revision>
<revision>
<version>0.2</version>
<date>2004-11-17</date>
<initials>psa</initials>
<remark><p>Updated to reflect draft-saintandre-xmpp-uri-07; specified Service Discovery usage.</p></remark>
</revision>
<revision>
<version>0.1</version>
<date>2004-11-12</date>
<initials>psa</initials>
<remark><p>Initial version.</p></remark>
</revision>
</header>
<section1topic='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 ®ISTRAR;) 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 <linkurl='#registrar-querytype'>XMPP IRI/URI Querytype Registry</link> section.</li>
<li>An initial set of actions and key-value pairs is described in the <linkurl='#actions'>Query Actions</link> section.</li>
<li>A corresponding initial submission to the registry is specified in the <linkurl='#registrar-querytype-init'>Initial Registration</link> section.</li>
<li>The process for submitting additional values to the registry is specified in the <linkurl='#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>
</section1>
<section1topic='Terminology'anchor='terms'>
<p>This document inherits terminology from &rfc3986;, &rfc3987;, and <cite>RFC 4622</cite>.</p>
</section1>
<section1topic='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>
<ol>
<li>Sending a message.</li>
<li>Adding or removing a roster item.</li>
<li>Subscribing to or unsubscribing from an entity's presence information.</li>
<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>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>
<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>
<p>A query component whose querytype is "message" MAY specify various key-value pairs. The following three keys are associated with the child elements of the &MESSAGE; stanza specified in the XML schema for the 'jabber:client' namespace as defined in &xmppim;:</p>
<ol>
<li>subject</li>
<li>body</li>
<li>thread</li>
</ol>
<p>In addition, the following three keys are associated with the attributes of the &MESSAGE; stanza specified in the XML schema for the 'jabber:client' namespace (the 'to' attribute is unnecessary, since it is provided by the XMPP address included in the IRI/URI):</p>
<p>The 'jabber:iq:roster' namespace provides a mechanism for managing an XMPP roster (also called a "contact list"). This namespace is defined in <cite>RFC 3921</cite>. The following actions are defined.</p>
<p>The registered querytype for adding items to the roster or editing items in the roster is "roster" (effectively there is no difference between adding and editing). An XMPP IRI/URI containing a "roster" querytype MAY also include at most one "name" key whose value maps to the 'name' attribute of the <item/> element within the 'jabber:iq:roster' namespace, and MAY contain one "group" key whose value maps to the character data of the <group/> child element of <item/>.</p>
<p>The 'jabber:iq:roster' namespace includes a mechanism for removing an XMPP roster item. The registered querytype for removing an item from the roster is "remove".</p>
<p>Closely coupled with roster management is presence subscription management. In XMPP, subscription management is handled via special values of the &PRESENCE; stanza, as described in <cite>RFC 3921</cite>. The following actions are defined</p>
<p>When an entity subscribes to another entity's presence by means of an XMPP IRI/URI, the invoked XMPP application SHOULD first send a roster add stanza as shown below (this is consistent with the recommendations in <cite>RFC 3921</cite>).</p>
<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>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>
<p>Security considerations for XMPP IRIs/URIs are specified in <cite>RFC 4622</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>
<p>This document requires no interaction with &IANA;. If in the future the IANA should wish to maintain a registry of XMPP URI/IRI query components, the XMPP Registrar will cooperate with efforts to migrate the registry from the XMPP Registrar to the IANA.</p>
<name>the name of the querytype (e.g., "pubsub")</name>
<proto>
the namespace of associated protocol output
(e.g., "http://jabber.org/protocol/pubsub")
</proto>
<desc>a natural-language description of the querytype</desc>
<doc>the document in which the querytype is specified</doc>
<keys>
<key>
<name>the name of the key (e.g., "action")</name>
<desc>a natural-language description of the key</desc>
<values>
<value>
<name>the name of a value (e.g., "subscribe")</name>
<desc>a natural-language description of the value</desc>
</value>
</values>
</key>
</keys>
</querytype>
]]></code>
<p>Note: Within the <querytype/> element, the <keys/> child element is OPTIONAL; within any given <key/> element, the <values/> child element is also OPTIONAL.</p>
<p>The registrant may register more than one querytype at a time, each contained in a separate <querytype/> element.</p>
<p>The following submission registers parameters related to the XMPP RFCs. For submissions related to XMPP extensions, refer to the relevant XMPP Extension Protocol specifications.</p>
