In certain protocols that make use of &xep0004;, it can be helpful to include media data such as small images. One example of such a "using protocol" is &xep0158;. This document defines a method for including media data in a data form.

The root element for media data is <media/>. This element MUST be qualified by the "urn:xmpp:tmp:media-element' namespace &NSNOTE;. The <media/> element MUST be contained within a <field/> element qualified by the 'jabber:x:data' namespace.

If the media is an image or video then the <media/> element SHOULD include 'height' and 'width' attributes specifying the recommended display size of the media in pixels.

The <media/> element SHOULD contain at least one <uri/> element to specify the out-of-band location of the media data. Constrained execution environments prevent some clients (e.g., Web clients) from rendering media unless it has been received out-of-band. The <uri/> element MUST contain a URI that indicates the location and MUST include a 'type' atribute that specifies the MIME type (see &rfc2045;) of the media.

The <media/> element MAY also contain one or more <data/> elements for distributing the media in-band. The <data/> element MUST be qualified by the 'urn:xmpp:tmp:data-element' as defined in &xep0231;. The encoded data SHOULD NOT be larger than 8 kilobytes. If a stanza contains more than one <data/> element, the sending entity MUST take care not to trigger server-defined bandwidth limits.