draft-ietf-xcon-common-data-model-26.txt   draft-ietf-xcon-common-data-model-27.txt 
XCON O. Novo XCON O. Novo
Internet-Draft G. Camarillo Internet-Draft G. Camarillo
Intended status: Standards Track Ericsson Intended status: Standards Track Ericsson
Expires: October 21, 2011 D. Morgan Expires: October 29, 2011 D. Morgan
Fidelity Investments Fidelity Investments
J. Urpalainen J. Urpalainen
Nokia Nokia
April 19, 2011 April 27, 2011
Conference Information Data Model for Centralized Conferencing (XCON) Conference Information Data Model for Centralized Conferencing (XCON)
draft-ietf-xcon-common-data-model-26.txt draft-ietf-xcon-common-data-model-27.txt
Abstract Abstract
[RFC5239] defines the idea of a centralized conferencing (XCON) as an [RFC5239] defines the idea of a centralized conferencing (XCON) as an
association of participants with a central focus. The state of a association of participants with a central focus. The state of a
conference is represented by a conference object. This document conference is represented by a conference object. This document
defines an Extensible Markup Language (XML)-based conference defines an Extensible Markup Language (XML)-based conference
information data model to be used for conference objects. A information data model to be used for conference objects. A
conference information data model is designed to convey information conference information data model is designed to convey information
about the conference and about participation in the conference. The about the conference and about participation in the conference. The
skipping to change at page 1, line 44 skipping to change at page 1, line 44
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 21, 2011. This Internet-Draft will expire on October 29, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 11 skipping to change at page 3, line 11
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 7 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 7
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.1. Data Model Format . . . . . . . . . . . . . . . . . . . . 7 3.1. Data Model Format . . . . . . . . . . . . . . . . . . . . 7
3.2. Data Model Namespace . . . . . . . . . . . . . . . . . . . 7 3.2. Data Model Namespace . . . . . . . . . . . . . . . . . . . 8
3.3. The Conference Object Identifier . . . . . . . . . . . . . 8 3.3. The Conference Object Identifier . . . . . . . . . . . . . 8
3.3.1. Conference Object URI Definition . . . . . . . . . . . 10 3.3.1. Conference Object URI Definition . . . . . . . . . . . 10
3.3.2. Normalization and Conference Object URI Comparison . . 10 3.3.2. Normalization and Conference Object URI Comparison . . 10
3.4. Data Model Structure . . . . . . . . . . . . . . . . . . . 10 3.4. Data Model Structure . . . . . . . . . . . . . . . . . . . 10
4. Data Model Definition . . . . . . . . . . . . . . . . . . . . 11 4. Data Model Definition . . . . . . . . . . . . . . . . . . . . 11
4.1. <conference-info> . . . . . . . . . . . . . . . . . . . . 15 4.1. <conference-info> . . . . . . . . . . . . . . . . . . . . 15
4.2. <conference-description> . . . . . . . . . . . . . . . . . 15 4.2. <conference-description> . . . . . . . . . . . . . . . . . 15
4.2.1. <language> . . . . . . . . . . . . . . . . . . . . . . 16 4.2.1. <language> . . . . . . . . . . . . . . . . . . . . . . 16
4.2.2. <display-text> . . . . . . . . . . . . . . . . . . . . 16 4.2.2. <display-text> . . . . . . . . . . . . . . . . . . . . 16
4.2.3. <subject> . . . . . . . . . . . . . . . . . . . . . . 16 4.2.3. <subject> . . . . . . . . . . . . . . . . . . . . . . 16
skipping to change at page 7, line 42 skipping to change at page 7, line 42
such extensions include scheduling elements, media control elements, such extensions include scheduling elements, media control elements,
floor control elements, non-SIP URIs, and addition of localization floor control elements, non-SIP URIs, and addition of localization
extensions to text elements. This data model can be used by extensions to text elements. This data model can be used by
conference servers providing different types of basic conferences. conference servers providing different types of basic conferences.
It is expected that this data model can be further extended with new It is expected that this data model can be further extended with new
elements in the future in order to implement additional advanced elements in the future in order to implement additional advanced
features. features.
3.1. Data Model Format 3.1. Data Model Format
A conference object document is an XML [W3C.REC-xml-20001006] A conference object document is an XML [W3C.REC-xml-20081126]
document that MUST be well formed and SHOULD be valid. Conference document. Conference object documents MUST be based on Extensible
object documents MUST be based on Extensible Markup Language (XML) Markup Language (XML) 1.0 and SHOULD be encoded using UTF-8.
1.0 and SHOULD be encoded using UTF-8.
The normative description of the syntax of the conference object
document, for use by implementors of parsers and generators, is found
in the RelaxNG schema provided in Section 5. Compliant messages MUST
meet the requirements of that schema.
3.2. Data Model Namespace 3.2. Data Model Namespace
This specification defines a new namespace specification for This specification defines a new namespace specification for
identifying the elements defined in the data model. This namespace identifying the elements defined in the data model. This namespace
is as follows: is as follows:
urn:ietf:params:xml:ns:xcon-conference-info urn:ietf:params:xml:ns:xcon-conference-info
3.3. The Conference Object Identifier 3.3. The Conference Object Identifier
skipping to change at page 58, line 40 skipping to change at page 58, line 40
[RFC4855] Casner, S., "Media Type Registration of RTP Payload [RFC4855] Casner, S., "Media Type Registration of RTP Payload
Formats", RFC 4855, February 2007. Formats", RFC 4855, February 2007.
[RFC5018] Camarillo, G., "Connection Establishment in the Binary [RFC5018] Camarillo, G., "Connection Establishment in the Binary
Floor Control Protocol (BFCP)", RFC 5018, September 2007. Floor Control Protocol (BFCP)", RFC 5018, September 2007.
[RFC5646] Phillips, A. and M. Davis, "Tags for Identifying [RFC5646] Phillips, A. and M. Davis, "Tags for Identifying
Languages", BCP 47, RFC 5646, September 2009. Languages", BCP 47, RFC 5646, September 2009.
[W3C.REC-xml-20001006] [W3C.REC-xml-20081126]
Bray, T., Sperberg-McQueen, C., Paoli, J., and E. Maler, Yergeau, F., Sperberg-McQueen, C., Paoli, J., Maler, E.,
"Extensible Markup Language (XML) 1.0 (Second Edition)", and T. Bray, "Extensible Markup Language (XML) 1.0 (Fifth
World Wide Web Consortium FirstEdition REC-xml-20001006, Edition)", World Wide Web Consortium Recommendation REC-
October 2000, xml-20081126, November 2008,
<http://www.w3.org/TR/2000/REC-xml-20001006>. <http://www.w3.org/TR/2008/REC-xml-20081126>.
Appendix A. Non-Normative RELAX NG Schema in XML Syntax Appendix A. Non-Normative RELAX NG Schema in XML Syntax
<?xml version="1.0" encoding="UTF-8" ?> <?xml version="1.0" encoding="UTF-8" ?>
<grammar <grammar
ns="urn:ietf:params:xml:ns:conference-info" ns="urn:ietf:params:xml:ns:conference-info"
xmlns="http://relaxng.org/ns/structure/1.0" xmlns="http://relaxng.org/ns/structure/1.0"
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info" xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info"
datatypeLibrary="http://www.w3.org/2001/XMLSchema-datatypes"> datatypeLibrary="http://www.w3.org/2001/XMLSchema-datatypes">
<start> <start>
 End of changes. 7 change blocks. 
15 lines changed or deleted 19 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/