From fd9f489c073ccd3e56d11edfc0f601122a5a6baf Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Maxime=20=E2=80=9Cpep=E2=80=9D=20Buquet?= Date: Mon, 25 May 2020 01:42:36 +0200 Subject: [PATCH] XEP-0411: Fix (typo) XEP numbers MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Maxime “pep” Buquet --- xep-0411.xml | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/xep-0411.xml b/xep-0411.xml index cef4d650..01d9a105 100644 --- a/xep-0411.xml +++ b/xep-0411.xml @@ -16,7 +16,7 @@ Council XMPP Core - XEP-0084 + XEP-0049 XEP-0153 @@ -28,6 +28,12 @@ daniel@gultsch.de daniel@gultsch.de + + 0.2.1 + 2020-05-25 + mb + Fix XEP numbers + 0.2.0 2018-11-08 @@ -66,7 +72,7 @@ ]]> -

Modern clients are expected to use PEP (XEP-0084) as interface to upload and retrieve their bookmarks and not explicitly request bookmarks from private XML anymore. Thus a service MUST support conversion from PEP to Private XML and vice versa. Whether PEP and Private XML are fed from the same data source or if they get copied over when ever one of them gets written is out of scope of this document.

+

Modern clients are expected to use PEP (XEP-0163) as interface to upload and retrieve their bookmarks and not explicitly request bookmarks from private XML anymore. Thus a service MUST support conversion from PEP to Private XML and vice versa. Whether PEP and Private XML are fed from the same data source or if they get copied over when ever one of them gets written is out of scope of this document.

When a legacy client modifies bookmarks over Private XML the service MUST send out notification messages to all subscribers of the 'storage:bookmarks' node.