From e67fdd3a391af34e8832b2b731fa98214b4f6e9a Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Thu, 3 Jan 2013 11:25:52 -0700 Subject: [PATCH] 0.1 --- xep-0316.xml | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/xep-0316.xml b/xep-0316.xml index 41d83b23..e0908a75 100644 --- a/xep-0316.xml +++ b/xep-0316.xml @@ -9,8 +9,8 @@ MUC Eventing Protocol 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. &LEGALNOTICE; - XXXX - ProtoXEP + 0316 + Experimental Standards Track Standards JIG Council @@ -26,6 +26,12 @@ mep &stpeter; + + 0.1 + 2013-01-03 + psa +

Initial published version approved for publication by the XMPP Council.

+
0.0.2 2012-12-09 @@ -124,6 +130,7 @@ ]]> +

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.

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):

- XEP-xxxx + XEP-0316 ]]> @@ -280,7 +287,7 @@ -

Thanks to Joe Hildebrand and Matthew Wild for their input.

+

Thanks to Joe Hildebrand, Matt Miller, and Matthew Wild for their input.