From 384c3a2fa204471d205a16f810a64ee3f16ae478 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Wed, 6 Aug 2008 22:29:59 +0000 Subject: [PATCH] 0.6 git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@2138 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0221.xml | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/xep-0221.xml b/xep-0221.xml index 10c1515f..6047790c 100644 --- a/xep-0221.xml +++ b/xep-0221.xml @@ -22,6 +22,12 @@ NOT_YET_ASSIGNED &ianpaterson; &stpeter; + + 0.6 + 2008-08-06 + psa +

Further modified examples to track changes to XEP-0231.

 + 0.5 2008-08-06 @@ -61,9 +67,8 @@

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' attribute that specifies the MIME type of the media.

+

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. If the URI scheme is cid: then the identifier MUST refer to a bit of binary data as described in &xep0231;.

The 'type' attribute of the <uri/> element is REQUIRED. The value of the 'type' attribute MUST match the syntax specified in &rfc2045;. That is, the value 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.

@@ -123,14 +128,10 @@ xmlns='urn:xmpp:tmp:media-element' elementFormDefault='qualified'> - - - + -