CLUE Working Group R. Presta Internet-Draft S P. Romano Intended status: Informational University of Napoli Expires: September 9, 2013 March 8, 2013 An XML Schema for the CLUE data model draft-presta-clue-data-model-schema-03 Abstract This document provides an XML schema file for the definition of CLUE data model types. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on September 9, 2013. Copyright Notice Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents Presta & Romano Expires September 9, 2013 [Page 1] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. . . . . . . . . . . . . . . . . . . . . . . . 13 5. . . . . . . . . . . . . . . . . . . . . . . . . . 13 6. . . . . . . . . . . . . . . . . . . . . . . . 13 7. . . . . . . . . . . . . . . . . . . . . . . . 14 8. . . . . . . . . . . . . . . . . . . . . . . 14 9. . . . . . . . . . . . . . . . . . . . . . . 14 10. . . . . . . . . . . . . . . . . . . . . . . . . 14 10.1. . . . . . . . . . . . . . . . . . . . . . 15 10.2. . . . . . . . . . . . . . . . . . . . 15 10.3. . . . . . . . . . . . . . . . . . . . . . 16 10.4. . . . . . . . . . . . . . . . . . . 16 10.4.1. . . . . . . . . . . . . . . . . . . . 17 10.4.2. . . . . . . . . . . . . . . . . . . . . 18 10.5. . . . . . . . . . . . . . . . . . 18 10.6. . . . . . . . . . . . . . . . . . . . . . . 19 10.7. . . . . . . . . . . . . . . . . . . . . . . . 19 10.8. . . . . . . . . . . . . . . . . . . . . . . . . . 19 10.9. . . . . . . . . . . . . . . . . . . . . . . . . 19 10.10. . . . . . . . . . . . . . . . . . . . . . . . 20 10.11. . . . . . . . . . . . . . . . . . . . . . . . . 20 10.12. . . . . . . . . . . . . . . . . . . . . . . . 20 10.13. . . . . . . . . . . . . . . . . . . 20 10.14. . . . . . . . . . . . . . . . . . . . . . . . 20 10.15. captureID attribute . . . . . . . . . . . . . . . . . . . 21 11. Audio captures . . . . . . . . . . . . . . . . . . . . . . . . 21 11.1. . . . . . . . . . . . . . . . . . . 21 11.2. . . . . . . . . . . . . . . . . . . . . . . 22 12. Video captures . . . . . . . . . . . . . . . . . . . . . . . . 22 12.1. . . . . . . . . . . . . . . . . . . . 23 12.2. . . . . . . . . . . . . . . . . . . . . . 23 13. Text captures . . . . . . . . . . . . . . . . . . . . . . . . 24 14. . . . . . . . . . . . . . . . . . . . . . . . . 24 14.1. (was:) . . . . . . . . . . . . . 25 14.2. . . . . . . . . . . . . . . . . . . . . . 26 14.3. sceneID attribute . . . . . . . . . . . . . . . . . . . . 26 14.4. scale attribute . . . . . . . . . . . . . . . . . . . . . 26 15. . . . . . . . . . . . . . . . . . . . . . . . . . 27 15.1. . . . . . . . . . . . . . . . . . . . 27 15.2. . . . . . . . . . . . . . . . . . . . . 28 15.3. sceneEntryID attribute . . . . . . . . . . . . . . . . . 29 15.4. mediaType attribute . . . . . . . . . . . . . . . . . . . 29 16. . . . . . . . . . . . . . . . . . . . . . . . . . . 29 16.1. . . . . . . . . . . . . . . . . . . . . . 29 16.2. . . . . . . . . . . . . . . . . . . . . . 29 16.3. encodingID attribute . . . . . . . . . . . . . . . . . . 30 Presta & Romano Expires September 9, 2013 [Page 2] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 17. Audio encodings . . . . . . . . . . . . . . . . . . . . . . . 30 18. Video encodings . . . . . . . . . . . . . . . . . . . . . . . 30 18.1. . . . . . . . . . . . . . . . . . . . . . . . 31 18.2. . . . . . . . . . . . . . . . . . . . . . . . 31 18.3. . . . . . . . . . . . . . . . . . . . . . 31 19. H26X encodings . . . . . . . . . . . . . . . . . . . . . . . . 31 20. . . . . . . . . . . . . . . . . . . . . . . . 32 20.1. . . . . . . . . . . . . . . . . . . . 32 20.2. . . . . . . . . . . . . . . . . . . . . . . 33 20.3. . . . . . . . . . . . . . . . . . . . . 33 20.4. encodingGroupID attribute . . . . . . . . . . . . . . . . 33 21. . . . . . . . . . . . . . . . . . . . . . . 33 21.1. . . . . . . . . . . . . . . . . . . . . . 34 21.2. . . . . . . . . . . . . . . . . . . . . 34 22. . . . . . . . . . . . . . . . . . . . . . . 34 22.1. . . . . . . . . . . . . . . . . . . . . 34 22.2. . . . . . . . . . . . . . . . . . . . . . . 34 23. . . . . . . . . . . . . . . . . . . . . . . . . . . 34 24. Sample XML file . . . . . . . . . . . . . . . . . . . . . . . 35 25. Diff with unofficial -02 version . . . . . . . . . . . . . . . 44 26. Diff with -02 version . . . . . . . . . . . . . . . . . . . . 46 27. Informative References . . . . . . . . . . . . . . . . . . . . 46 Presta & Romano Expires September 9, 2013 [Page 3] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 1. Introduction This document provides an XML schema file for the definition of CLUE data model types. The schema is based on information contained in [I-D.ietf-clue-framework] and also relates to the data model sketched in [I-D.romanow-clue-data-model]. It encodes information and constraints defined in the aforementioned documents in order to provide a formal representation of the concepts therein presented. The schema definition is intended to be modified according to changes applied to the above mentioned CLUE documents. The document actually represents a strawman proposal aiming at the definition of a coherent structure for all the information associated with the description of a telepresence scenario. 2. Terminology [TBD] Copy text from the framework document. 3. XML Schema This section contains the proposed CLUE data model schema definition. The element and attribute definitions are formal representation of the concepts needed to describe the capabilities of a media provider and the current streams it is transmitting within a telepresence session. The main groups of information are: : the list of media captures available (Section 4) : the list of individual encodings (Section 5) : the list of encodings groups (Section 6) : the list of capture scenes (Section 7) : the list of simultaneous capture sets(Section 8) : the list of instantiated capture encodings (Section 9) All of the above refers to concepts that have been introduced in [I-D.ietf-clue-framework] and [I-D.romanow-clue-data-model] and Presta & Romano Expires September 9, 2013 [Page 4] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 further detailed in threads on the mailing list as well as in the following of this document. Presta & Romano Expires September 9, 2013 [Page 5] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 Presta & Romano Expires September 9, 2013 [Page 6] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 Presta & Romano Expires September 9, 2013 [Page 7] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 Presta & Romano Expires September 9, 2013 [Page 8] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 Presta & Romano Expires September 9, 2013 [Page 9] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 Presta & Romano Expires September 9, 2013 [Page 10] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 Presta & Romano Expires September 9, 2013 [Page 11] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 Presta & Romano Expires September 9, 2013 [Page 12] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 Following sections describe the XML schema in more detail. 4. represents the list of one ore more media captures available on the media provider's side. Each media capture is represented by a element (Section 10). 5. represents the list of individual encodings available on the media provider's side. Each individual encoding is represented by an element (Section 16). 6. represents the list of the encoding groups organized on the media provider's side. Each encoding group is represented by Presta & Romano Expires September 9, 2013 [Page 13] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 a element (Section 20). 7. represents the list of the capture scenes organized on the media provider's side. Each capture scene is represented by a element. (Section 14). 8. contains the simultaneous sets indicated by the media provider. Each simultaneous set is represented by a element. (Section 21). 9. is a list of capture encodings. It can represents the list of the desired capture encodings indicated by the media consumer or the list of instantiated captures on the provider's side. Each capture encoding is represented by a element. (Section 22). 10. According to the CLUE framework, a media capture is the fundamental representation of a media flow that is available on the provider's side. Media captures are characterized with a set of features that are independent from the specific type of medium, and with a set of feature that are media-specific. We design the media capture type as an abstract type, providing all the features that can be common to all media types. Media-specific captures, such as video captures, audio captures and others, are specialization of that media capture type, as in a typical generalization-specialization hierarchy. The following is the XML Schema definition of the media capture type: Presta & Romano Expires September 9, 2013 [Page 14] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 10.1. is a mandatory field specifying the media type of the capture ("audio", "video", "text",...). 10.2. is a mandatory field containing the identifier of the capture scene the media capture belongs to. Indeed, each media capture must be associated with one and only capture scene. When a media capture is spatially definible, some spatial information is provided along with it in the form of point coordinates (see Section 10.4). Such coordinates refers to the space of coordinates defined for the capture scene containing the capture. Presta & Romano Expires September 9, 2013 [Page 15] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 10.3. is a mandatory field containing the identifier of the encoding group the media capture is associated with. 10.4. Media captures are divided into two categories: non spatially definible captures and spatially definible captures. Non spatially definible captures are those that do not capture parts of the telepresence room. Capture of this case are for example those related to registrations, text captures, DVDs, registered presentation, or external streams, that are played in the telepresence room and transmitted to remote sites. Spatially definible captures are those that capture part of the telepresence room. The captured part of the telepresence room is described by means of the element. This is the definition of the spatial information type: The contains the coordinates of the capture device that is taking the capture, as well as, optionally, the pointing direction (see Section 10.4.1). It is a mandatory field when the media capture is spatially definible, independently from the media type. The is an optional field containing four points defining the captured area represented by the capture (see Section 10.4.2). Presta & Romano Expires September 9, 2013 [Page 16] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 10.4.1. The element is used to represent the position and the line of capture of a capture device. The XML Schema definition of the element type is the following: The point type contains three spatial coordinates ("x","y","z") representing a point in the space associated with a certain capture scene. The capture point type extends the point type, i.e., it is represented by three coordinates identifying the position of the capture device, but can add further information. Such further information is conveyed by the , which is another point-type element representing the "point on line of capture", that gives the pointing direction of the capture device. If the point of capture is not specified, it means the consumer should not assume anything about the spatial location of the capturing device. The coordinates of the point on line of capture MUST NOT be identical Presta & Romano Expires September 9, 2013 [Page 17] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 to the capture point coordinates. If the point on line of capture is not specified, no assumptions are made about the axis of the capturing device. 10.4.2. is an optional element that can be contained within the spatial information associated with a media capture. It represents the spatial area captured by the media capture. The XML representation of that area is provided through a set of four point-type element, , , , and , as it can be seen from the following definition: , , , and should be co- planar. For a switched capture that switches between different sections within a larger area, the area of capture should use coordinates for the larger potential area. By comparing the capture area of different media captures within the same capture scene, a consumer can determine the spatial relationships between them and render them correctly. If the area of capture is not specified, it means the Media Capture is not spatially related to any other media capture. 10.5. When media captures are non spatially definible, they are marked with the boolean element set to "true". Presta & Romano Expires September 9, 2013 [Page 18] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 10.6. is used to provide optionally human-readable textual information. It is used to describe media captures, capture scenes and capture scene entries. A media capture can be described by using multiple elements, each one providing information in a different language. Indeed, the element definition is the following: As it can be seen, is a string element with an attribute ("lang") indicating the language used in the textual description. 10.7. ([I-D.groves-clue-capture-attr]) is an optional integer field indicating the importance of a media capture according to the media provider's perspective. It can be used on the receiver's side to automatically identify the most "important" contribution available from the media provider. [edt note: no final consensus has been reached on the adoption of such media capture attribute.] 10.8. is an optional element containing the language used in the capture, if any. The purpose of the element could match the one of the "language" attribute proposed in [I-D.groves-clue-capture-attr]. 10.9. is an optional string element. It contains enumerated values describing the "role" of the media capture according to what Presta & Romano Expires September 9, 2013 [Page 19] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 is envisionend in [RFC4796] ("slides", "speaker", "sl", "main", "alt"). The values for this attribute are the same as the mediacnt values for the content attribute in [RFC4796]. This attribute can list multiple values, for example "main, speaker". [edt note: a better XML Schema definition for that element will soon be defined.] 10.10. is a boolean element which indicates whether or not the media capture represents the most appropriate subset of a "whole". What is "most appropriate" is up to the provider and could be the active speaker, a lecturer or a VIP. [edt note: :(] 10.11. is an optional boolean element indicating wheter or not the capture device originating the capture moves during the telepresence session. That optional boolean element has the same purpose of the dynamic attribute proposed in [I-D.groves-clue-capture-attr]. [edt note: There isn't yet final consensus about that element.] 10.12. is an optional boolean element indicating wheter or not the media capture is a mix (audio) or composition (video) of streams. This attribute is useful for a media consumer for example to avoid nesting a composed video capture into another composed capture or rendering. 10.13. The optional contains an unsigned integer indicating the maximum number of capture encodings that can be simultaneously active for the media capture. If absent, this parameter defaults to 1. The minimum value for this attribute is 1. The number of simultaneous capture encodings is also limited by the restrictions of the encoding group the media capture refers to my means of the element. 10.14. The optional element contains the value of the ID attribute of the media capture it refers to. The media capture Presta & Romano Expires September 9, 2013 [Page 20] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 marked with a element can be for example the translation of a main media capture in a different language. The element could be interpreted the same manner of the supplementary information attribute proposed in [I-D.groves-clue-capture-attr] and further discussed in http://www.ietf.org/mail-archive/web/clue/current/msg02238.html. [edt note: There isn't yet final consensus about that element.] 10.15. captureID attribute The "captureID" attribute is a mandatory field containing the identifier of the media capture. 11. Audio captures Audio captures inherit all the features of a generic media capture and present further audio-specific characteristics. The XML Schema definition of the audio capture type is reported below: Audio-specific information about the audio capture is contained in (Section 11.1) and in (Section 11.2). 11.1. The optional element is a field with enumerated values ("mono" and "stereo") which describes the method of encoding used for audio. A value of "mono" means the audio capture has one channel. A value of "stereo" means the audio capture has two audio channels, left and right. A single stereo capture is different from Presta & Romano Expires September 9, 2013 [Page 21] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 two mono captures that have a left-right spatial relationship. A stereo capture maps to a single RTP stream, while each mono audio capture maps to a separate RTP stream. The XML Schema definition of the element type is provided below: 11.2. The element is an optional field describing the characteristic of the mic capturing the audio signal. It can contains the enumerated values listed below: 12. Video captures Video captures, similarly to audio captures, extend the information of a generic media capture with video-specific features, such as (Section 12.1) and (Section 12.2). The XML Schema representation of the video capture type is provided in the following: Presta & Romano Expires September 9, 2013 [Page 22] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 12.1. If a video capture has a native aspect ratio (for instance, it corresponds to a camera that generates 4:3 video), then it can be supplied as a value of the element, in order to help rendering. 12.2. The element is a boolean element indicating that there is text embedded in the video capture. The language used in such embedded textual description is reported in "lang" attribute. The XML Schema definition of the element is: The element could correspond to the embedded-text attribute introduced in [I-D.groves-clue-capture-attr] Presta & Romano Expires September 9, 2013 [Page 23] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 [edt note: no final consensus has been reached yet about the adoption of such element] 13. Text captures Also text captures can be described by extending the generic media capture information, similarly to audio captures and video captures. The XML Schema representation of the text capture type is currently lacking text-specific information, as it can be seen by looking at the definition below: 14. A media provider organizes the available capture in capture scenes in order to help the receiver both in the rendering and in the selection of the group of captures. Capture scenes are made of capture scene entries, that are set of media captures of the same media type. Each capture scene entry represents an alternative to represent completely a capture scene for a fixed media type. The XML Schema representation of a element is the following: Presta & Romano Expires September 9, 2013 [Page 24] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 The element can contain zero or more textual elements, defined as in Section 10.6. Besides , there are two other fields: (Section 14.1), describing the coordinate space which the media captures of the capture scene refer to, and (Section 14.2), the list of the capture scene entries. 14.1. (was:) The describes a bounding volume for the spatial information provided alongside spatially-definible media capture associated with the considered capture scene. Such volume is described as an arbitrary hexahedrons with eight points (, , , , , , , and ). The coordinate system is Cartesian X, Y, Z with the origin at a spatial location of the media provider's choosing. The media provider must use the same coordinate system with same scale and origin for all media capture coordinates within the same capture scene. [edt note: this is just a place holder, the definition of the bounding volume has to be discussed] Presta & Romano Expires September 9, 2013 [Page 25] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 14.2. The element is a mandatory field of a capture scene containing the list of scene entries. Each scene entry is represented by a element (Section 15). 14.3. sceneID attribute The sceneID attribute is a mandatory attribute containing the identifier of the capture scene. 14.4. scale attribute The scale attribute is a mandatory attribute that specifies the scale of the coordinates provided in the capture space and in the spatial information of the media capture belonging to the considered capture scene. The scale attribute can assume three different values: "millimeters" - the scale is in millimeters. Systems which know their physical dimensions (for example professionally installed telepresence room systems) should always provide those real-world measurements. "unknown" - the scale is not necessarily millimeters, but the scale is the same for every media capture in the capture scene. Systems which don't know specific physical dimensions but still know relative distances should select "unknown" in the scale attribute of the capture scene to be described. "noscale" - there is no a common physical scale among the media captures of the capture scene. That means the scale could be different for each media capture. Presta & Romano Expires September 9, 2013 [Page 26] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 15. A element represents a capture scene entry, which contains a set of media capture of the same media type describing a capture scene. A element is characterized as follows. One or more optional elements provide human-readable information about what the scene entry contains. is defined as already seen in Section 10.6. The remaining child elements are described in the following subsections. 15.1. represents the switching policies the media provider support for the media captures contained inside a scene entry. The element contains two boolean elements: Presta & Romano Expires September 9, 2013 [Page 27] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 : if set to "true", it means that the media provider supports the site switching policy for the included media captures; : if set to "true", it means that the media provider supports the segment switching policy for the included media captures. The "site-switch" policy means all captures are switched at the same time to keep captures from the same endpoint site together. The "segment-switch" policy means different captures can switch at different times, and can be coming from different endpoints. 15.2. The is the list of the identifiers of the media captures included in the scene entry. It is an element of the captureIDListType type, which is defined as a sequence of each one containing the identifier of a media capture listed within the element: Presta & Romano Expires September 9, 2013 [Page 28] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 15.3. sceneEntryID attribute The sceneEntryID attribute is a mandatory attribute containing the identifier of the capture scene entry represented by the element. 15.4. mediaType attribute The mediaType attribute contains the media type of the media captures included in the scene entry. 16. The element represents an individual encoding, i.e., a way to encode a media capture. Individual encodings can be characterized with features that are independent from the specific type of medium, and with features that are media-specific. We design the individual encoding type as an abstract type, providing all the features that can be common to all media types. Media-specific individual encodings, such as video encodings, audio encodings and others, are specialization of that type, as in a typical generalization- specialization hierarchy. 16.1. is a mandatory field containing the name of the encoding (e.g., G711, H264, ...). 16.2. represent the maximum bitrate the media provider can instantiate for that encoding. Presta & Romano Expires September 9, 2013 [Page 29] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 16.3. encodingID attribute The encodingID attribute is a mandatory attribute containing the identifier of the individual encoding. 17. Audio encodings Audio encodings inherit all the features of a generic individual encoding and can present further audio-specific encoding characteristics. The XML Schema definition of the audio encoding type is reported below: Up to now the only audio-specific information is the element containing the media type of the media captures that can be encoded with the considered individual encoding. In the case of audio encoding, that element is forced to "audio". 18. Video encodings Similarly to audio encodings, video encodings can extend the information of a generic individual encoding with video-specific encoding features, such as , and . The element contains the media type of the media captures that can be encoded with the considered individual encoding. In the case of video encoding, that element is forced to "video". Presta & Romano Expires September 9, 2013 [Page 30] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 18.1. represents the video resolution's maximum width supported by the video encoding, expressed in pixels. [edt note: not present in -09 version of the framework doc] 18.2. representd the video resolution's maximum heith supported by the video encoding, expressed in pixels. [edt note: not present in -09 version of the framework doc] 18.3. provides the maximum frame rate supported by the video encoding for the video capture to be encoded. [edt note: not present in -09 version of the framework doc] 19. H26X encodings This is an example of how it is possible to further specialize the definition of a video individual encoding in order to cover encoding specific information. A H26X video encoding can be represented through an element inheriting the video encoding characteristics described above (Section 18) and by adding other information such as , which represent the maximum number of pixels to be processed per second;. Presta & Romano Expires September 9, 2013 [Page 31] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 [edt note: Need to be checked] 20. The element represents an encoding group, which is a set of one or more individual encodings, and parameters that apply to the group as a whole. The definition of the element is the following: In the following, the contained elements are further described. 20.1. is an optional field containing the maximum bitrate supported for all the individual encodings included in the encoding group. Presta & Romano Expires September 9, 2013 [Page 32] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 20.2. is an optional field containing the maximum number of pixel per second for all the individual encodings included in the encoding group. [edt note: Need to be checked] 20.3. is the list of the individual encoding grouped together. Each individual encoding is represented through its identifier contained within an element. 20.4. encodingGroupID attribute The encodingGroupID attribute contains the identifier of the encoding group. 21. represents a simultaneous set, i.e. a list of capture of the same type that cab be transmitted at the same time by a media provider. There are different simultaneous transmission sets for each media type. Presta & Romano Expires September 9, 2013 [Page 33] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 [edt note: need to be checked] 21.1. contains the identifier of the media capture that belongs to the simultanous set. 21.2. contains the identifier of the scene entry containing a group of capture that are able to be sent simultaneously with the other capture of the simultaneous set. 22. A is given from the association of a media capture and an individual encoding, to form a capture stream. It is defined as en element of the following type: 22.1. contains the identifier of the media capture that has been encoded to form the capture encoding. 22.2. contains the identifier of the applied individual encoding. 23. The element has been left within the XML Schema for the sake of convenience when representing a prototype of ADVERTISEMENT message (see the example section). Presta & Romano Expires September 9, 2013 [Page 34] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 24. Sample XML file The following XML document represents a schema compliant example of a CLUE telepresence scenario. There are 5 video captures: VC0: the video from the left camera VC1: the video from the central camera VC2: the video from the right camera VC3: the overall view of the telepresence room taken from the central camera VC4: the video associated with the slide stream There are 2 audio captures: AC0: the overall room audio taken from the central camera AC1: the audio associated with the slide stream presentation The captures are organized into two capture scenes: Presta & Romano Expires September 9, 2013 [Page 35] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 CS1: this scene contains captures associated with the participants that are in the telepresence room. CS2: this scene contains captures associated with the slide presentation, which is a pre-registered presentation played within the context of the telepresence session. Within the capture scene CS1, there are three scene entries available: CS1_SE1: this entry contains the partipants' video captures taken from the three cameras (VC0, VC1, VC2). CS1_SE2: this entry contains the zoomed-out view of the overall telepresence room (VC3) CS1_SE3: this entry contains the overall telepresence room audio (AC0) On the other hand, capture scene CS2 presents two scene entries: CS2_SE1: this entry contains the presentation audio stream (AC1) CS2_SE2: this entry contains the presentation video stream (VC4) There are two encoding groups: EG0 This encoding groups involves video encodings ENC0, ENC1, ENC2 EG1 This encoding groups involves audio encodings ENC3, ENC4 As to the simultaneous sets, only VC1 and VC3 cannot be transmitted simultaneously since they are captured by the same device. i.e. the central camera (VC3 is a zoomed-out view while VC1 is a focused view of the front participants). The simultaneous sets would then be the following: SS1 made by VC0, VC1, VC2, VC4, AC0, AC1 SS2 made by VC0, VC3, VC2, VC4, AC0, AC1 audio CS2 EG1 true presentation audio slide mono video CS2 EG0 true presentation video slides audio CS1 EG1 0.5 1.0 0.5 0.5 0.0 0.5 audio from the central camera mic mono figure8 video CS1 EG0 Presta & Romano Expires September 9, 2013 [Page 37] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 1.5 1.0 0.5 1.5 0.0 0.5 0.0 3.0 0.0 3.0 3.0 0.0 0.0 3.0 3.0 3.0 3.0 3.0 zoomed out view of the room video CS1 EG0 2.5 1.0 0.5 Presta & Romano Expires September 9, 2013 [Page 38] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 2.5 0.0 0.5 2.0 3.0 0.0 3.0 3.0 0.0 2.0 3.0 3.0 3.0 3.0 3.0 right camera video video CS1 EG0 1.5 1.0 0.5 1.5 0.0 0.5 Presta & Romano Expires September 9, 2013 [Page 39] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 1.0 3.0 0.0 2.0 3.0 0.0 1.0 3.0 3.0 2.0 3.0 3.0 central camera video video CS1 EG0 0.5 1.0 0.5 0.5 0.0 0.5 0.0 3.0 0.0 Presta & Romano Expires September 9, 2013 [Page 40] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 1.0 3.0 0.0 0.0 3.0 3.0 1.0 3.0 3.0 left camera video h263 4000000 video 1920 1088 h263 4000000 video 1920 1088 h263 4000000 video 1920 1088 g711 Presta & Romano Expires September 9, 2013 [Page 41] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 64000 audio g711 64000 audio 12000000 ENC0 ENC1 ENC2 12000000 ENC3 ENC4 main scene 0.0 3.0 0.0 3.0 3.0 0.0 0.0 3.0 2.0 3.0 Presta & Romano Expires September 9, 2013 [Page 42] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 3.0 2.0 0.0 3.0 0.0 3.0 3.0 0.0 0.0 3.0 2.0 3.0 3.0 2.0 participants streams VC0 VC1 VC2 room stream VC3 room audio AC0 Presta & Romano Expires September 9, 2013 [Page 43] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 presentation presentation video VC4 presentation audio AC1 VC0 VC1 VC2 VC4 AC0 AC1 VC0 VC3 VC2 VC4 AC0 AC1 25. Diff with unofficial -02 version Here the link to the unofficial -02 version: http://www.grid.unina.it/Didattica/RetiDiCalcolatori /inf/draft-presta-clue-data-model-schema-02.html Presta & Romano Expires September 9, 2013 [Page 44] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 moved from to elements. have been moved out from the blob again. Media captures should have identifiers that are valid out of the local scope of capture scenes, since a consumer should be able to require also single captures in the CONFIGURE message. This design choice reflects a bottom up approach where captures are the basis of the data model. In each media capture a reference to the capture scene containing it is provided. It identifies the space the spatial information of the media capture refers to. XML document example updated A new example, compliant with the updated schema, has been provided. language attribute added to Such optional attribute reflects the language used in the capture, if any. The purpose of the element could match the one of the language attribute proposed in [I-D.groves-clue-capture-attr]. added to The priority element has an integer value helping in specifying a media capture relative importance with respect to the other captures. That element could correspond to the priority attribute introduced in [I-D.groves-clue-capture-attr]. added to The element, if present, indicates text embedded in the video capture. The language used in such embedded textual description is also envisioned within the element itself. That element could correspond to the priority attribute introduced in [I-D.groves-clue-capture-attr] added to That optional element contains the ID of a capture the capture refers to. This is for supporting cases where there is the translation of a main capture in a different language. Such translation can be marked with a tag to refer to the main capture. This could be interpreted the same manner of the supplementary information attribute proposed in [I-D.groves-clue-capture-attr] and further discussed in http://www.ietf.org/mail-archive/web/clue/current/msg02238.html. added to That optional boolean element has the same purpose of the dynamic attribute proposed in [I-D.groves-clue-capture-attr]. It indicates if the capture device originating the capture moves during the telepresence session. Presta & Romano Expires September 9, 2013 [Page 45] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 new element definition for has a new attribute, lang, indicating the language used for the text within . is used to provide human readable information about captures, scene, and scene entries. The definitions of the corresponding XML elements (i.e., , , ) have been updated to make them able to contain more than one . In that way, they can be described in different languages. text capture added as new type of capture The element is just a place holder, since it is not characterized with any further information up to now. 26. Diff with -02 version of capture space type (was:) describes a bounding volume for the space of a capture scene as an arbitrary hexahedrons with eight points (placeholder solution). H26X encoding to be checked. Simultaneous sets The XML Schema definition of the simultaneous sets has changed. A simultaneous set is defined as a list of L media capture identifiers and M capture scene entrie identifiers, where L, M can be 0 or unbounded. Capture encoding A new XML Schema type has been added to describe capture encodings as the result of the association of a media capture, represented by its identifier, with an individual encoding, represented by its identifier as well. Clue info The element has been left within the XML Schema for the sake of convenience when representing a prototype of ADVERTISEMENT message (see the example section). Data model definitions added For each element of the datamodel a brief description has been reported to foster discussion. 27. Informative References [I-D.groves-clue-capture-attr] Groves, C., Yang, W., and R. Even, "CLUE media capture description", draft-groves-clue-capture-attr-01 (work in progress), February 2013. [I-D.ietf-clue-framework] Duckworth, M., Pepperell, A., and S. Wenger, "Framework for Telepresence Multi-Streams", Presta & Romano Expires September 9, 2013 [Page 46] Internet-Draft draft-presta-clue-data-model-schema-03 March 2013 draft-ietf-clue-framework-09 (work in progress), February 2013. [I-D.romanow-clue-data-model] Romanow, A. and A. Pepperell, "Data model for the CLUE Framework", draft-romanow-clue-data-model-01 (work in progress), June 2012. [RFC4796] Hautakorpi, J. and G. Camarillo, "The Session Description Protocol (SDP) Content Attribute", RFC 4796, February 2007. Authors' Addresses Roberta Presta University of Napoli Via Claudio 21 Napoli 80125 Italy EMail: roberta.presta@unina.it Simon Pietro Romano University of Napoli Via Claudio 21 Napoli 80125 Italy EMail: spromano@unina.it Presta & Romano Expires September 9, 2013 [Page 47]