%ents; ]>
User Chatting This document defines an XMPP protocol extension for communicating information about the chatrooms a user visits. &LEGALNOTICE; 0194 Experimental Standards Track Standards XMPP Core XMPP IM XEP-0060 XEP-0163 TO BE ASSIGNED &stpeter; 0.2 2007-09-14 psa

Updated in accordance with XEP-0163.

 0.1 2006-08-30 psa

Initial version.

 0.0.1 2006-08-28 psa

First draft.

&xep0060; and &xep0163; can be used to publish a wide variety of "extended presence" information about users. This document specifies an extended presence payload format that communicates information about the chatrooms a user visits. This information may be of interest to a user's contacts and can also be used in social networking applications.

Information about chatrooms is provided by the user (or automated integration with Jabber, IRC, or other systems) and is propagated on the network by the user's client. The information container for chatting data is a <room/> element that is qualified by the 'http://www.xmpp.org/extensions/xep-0194.html#ns' namespace &NSNOTE;. The chatting information itself is provided as the XML character data of the following children of the <room/> element:

Element Description Example Datatype Inclusion
name The name of the chatroom jdev xs:string OPTIONAL
topic The current topic of discussion in the room whiteboard brainstorming session xs:string OPTIONAL
uri A URI for the room (this SHOULD be an XMPP URI or IRI in accordance with &rfc4622; but MAY use some other URI scheme, such as the irc: scheme) xmpp:jdev@conference.jabber.org xs:anyURI REQUIRED

NOTE: The datatypes specified above are defined in &w3xmlschema2;.

When a user joins a room, its client may publish that fact to a special pubsub or PEP node (if a PEP node, the NodeID is "http://www.xmpp.org/extensions/xep-0194.html#ns" &NSNOTE;). The chatting information SHOULD be communicated and transported by means of the XEP-0060 protocol, especially the subset specified in XEP-0163 (as shown in the following examples). Because chatroom information is not pure presence information and can change independently of the user's availability, it SHOULD NOT be provided as an extension to the &PRESENCE; stanza type.

jdev xmpp:jdev@conference.jabber.org ]]>

The chatting information is then delivered to all subscribers:

jdev xmpp:jdev@conference.jabber.org . . . ]]>

When the user exits the room, the user's client SHOULD send an empty <room/> element to the node with the same ItemID:

]]> . . . ]]>

The chat rooms that a user visits may be sensitive. A client must provide a way for a user to configure which rooms or types of rooms will not be published (e.g., via user preferences).

This document requires no interaction with &IANA;.

Until this specification advances to a status of Draft, its associated namespace shall be "http://www.xmpp.org/extensions/xep-0194.html#ns"; upon advancement of this specification, the ®ISTRAR; shall issue a permanent namespace in accordance with the process defined in Section 4 of &xep0053;.

 ]]>