1 / 6

A Common Conference Information Data Model for XCON draft-novo-xcon-common-data-model-00.txt

A Common Conference Information Data Model for XCON draft-novo-xcon-common-data-model-00.txt. Oscar.Novo@ericsson.com. The Model. Conference Object. Conference Description (times, duration) Membership (roles, capacity, names) Signaling (protocol, direction, status) Security Information

sbrent
Download Presentation

A Common Conference Information Data Model for XCON draft-novo-xcon-common-data-model-00.txt

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. A Common Conference Information Data Model for XCON draft-novo-xcon-common-data-model-00.txt Oscar.Novo@ericsson.com

  2. The Model Conference Object • Conference Description (times, duration) • Membership (roles, capacity, names) • Signaling (protocol, direction, status) • Security Information • Floor Information • Sidebars Common Conference Information Type Conference Template type • Mixer algorithm, inputs and outputs • Floor Control • User Control Interface • User´s view • Etc

  3. Example | |--<available-media> | | |--!<entry> | | | |--<type> | | | |--<status> | | | |--<codecs> | | | | |--<entry> | |--<host-info> | |--<display-text> | |--<web-page> | |--<uris> | | |--<entry> | | | |--<uri> | | | |--<description> | | |--<entry> | | | |--<uri> | | | |--<description> |--<conference-state> | |--<allow-conference-state> | |--<user-count> | |--!<active> | |--<locked> | extension |--<users> | |--<user> | | |--<display-text> | | |--<associated-aors> | | |--<languages> | extension <conference-info> | |--<conference-description> | |--<display-text> | |--<subject> | |--<free-text> | |--<conf-uris> | | |--<entry> | | | |--<uri> | | | |--<display-text> | | | |--<purpose> | extension | |--<service-uris> | | |--<entry> | | | |--<uri> | | | |--<display-text> | | | |--<purpose> | extension Possibility to extend the XML schema with the templates or future extensions

  4. Why is important to defined the Common Conference Information Data Model • Help design the Conference Control Protocol • Help select the Conference Control Protocol • Includes information not defined in the SIPPING conference package (e.g. Security issues) • Includes information spread in many documents in one frame

  5. Extensibility of the Common Conference Information Data • Create a new namespace called common-conference-info (or XCon-conference-info for that matter) that incorporates all the conferencing elements needed in XCON to facilitate data manipulation protocols that operate on the conference object? • Use the conference-info namespaces and schemas in the sipping conferencing package and other drafts?

  6. Questions, comments?

More Related