Per a vote of the XMPP Council, advanced status to Draft; concurrently, the XMPP Registrar issued the urn:xmpp:media-element namespace.
Further modified examples to track changes to XEP-0231.
Modified examples to track changes to XEP-0231.
Generalized text regarding inclusion of parameters in type attribute per RFC 2045.
Changed MUST to SHOULD regarding inclusion of uri element; allowed inclusion of codecs parameter in type attribute per RFC 4281; added Security Considerations section.
Modified to reuse data element from XEP-0231.
Initial version, split off from XEP-0158.
In certain protocols that make use of Data Forms (XEP-0004)
The root element for media data is <media/>. This element MUST be qualified by the "urn:xmpp:media-element' namespace. 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.
The 'type' attribute of the <uri/> element is REQUIRED. The value of the 'type' attribute MUST match the syntax specified in RFC 2045
The cid: URI points to data that can be retrieved using the protocol described in Bits of Binary (XEP-0231)
The following example is provided only for the purpose of illustration; consult the specifications for using protocols (e.g., XEP-0158) to see canonical examples.
The ability to include arbitrary binary data implies that it is possible to send scripts, applets, images, and executable code, which may be potentially harmful. To reduce the risk of such exposure, an implementation MAY choose to not display or process such data but instead either completely ignore the data, show only the value of the 'alt' attribute (if included), or prompt a human user for approval (either explicitly via user action or implicitly via a list of approved entities from whom the user will accept binary data without per-event approval).
This document requires no interaction with the Internet Assigned Numbers Authority (IANA)
The XMPP Registrar
The protocol documented by this schema is defined in
XEP-0221: http://www.xmpp.org/extensions/xep-0221.html
]]>