moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-25 10:42:19 -05:00
Code Issues Releases Wiki Activity

Model of MIX core and additonal specs;

Browse Source
This commit is contained in:
Steve Kille 2017-02-08 14:04:17 +00:00 committed by Sam Whited
parent f462915ed9
commit ab6eefa510
1 changed files with 13 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
xep-0369.xml
View File

@ -42,10 +42,13 @@
<initials>sek</initials> <initials>sek</initials>
<remark><p> <remark><p>
Update after Brussels Summit; Update after Brussels Summit;
Remove Explicit Client Activation and replace with client capability discovery; Remove Explicit Client Activation and replace with client capability discovery (summit 3);
Limit Indirect to Join/Leave; Limit Indirect to Join/Leave;
Clarify Server use of Disco of Client; Clarify Server use of Disco of Client;
Add MIX capability information to Roster; Add MIX capability information to Roster (summit 10);
MIX as Core Spec (summit 1);
Clarifications of password control, voice and name/description (summit 4/5/6)
Removal of Subject and reference future Sticky Messages XEP (summit 7);
</p></remark> </p></remark>
</revision> </revision>
<revision> <revision>
@ -250,6 +253,11 @@
</section1> </section1>
<section1 topic='Concepts' anchor='concepts'> <section1 topic='Concepts' anchor='concepts'>
<section2 topic="Specification Appproach" anchor="concepts-approach">
<p>
MIX will enable a wide range of auxiliary services. The goal of the MIX specification is to set out the core capabilities needed for MIX. It is anticipated that additional XEPs will be written to extend the core MIX, and the core MIX specification notes some areas where this may happen. This approach will avoid the core MIX specification becoming unduly large. Profiles referencing sets of related MIX XEPs may be developed in the future.
</p>
</section2>
<section2 topic="Core Concepts" anchor="concepts-core"> <section2 topic="Core Concepts" anchor="concepts-core">
<p>The following concepts underlie the design of MIX.</p> <p>The following concepts underlie the design of MIX.</p>
<ol> <ol>
@ -2295,7 +2303,9 @@ the participant is not be subscribed to all nodes associated with the channel (i
</p> </p>
<example caption="Roster Item Encoding of a MIX Channel"><![CDATA[ <example caption="Roster Item Encoding of a MIX Channel"><![CDATA[
<item jid='romeo@example.net'/ channel='true' xmlns='urn:xmpp:mix:0'/> <item jid='romeo@example.net'>
<channel xmlns=‘urn:xmpp:mix:0'/>
</item>
]]></example> ]]></example>
<p> <p>