From 7bd6a6e499384bc08a5a42afd1238913e3bf1743 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Tue, 17 Nov 2009 19:22:44 +0000 Subject: [PATCH] 1.1rc1 git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@3631 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0166.xml | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/xep-0166.xml b/xep-0166.xml index 9e6e26d7..e3e2c317 100644 --- a/xep-0166.xml +++ b/xep-0166.xml @@ -11,6 +11,7 @@ &LEGALNOTICE; 0166 Draft + Standards Track Standards Council @@ -36,6 +37,12 @@ &robmcqueen; &seanegan; &hildjj; + + 1.1rc1 + in progress, last updated 2009-11-08 + psa/jjh +

Specified handling of duplicate name attributes on content element; clarified recommended usage of Jingle when exchanging multiple content-types; declared the principle that application types ought not to be mixed beyond necessity within a single session; clarified use of the reason element in cases other than termination.

 + 1.0 2009-06-10 @@ -770,6 +777,7 @@ PENDING o-----------------------+ | ]]> +

Application types ought not to be mixed beyond necessity within a single session. Therefore the session initiation request (along with subsequent additions) will include only content-types that can be grouped together into a coherent session within a given Jingle application. For example, two parties might start an audio call but then add a video aspect to that call. If one of the parties decides to send a file to the other party as a result of discussion over the audio/video session or a text chat conversation, conceptually that is probably a separate session (unless file exchange or screen sharing or some other application type is an integral part of a broader collaboration experience and needs to be calibrated with the audio/video session).

Note: The syntax and semantics of the &DESCRIPTION;, &TRANSPORT;, and <security/> elements are out of scope for this document, since they are defined in related specifications. The syntax and semantics of the &JINGLE; and &CONTENT; elements are specified in this document under Formal Definition.

@@ -1256,13 +1264,13 @@ PENDING o-----------------------+ | name - A unique name or identifier for the content type according to the creator, which MAY have meaning to a human user in order to differentiate this content type from other content types (e.g., two content types containing video media could differentiate between "room-pan" and "slides"). + A unique name or identifier for the content type according to the creator, which MAY have meaning to a human user in order to differentiate this content type from other content types (e.g., two content types containing video media could differentiate between "room-pan" and "slides"). If there are two content types with the same value for the 'name' attribute, they shall understood as alternative definitions for the same purpose (e.g., a legacy method and a standards-based method for establishing a voice call), typically to smooth the transition from an older technology to Jingle. REQUIRED senders Which parties in the session will be generating content; the allowable values are "initiator", "none", "responder", and "both" (where the default is "both"). - REQUIRED when sending content-modify; otherwise OPTIONAL + OPTIONAL except when sending content-modify, in which case it is REQUIRED. @@ -1273,6 +1281,7 @@ PENDING o-----------------------+ |
  • The <reason/> element MAY contain a <text/> element that provides human-readable information about the reason for the action.
  • The <reason/> element MAY contain an element qualified by some other namespace that provides more detailed machine-readable information about the reason for the action.
    • +

    A <reason/> element can be included with any Jingle action, and is not limited to session termination events.

    The defined conditions are described in the following table.