This commit is contained in:
Peter Saint-Andre 2013-01-03 11:25:52 -07:00
parent d827aac810
commit e67fdd3a39
1 changed files with 11 additions and 4 deletions

View File

@ -9,8 +9,8 @@
<title>MUC Eventing Protocol</title>
<abstract>This specification defines semantics for using the XMPP publish-subscribe protocol to broadcast state change events associated with a Multi-User Chat (MUC) room. This profile of pubsub therefore enables a chatroom to function as a virtual pubsub service, easing the discovery of syndicated data and event notifications associated with such a room.</abstract>
&LEGALNOTICE;
<number>XXXX</number>
<status>ProtoXEP</status>
<number>0316</number>
<status>Experimental</status>
<type>Standards Track</type>
<sig>Standards JIG</sig>
<approver>Council</approver>
@ -26,6 +26,12 @@
<supersededby/>
<shortname>mep</shortname>
&stpeter;
<revision>
<version>0.1</version>
<date>2013-01-03</date>
<initials>psa</initials>
<remark><p>Initial published version approved for publication by the XMPP Council.</p></remark>
</revision>
<revision>
<version>0.0.2</version>
<date>2012-12-09</date>
@ -124,6 +130,7 @@
</pubsub>
</iq>
]]></example>
<p class='box'>Note: Publishing to an occupant's MEP node happens by sending an explicit publish request to the Occupant JID. Publishing to a user's PEP node MUST NOT trigger a MEP publish request, because PEP and MEP are separate pubsub contexts.</p>
<p>As a result, everyone in the room who is interested in that kind of data will receive a notification about the event (note that even the publisher receives the event, if they have advertised interest in the payload type):</p>
<example caption='Interested occupants receive event notification'><![CDATA[
<message from='coven@chat.shakespeare.lit/secondwitch'
@ -268,7 +275,7 @@
A MUC eventing service that supports the
publish-subscribe subset defined herein.
</desc>
<doc>XEP-xxxx</doc>
<doc>XEP-0316</doc>
</type>
</category>
]]></code>
@ -280,7 +287,7 @@
</section1>
<section1 topic='Acknowledgements' anchor='ack'>
<p>Thanks to Joe Hildebrand and Matthew Wild for their input.</p>
<p>Thanks to Joe Hildebrand, Matt Miller, and Matthew Wild for their input.</p>
</section1>
</xep>