summaryrefslogtreecommitdiff
path: root/spec
diff options
context:
space:
mode:
authorXavier Claessens <xclaesse@gmail.com>2011-11-07 15:54:17 +0100
committerXavier Claessens <xclaesse@gmail.com>2011-11-07 15:54:17 +0100
commitbe8d9703007fd13f56392dedc7ecae206cb9a4ad (patch)
tree15080960d860e5fb73e5d58d803f512ffdf03e2b /spec
parentd919bdce7eb7f9f1f0e90e31236bd4c886d35df8 (diff)
Call1: Clarify interfaces that may implement Mute iface
Diffstat (limited to 'spec')
-rw-r--r--spec/Call_Content.xml9
-rw-r--r--spec/Call_Interface_Mute.xml8
-rw-r--r--spec/Call_Stream.xml7
3 files changed, 15 insertions, 9 deletions
diff --git a/spec/Call_Content.xml b/spec/Call_Content.xml
index e97e98fc..12061a29 100644
--- a/spec/Call_Content.xml
+++ b/spec/Call_Content.xml
@@ -23,16 +23,17 @@
<interface name="org.freedesktop.Telepathy.Call1.Content"
tp:causes-havoc="experimental">
<tp:added version="0.19.0">(draft 1)</tp:added>
- <tp:requires
- interface="org.freedesktop.Telepathy.Call1.Interface.Mute"/>
<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
- This object represents one Content inside a <tp:dbus-ref
+ <p>This object represents one Content inside a <tp:dbus-ref
namespace="ofdT.Channel.Type">Call1</tp:dbus-ref>. For
example, in an audio/video call there would be one audio content
and one video content. Each content has one or more <tp:dbus-ref
namespace="ofdT.Call1">Stream</tp:dbus-ref> objects which
- represent the actual transport to one or more remote contacts.
+ represent the actual transport to one or more remote contacts.</p>
+ <p>For protocols that support muting all streams of a given content
+ separately, this object MAY also implement the <tp:dbus-ref
+ namespace="ofdT.Call1.Interface">Mute</tp:dbus-ref> interface</p>
</tp:docstring>
<method name="Remove" tp:name-for-bindings="Remove">
diff --git a/spec/Call_Interface_Mute.xml b/spec/Call_Interface_Mute.xml
index e0089720..1202383f 100644
--- a/spec/Call_Interface_Mute.xml
+++ b/spec/Call_Interface_Mute.xml
@@ -20,9 +20,11 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
<interface name="org.freedesktop.Telepathy.Call1.Interface.Mute" tp:causes-havoc="experimental">
<tp:added version="0.19.6">(draft version, not API-stable)</tp:added>
- <tp:xor-requires interface="org.freedesktop.Telepathy.Channel.Type.Call1"/>
- <tp:xor-requires interface="org.freedesktop.Telepathy.Call1.Content"/>
- <tp:xor-requires interface="org.freedesktop.Telepathy.Call1.Stream"/>
+ <tp:xor-requires>
+ <tp:requires interface="org.freedesktop.Telepathy.Channel.Type.Call1"/>
+ <tp:requires interface="org.freedesktop.Telepathy.Call1.Content"/>
+ <tp:requires interface="org.freedesktop.Telepathy.Call1.Stream"/>
+ </tp:xor-requires>
<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
<p>Interface for calls which may be muted. This only makes sense
diff --git a/spec/Call_Stream.xml b/spec/Call_Stream.xml
index 2693f530..b71dacdb 100644
--- a/spec/Call_Stream.xml
+++ b/spec/Call_Stream.xml
@@ -25,11 +25,14 @@
<tp:added version="0.19.0">(draft 1)</tp:added>
<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
- One stream inside a <tp:dbus-ref
+ <p>One stream inside a <tp:dbus-ref
namespace="ofdT.Call1">Content</tp:dbus-ref>. A stream is
a single flow of packets to and from a single remote endpoint.
If your call connects to multiple people, you could have
- multiple streams.
+ multiple streams.</p>
+ <p>For protocols that support muting streams separately, this object MAY
+ also implement the <tp:dbus-ref
+ namespace="ofdT.Call1.Interface">Mute</tp:dbus-ref> interface</p>
</tp:docstring>
<method name="SetSending" tp:name-for-bindings="Set_Sending">