22
edits
(3 intermediate revisions by one other user not shown) | |||
Line 40: | Line 40: | ||
* Add feature delete-nodes-redirect (OPTIONAL) | * Add feature delete-nodes-redirect (OPTIONAL) | ||
* Modify language to state there can be only one redirect element. | * Modify language to state there can be only one redirect element. | ||
=== Redundant features for Item Retraction === | |||
The latest revision introduced a feature 'delete-items', while 'retract-items' was already there. Ralphm proposed to the list: | |||
<blockquote> | |||
[...] Reading the text around it, I feel it is | |||
confusing, too. I'd rather go with talking about 'retracting items' and | |||
'deleting nodes' thoughout, and not talk about 'deleting items'. | |||
</blockquote> | |||
<blockquote> | |||
I think that many (all?) clients ignore this feature for discovery | |||
altogether, so what about making 'delete-items' a thing that servers | |||
SHOULD also advertise along with 'retract-items', but have clients | |||
depend on 'retract-items' exclusively? | |||
</blockquote> | |||
=== No text on #publish_model === | |||
A few examples mention an option #publish_model, which seems useful, but there's no actual text describing behaviour of said option. | |||
=== Entity node creation authorization request (Section 8.1) === | |||
There's no way to know if an entity can create (or not) a node before actually create it. | |||
This issue bring a bad UI experience on some Pubsub clients (we display an error after the form creation submission). | |||
== XEP-0163: PEP == | == XEP-0163: PEP == |
edits