XEP-0411: Fix (typo) XEP numbers

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
This commit is contained in:
Maxime “pep” Buquet 2020-05-25 01:42:36 +02:00
parent eb3ccc48f0
commit fd9f489c07
No known key found for this signature in database
GPG Key ID: DEDA74AEECA9D0F2
1 changed files with 8 additions and 2 deletions

View File

@ -16,7 +16,7 @@
<approver>Council</approver>
<dependencies>
<spec>XMPP Core</spec>
<spec>XEP-0084</spec>
<spec>XEP-0049</spec>
<spec>XEP-0153</spec>
</dependencies>
<supersedes/>
@ -28,6 +28,12 @@
<email>daniel@gultsch.de</email>
<jid>daniel@gultsch.de</jid>
</author>
<revision>
<version>0.2.1</version>
<date>2020-05-25</date>
<initials>mb</initials>
<remark>Fix XEP numbers</remark>
</revision>
<revision>
<version>0.2.0</version>
<date>2018-11-08</date>
@ -66,7 +72,7 @@
</iq>]]></example>
</section1>
<section1 topic='Conversion' anchor='conversion'>
<p>Modern clients are expected to use PEP (<strong>XEP-0084</strong>) 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.</p>
<p>Modern clients are expected to use PEP (<strong>XEP-0163</strong>) 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.</p>
<p>When a legacy client modifies bookmarks over Private XML the service MUST send out notification messages to all subscribers of the 'storage:bookmarks' node.</p>
</section1>
<section1 topic='Implementation Notes' anchor='impl'>