From 68e1218a0fbd497d9c49343a8c1782e049d950ab Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Mon, 28 Jul 2008 00:17:15 +0000 Subject: [PATCH] 0.4 git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@2100 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0221.xml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/xep-0221.xml b/xep-0221.xml index 4cf23501..93cf180a 100644 --- a/xep-0221.xml +++ b/xep-0221.xml @@ -22,6 +22,12 @@ NOT_YET_ASSIGNED &ianpaterson; &stpeter; + + 0.4 + 2008-07-27 + psa +

Generalized text regarding inclusion of parameters in type attribute per RFC 2045.

 + 0.3 2008-06-18 @@ -49,7 +55,7 @@

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. If included, 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 MIME type SHOULD be as registered in the &ianamedia;. The 'type' attribute MAY include the codecs parameter as specified in &rfc4281;, as shown in the example of the "audio/ogg" media type in the example below.

+

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. If included, the <uri/> element MUST contain a URI that indicates the location and MUST include a 'type' attribute that specifies the MIME type of the media. As specified in &rfc2045;, the value of the 'type' attribute MUST include a top-level media type, the "/" character, and a subtype; in addition, it MAY include one or more optional parameters (e.g., the "audio/ogg" MIME type in the example shown below includes a "codecs" parameter as specified in &rfc4281;). The "type/subtype" string SHOULD be registered in the &ianamedia;, but MAY be an unregistered or yet-to-be-registered value.

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.