On 25.03.19 22:07, Dave Cridland wrote: > On Mon, 25 Mar 2019 at 14:03, Florian Schmaus <f...@geekplace.eu > <mailto:f...@geekplace.eu>> wrote: > On 25.03.19 13:52, Dave Cridland wrote: > > On Mon, 25 Mar 2019 at 12:26, Florian Schmaus <f...@geekplace.eu > <mailto:f...@geekplace.eu> > > <mailto:f...@geekplace.eu <mailto:f...@geekplace.eu>>> wrote: > > I lean towards 2. Which could mean that > > > > <message from='f...@bar.com <mailto:f...@bar.com> > <mailto:f...@bar.com <mailto:f...@bar.com>>' > > to='u...@example.com <mailto:u...@example.com> > <mailto:u...@example.com <mailto:u...@example.com>>'> > > <stanza-id by='example.com <http://example.com> > <http://example.com>' …/> > > </message> > > > > does not indicate archival of the message into > u...@example.com <mailto:u...@example.com> > > <mailto:u...@example.com <mailto:u...@example.com>>'s MAM > > archive, while > > > > <message from='f...@bar.com <mailto:f...@bar.com> > <mailto:f...@bar.com <mailto:f...@bar.com>>' > > to='u...@example.com <mailto:u...@example.com> > <mailto:u...@example.com <mailto:u...@example.com>>'> > > <stanza-id by='u...@example.com <mailto:u...@example.com> > <mailto:u...@example.com <mailto:u...@example.com>>' …/> > > </message> > > > > does. > > > > > > Ah, so the first suggests the message is archived by the server-level > > archive? > > I'd say it depends whether "example.com <http://example.com>" > announces the MAM disco#info > feature. And I also believe that this does not automatically imply for > the receiving entity that it has access to that message in the archive > (if there is one). > > > Ah, so the semantics of XEP-0359 vary depending on an unrelated > specification not referenced by the document in ways that are not > specified in either document?
I wouldn't say that the semantics of XEP-0359 vary. The <stanza-id/> element tells you that an entity, identified by the JID in the 'by' value, assigned a particular ID to this stanza. If and how you could potentially lookup the stanza depends on various factors, including that you and the entity need to speak a common protocol. As you possibly know we usually use disco#info to determine the available features and supported protocols of an entity, hence a lookup only appears obvious to me. I am happy to clarify that in case the idea isn't as obvious as I thought it to be. - Florian
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________
