On 4/6/09 12:28 AM, Alexander Tsvyashchenko wrote: > Hello Peter, > > On Sun, 05 Apr 2009 16:24:33 -0600, Peter Saint-Andre <[email protected]> > wrote: > >> You are right -- the words "participating full JID" in the first >> paragraph of Section 7.2 unnecessarily and incorrectly limit the >> matching for collection retrieval. I've fixed that: >> >> > http://svn.xmpp.org:18080/browse/XMPP/trunk/extensions/xep-0136.xml?%40diffMode=u&%40diffWrap=s&r1=2415&r2=2993&u=3&ignore=&k= > > ... in fact it seems I've managed to convince several people in the > opposite already (including topic-starter) based on current XEP-136 wording > ;-) See discussion starting from this comment: > https://www.ndl.kiev.ua/content/modarchiveodbc-release#comment-117
Oops. The original poster was right that the following text is confusing: *** To request a page of messages from a collection the client sends a <retrieve/> element. The 'with' and 'start' attributes specify the participating full JID and the start time (see XEP-0082). Both attributes MUST be included to uniquely identify a collection. In addition, the client MAY match an exact bare JID (<[email protected]> or <domain.tld>) by setting the boolean 'exactmatch' attribute to a value of "true" or "1" [14] -- for details, refer to the Exact JID Matching section of this document. *** There is no need for 'exactmatch' if you can specify only a full JID. I'll look at this more tomorrow... Peter -- Peter Saint-Andre https://stpeter.im/
smime.p7s
Description: S/MIME Cryptographic Signature
