Developers have been poking me about roster versioning: http://xmpp.org/extensions/xep-0237.html
In fact developers are already implementing it. :)
So we need to make a final decision:
1. Do we limit this to rosters?
<iq type='get'>
<query xmlns='jabber:iq:roster' ver='foo'/>
</iq>
Implications: (a) it is included in rfc3921bis (b) it can't be used for
anything else (e.g. disco) and we'd need to define similar methods for
those protocols.
OR
2. Do we make it more general?
<iq type='get'>
<query xmlns='jabber:iq:roster'>
<ver xmlns='urn:xmpp:dataver'>foo</ver>
</query>
</iq>
Implications: (a) it is defined in a standalone XEP (b) it can be used
in any protocol that might return large data sets (rosters, disco, and
perhaps others).
I still lean to #1 but let's get consensus and finish this discussion so
that developers can do their coding. :)
Peter
--
Peter Saint-Andre
https://stpeter.im/
smime.p7s
Description: S/MIME Cryptographic Signature
