%ents; ]>
User Gaming This document defines an XMPP protocol extension for communicating information about the games a user plays. &LEGALNOTICE; 0196 Experimental Standards Track Standards JIG XMPP Core XMPP IM JEP-0060 JEP-0163 gaming &stpeter; 0.1 2006-08-30 psa

Initial JEP version; added several more fields.

 0.0.1 2006-08-28 psa

First draft.

&jep0060; and &jep0163; 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 games a user plays. This information may be of interest to a user's contacts and can also be used in social networking applications.

Information about games is provided by the user (or automated integration with gaming systems) and is propagated on the network by the user's client. The information container for gaming data is a <game/> element that is qualified by the 'http://jabber.org/protocol/gaming' namespace. The game information itself is provided as the XML character data of the following children of the <game/> element:

Element Description Example Datatype Inclusion
character_name The name of the user's character in the game Stentor xs:string OPTIONAL
character_profile A URI for a profile of the user's character http://wow.example.com/profile.html?12345 xs:anyURI OPTIONAL
name The name of the game Worlds of Warfare xs:string REQUIRED
level The user's level in the game 66 xs:string OPTIONAL
server_address The hostname or IP address of the server where the user is playing wow6.example.com xs:string OPTIONAL
server_name The name of the server where the user is playing WOW Example xs:string OPTIONAL
uri A URI for the game or relevant gaming service http://wow.example.com/ xs:anyURI OPTIONAL

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

When a user starts playing a game, its client may publish that fact to a special pubsub or PEP node (if a PEP node, the NodeID is "http://jabber.org/protocol/gaming"). The gaming information SHOULD be communicated and transported by means of the JEP-0060 protocol, especially the subset specified in JEP-0163 (as shown in the following examples). Because gaming 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.

chess http://www.chesspark.com/ ]]>

The gaming information is then delivered to all subscribers:

chess http://www.chesspark.com/ . . . ]]>

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

]]> . . . ]]>

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

This document requires no interaction with &IANA;.

The ®ISTRAR; shall include 'http://jabber.org/protocol/gaming' in its registry of protocol namespaces.

 ]]>