Hi, I feel it'll create inconsistency due to changes in section "7.1 and 7.2" . As per section sec 4.5 the with attribute can be JID (not only full jid). so due to this change, it'll not be possible retrieve the collections having with attribute as bare JID.
One solution I think of is to keep sec "7.1 Retrieving a List of Collections" as it is and for sec. "7.2 Retrieving a Collection", remove the 'exactmatch' attribute and the value of with attribute should always be exactly matched by default. Regards, Sachin Khandelwal Sr. Software Engineer | Mundu Sever Geodesic Limited | www.geodesic.com Tel: +91 22 4031 5815 On Wednesday 08 April 2009 03:25:24 Peter Saint-Andre wrote: > On 4/7/09 3:44 PM, Peter Saint-Andre wrote: > > On 4/7/09 3:32 PM, Alexander Tsvyashchenko wrote: > >> Peter, > >> > >> On Tue, 07 Apr 2009 10:31:20 -0600, Peter Saint-Andre > >> <stpe...@stpeter.im> > >> > >> wrote: > >>> On 4/6/09 12:28 AM, Alexander Tsvyashchenko wrote: > >>>> I see two possible solutions: > >>>> > >>>> 1) Keep things like they were before, so that "retrieve" may return > >>>> messages from one collection only. Requires rollback of the last > >>>> change to > >>>> XEP and removing "exactmatch" support by "retrieve" from 10.1 and from > >>>> XML > >>>> Schema. > >>> > >>> I now think that is the right approach. > >>> > >>> Alexander, what do you think? > >> > >> I think that would be both the best and the easiest solution (the rare > >> case when these qualities do not interfere ;-) > > > > OK, good. I will update XEP-0136 accordingly > > Done: > > http://svn.xmpp.org:18080/browse/XMPP/trunk/extensions/xep-0136.xml?%40diff >Mode=u&%40diffWrap=s&r1=2993&r2=3008&u=3&ignore=&k= > > Peter
