OK folks, it's time to push version 1.13 of XEP-0060 out the door. My
main question is: do we have consensus on the versioning stuff? If not
(and if we can't gain consensus soon), then I would vote to remove it so
that we can publish 1.13.

BTW the changelog is long so please take a few moments to review it:

    * Corrected a large number of reported errata.
    * Removed delete-any feature.
    * Added missing delete-items feature.
    * Removed replyto and replyroom config options.
    * Removed multiple node discovery since it depended on the
deprecated Service Discovery Publishing feature.
    * Defined "room" value for itemreply config option.
    * Added optional 'publisher' attribute to <item/> element.
    * Added optional <redirect/> child to <delete/> element.
    * Clarified meaning of filtered notifications (they are based on
NodeIDs, not payload namespaces).
    * Added pubsub-on-a-jid service discovery feature for explicit
discovery that an IM and presence account also functions as a virtual
pubsub service.
    * Added purge_offline node configuration option for purging the node
when the relevant publisher goes offline, for use in certain extended
presence applications.
    * Added item_expire node configuration option for automatically
removing items after a certain number of seconds.
    * Added notification_type node configuration option for defining
which value of the <message/> type attribute shall be used for
notifications.
    * Added retrieve-default-sub feature for retrieving default
subscription configuration from a node (as you can retrieve default node
configuration from the service).
    * Clarified suggested rules for payload definitions.
    * Mentioned that singleton pattern can be enforced by setting
max_items to 1.
    * Removed subids from subscription approval forms because
subscribers can have only one unapproved subscription request per node
at a given time.
    * Added optional support for delivery of notifications via XMPP IQ
stanzas.
    * Removed the notion of batch publishing because it makes
information coherence and atom handling excessively difficult.
    * Added error handling for too-many-subscriptions to help prevent a
certain denial of service attack.
    * Added process for retrieving default subscription configuration
options for leaf nodes, by omitting the 'node' attribute on the
<default/> element (also added the <default/> element to the schema for
the http://jabber.org/protocol/pubsub namespace, since it was missing).
    * Added optional data versioning via the 'ver' attribute on the
<item/> element (item-level versioning) and <items/> element (node-level
versioning), along with associated pubsub#versioning configuration field.

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to