Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The application/conference-info+xml document format details the data model for a conference specified in [RFC4575]. Extensions to [RFC4575] are also specified in [MS-CONFBAS]. This protocol does not introduce any new extensions to the underlying XML schema that is defined in [MS-CONFBAS]. This protocol further extends the conference data model by specifying the semantics of XML elements and attributes that are relevant to the message syntaxes defined in this protocol.
Extensions to this protocol MAY define the semantics of other elements and attributes that they depend upon. They MAY also introduce new extensions to this data model.
Note that not all of the extension element semantics defined by this protocol are exclusively limited to audio and video conference modalities. Unless otherwise specified, extensions to this protocol or other extensions to [RFC4575] and to [MS-CONFBAS] MAY define media type-specific semantics, MCU-specific semantics, or generic media-type-agnostic semantics that are broader and more general in scope than those defined in this protocol.
The cardinality of each extension element is specified in the XML schema using standard minOccurs and maxOccurs XML schema conventions. Similarly, the cardinality of each extension attribute is specified in the XML schema using standard required or optional attributes. Similarly, the namespace of each extension attribute or element is specified in the XML schema using standard conventions and is omitted here for brevity.
This section defines only the general semantics of extension XML data types out of the context of any C3P message. C3P requests, responses, and notifications MAY further define or restrict this data model. Any such restrictions are specified by their message syntaxes as needed.