From 3a2e728f1d6a71041d119c37b111f3d5c408d069 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Fri, 3 Apr 2009 03:27:11 +0000 Subject: [PATCH] initial published version git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@2962 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0264.xml | 209 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 209 insertions(+) create mode 100644 xep-0264.xml diff --git a/xep-0264.xml b/xep-0264.xml new file mode 100644 index 00000000..42b974db --- /dev/null +++ b/xep-0264.xml @@ -0,0 +1,209 @@ + + +%ents; +]> + + +
+ File Transfer Thumbnails + This specification defines a way for a client supply a preview image for a file transfer. + &LEGALNOTICE; + 0264 + Experimental + Standards Track + Standards + Council + + XMPP Core + XEP-0096 + XEP-0231 + + + + thumbs + + Marcus + Ludblad + ml@update.uu.se + mlundblad@jabber.org + + + 0.1 + 2009-04-02 + psa +

Initial published version.

 + + + 0.0.3 + 2009-03-10 + ml +

Split use-case section into "Introduction", "Requirements", and "Use case".

+ + + + 0.0.2 + 2009-02-25 + ml +

Removed service disovery. +Added missing namespace on thumnail elements.

+ + + + 0.0.1 + 2009-02-23 + ml +

First draft.

 + +
+ +

The current methods for file transfers include basic meta data about the +file being offered (name, size, and date). There currently is no way to provide an image thumbnail for files such as photos.

+ + +

This documents defines a way to include a thumbnail image as an additional metadata in a file transfer.

+ + +

When a client wishes to supply a thumbnail in a transfer offer, it can do so by including an extra ]]> element as show in the following exaples.

+ + + + + + + + + + + + + + + + ]]> + +

The receiver MAY now request the data using the protocol defined in &xep0231;.

+ + + + + + + This is a test. If this were a real file... + + + + + ... + + + +]]> + + +

The following attributes are defined for the <thumbnail/> element.

+ + + + + + + + + + + + + + + + + + + + + + + + + + +
AttributeDescriptionInclusion
cidA Content-ID that can be mapped to a cid: URL as specified in &rfc2111;. The 'cid' value SHOULD be of the form algo+hash@bob.xmpp.org, where the "algo" is the hashing algorithm used (e.g., "sha1" for the SHA-1 algorithm as specified in &rfc3174;) and the "hash" is the hex output of the algorithm applied to the binary data itself.REQUIRED
mime-typeThe value of the 'mime-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.RECOMMENDED
widthThe intended display width of the thumbnail image. Used as a hint for the receiving client to prepare i.e. a dialog window.OPTIONAL
heightThe intended display height of the thumbnail image. Used as a hint for the receiving client to prepare i.e. a dialog window.OPTIONAL
+ + + + +

The inclusion of an image thumbnail may leak information about a transfer +otherwise taking place on an e2e encrypted file transfer stream. A client MAY +wish to not include a thumbnail.

+ + +

This document requires no interaction with &IANA;.

+ + + +

This specification defines the following XML namespace:

+
    +
  • urn:xmpp:thumbs:0
    • +
+

The ®ISTRAR; includes this namespace in the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.

+ + + &NSVER; + + + + + + + + + + The protocol documented by this schema is defined in + xxx + + + + + + + + + + + + + ]]> + +