%ents; ]>
Pubsub Message Archive Management This document defines a protocol to query and control a pubsub node's message archive. &LEGALNOTICE; 0442 Experimental Standards Track Standards XMPP Core XEP-0030 XEP-0059 XEP-0060 XEP-0297 XEP-0313 pubsub-mam &mwild; &ksmith; 0.2.0 2020-08-25 XEP Editor (jsc) Accepted by vote of Council on 2020-08-19. 0.1.0 2020-03-30 mw

Split off from XEP-0313 v0.6.3 to ease advancement of that XEP and allow further clarification and expansion of pubsub use cases.

This document specifies how to use &xep0313; in combination with &xep0060; to host and query archives on pubsub nodes.

When querying a pubsub node's archive, the 'node' attribute is added to the <query> element.

]]> Soliloquy To be, or not to be: that is the question: Whether 'tis nobler in the mind to suffer The slings and arrows of outrageous fortune, Or to take arms against a sea of troubles, And by opposing end them? tag:denmark.lit,2003:entry-32397 2003-12-13T18:30:02Z 2003-12-13T18:30:02Z ]]>

A PubSub service offering MAM SHOULD store each of the items published to each node. When responding to MAM requests it MUST construct the message stanza within the <forwarded> element in the same manner as the notifications sent to subscribers for the item, except that specifying the 'from' 'to' and 'id' attributes are OPTIONAL. Pubsub items must be returned one per message stanza (i.e. there MUST NOT be multiple <item> elements within the <items> element).