-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 7/14/09 1:15 PM, Curtis King wrote: > > On 14-Jul-09, at 8:13 AM, Peter Saint-Andre wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On 7/14/09 12:11 AM, Tomasz Sterna wrote: >>> On wto, 2009-07-14 at 04:40 +0200, Jiří Zárevúcky wrote: >>>> I agree specs should be strict, but someone not capable of deducing >>>> this actually implementing the spec? That is a ridiculous idea >>>> (considering all the examples). >>> >>> I've seen XMPP implemented by "XML console deduction", so I am expecting >>> the worse. >> >> True. :) >> >> I shall add an example about this when I copy over the roster versioning >> stuff to 3921bis. > > Can a server always include ver attribute in all roster pushes, even > when it hasn't been enabled by a client? The XEP only states, "When > roster versioning is enabled, the server MUST include the updated roster > version with each roster push. Roster pushes MUST occur in order of > modification and the version contained in a roster push MUST be unique." > It should be clear in the draft.
Agreed -- there is no harm if the server always includes 'ver'. I'll update the spec to say that. Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpc2sgACgkQNL8k5A2w/vxWPACePB7KXKtOmJqMbBi0JFlLzExg RPYAnjB0uHfNtLavWbDvslrg4R29/eO9 =b8oT -----END PGP SIGNATURE-----
