Hi, Looking at XEP-0313: Message Archive Management and XEP-0163: Personal Eventing Protocol I think that there may be an interoperability issue between those XEPs.
XEP-0163 states that Jabber/XMPP server that supports PEP associates a virtual PubSub service with the account. In fact, this makes PubSub service available under user account bare JID. In XEP-0313 in section 7. Determining support we have the following statement: "If a server or other entity hosts archives and supports MAM queries, it MUST advertise the 'urn:xmpp:mam:2' feature in response to Service Discovery (XEP-0030) [15] requests made to archiving JIDs (i.e. JIDs hosting an archive, such as users' bare JIDs)" and XEP-0313 also suggests the possibility to use MAM to query PubSub items. Now if we consider that XEP-0163 uses bare JID as a PubSub service JID and XEP-0313 MAM uses the same bare JID address to host an archive of user messages then it is not possible to advertise and use MAM support for PEP (PubSub) nodes hosted under the same address. In this case MAM will advertise feature "urn:xmpp:mam:2" for jid [email protected] and the same feature should be returned for PEP if it supports MAM. There is no way to distinguish which one is supported. The same issue is with querying archives. No way to tell if we should query PEP archive or user messages archive as both are under the same bare JID! Even if we would consider that user message archive should be queried with an <iq/> without 'to' attribute set and we would query PEP nodes with 'to' attribute set, then there is still no possibility to determine if MAM is supported for PEP or for user archive only are to determine support we are sending disco#info query always to the same bare JID. Am I correct? or maybe I'm missing something? Thanks, Andrzej _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
