I've been working to update XEP-0060 (Publish-Subscribe) with a few more fixes based on implementation and deployment experience. In particular:
1. A few weeks ago, we discussed on this list some slight modifications to XEP-0060 so that a service will return the ItemID on publish if the publisher did not include an ItemID in its publish request. I have updated the spec according to that consensus, as described here: http://mail.jabber.org/pipermail/standards/2008-May/018811.html 2. Mickael Remond pinged me off-list about adding an example showing the use of Result Set Management (XEP-0059) to handle large sets of published items (as we've done in XEP-0045), so I added that. 3. Ralph Meijer and I chatted recently about some oddities related to node association and disassociation with respect to the root collection node, which should be clarified now. 4. Someone who shall remain nameless pinged me off-list about the handling of node deletion, noting that this was not well specified in the case of collection nodes. I agreed. However, clearing that up has led me to write a new section (9.1) that defines a variety of different deployment scenarios (graph theory!), and then to write another new section (9.6) that uses those definitions in specifying how deletion of a collection node should be handled. The rendered text for version 1.12pre1 is here: http://www.xmpp.org/extensions/tmp/xep-0060-1.12.html The SVN diff is here: http://is.gd/w1g Enjoy! Peter -- Peter Saint-Andre https://stpeter.im/
smime.p7s
Description: S/MIME Cryptographic Signature
