Looks good - worth making the point about the transience of a label catalog. Slight grammar error though: "Two identical catalog requests may returned different results".
Another thought - if there is a chance that the catalog may change between the client requesting it and then sending a message with a label from the catalog, it may be worth including some guidance for when a message is sent with a label which is no longer acceptable (I.e. Is there a specific error that the server should return?). Also, I wonder if, as a future update, some kind of hint from the server about catalog lifetime would be useful. Or this may just be a solution in search of a problem! Cheers, Ash On 05/01/2013 03:32, "Peter Saint-Andre" <[email protected]> wrote: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >Kurt Zeilenga has submitted version 1.1 of XEP-0258. This requires >Council approval. The diff and rendered file are here: > >http://xmpp.org/extensions/diff/api/xep/0258/diff/1.0/vs/1.1rc1 > >http://xmpp.org/extensions/tmp/xep-0258-1.1.html > >Kurt told me he can attend the Council meeting in which this is >discussed, if desired. > >Peter > >- -- >Peter Saint-Andre >https://stpeter.im/ > > >-----BEGIN PGP SIGNATURE----- >Version: GnuPG/MacGPG2 v2.0.18 (Darwin) >Comment: Using GnuPG with undefined - http://www.enigmail.net/ > >iEYEARECAAYFAlDnnsAACgkQNL8k5A2w/vygsQCfc6lCOcG9MpZTjWACa9Ecge3q >cOsAoKDp/L5XYaX7h0wv6uUqrtMdtlp4 >=ikhw >-----END PGP SIGNATURE-----
