From 830ce660116d862a0a757c68806ef7c5b0ee1266 Mon Sep 17 00:00:00 2001 From: Daniel Gultsch Date: Tue, 12 Dec 2017 17:26:30 +0100 Subject: [PATCH] XEP-0060: Introduce 1:1 mapping between publish-options and node configuration --- xep-0060.xml | 50 ++++++++++++++++---------------------------------- 1 file changed, 16 insertions(+), 34 deletions(-) diff --git a/xep-0060.xml b/xep-0060.xml index f7f1cee4..82c52e28 100644 --- a/xep-0060.xml +++ b/xep-0060.xml @@ -50,12 +50,26 @@ &stpeter; &ralphm; + + 1.15.0 + 2017-12-12 + dg + +
    +
  • Specify that unregistered publish-options are mapped 1:1 to node configurations
    • +
  • Get rid of per-item OVERRIDE
    • +
  • Get rid of METADATA publish-options
    • +
  • Remove registration for the obsolete pubsub#access_model publish-options
    • +
+ + 1.14 2017-11-29 jt

Add pubsub#multi-items to features.

 + 1.13.8 2017-10-10 @@ -2969,8 +2983,8 @@ And by opposing end them? ]]>

The <publish-options/> element MUST contain a data form (see XEP-0004), whose FORM_TYPE MUST be "http://jabber.org/protocol/pubsub#publish-options" (see XEP-0068).

-

Fields and their behaviour MUST be registered with the XMPP Registrar. Each field MUST specify whether it defines METADATA to be attached to the item, a per-item OVERRIDE of the node configuration, or a PRECONDITION to be checked against the node configuration. A pubsub service advertising support for publishing options MUST reject publications with unknown fields.

-

A field defined as a precondition MUST be processed as follows:

+

Each form field denotes a precondition to publishing the request. A pub-sub service advertising support for publishing options MUST check each precondition field against the node configuration of the same name, and it MUST reject the publication upon encountering unknown fields.

+

Preconditions MUST be processed as follows:

  1. If the node exists and the precondition is not met, then the publish MUST fail with a &conflict; error condition and a pubsub-specific condition of <precondition-not-met/>.
  2. If the node exists and the precondition is met, then the publish succeeds.
    3. @@ -6423,38 +6437,6 @@ xmpp:pubsub.shakespeare.lit?pubsub;action=retrieve;node=princely_musings;item=ae label='The type of node data, usually specified by the namespace of the payload (if any)'/> -]]> - - - - http://jabber.org/protocol/pubsub#publish-options - XEP-0060 - - Forms enabling publication with options; each field must specify whether it - defines METADATA to be attached to the item, a per-item OVERRIDE of the node - configuration, or a PRECONDITION to be checked against the node configuration. - - - - - - - - - ]]>