- From: Josh Soref <jsoref@blackberry.com>
- Date: Tue, 16 Apr 2013 21:06:33 +0000
- To: sysapps <public-sysapps@w3.org>
The description for disconnected [1] says: > The multiparty call has been disconnected and this object is invalid for call control. In this final state, the implementation MUST raise an ILLEGAL_STATE exception when any method call is attempted. Descriptions should really be informative, and shouldn't include normative (MUST) language. Note that not all methods trigger the same error state when one takes a call/conference which is in "disconnected". * `split` will trigger InvalidModificationError instead. * removeParticipant supposedly will ask the system to do work... On the subject of normatives, CallHistoryEntry Interface [2] says: "This section is non-normative." "This interface describes the properties which MUST be supported for call history entries." "For multiparty call there MUST be a separate object for each call participant, sharing the same value for the conferenceId property." Non-normative sections SHOULD NOT use RFC words.... [1] http://telephony.sysapps.org/#multiparty-steps [2] http://telephony.sysapps.org/#callhistoryentry-interface --------------------------------------------------------------------- This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
Received on Tuesday, 16 April 2013 21:07:02 UTC