mirror of
https://github.com/moparisthebest/xeps
synced 2024-11-24 10:12:19 -05:00
XEP-0411: Fix (typo) XEP numbers
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
This commit is contained in:
parent
eb3ccc48f0
commit
fd9f489c07
10
xep-0411.xml
10
xep-0411.xml
@ -16,7 +16,7 @@
|
|||||||
<approver>Council</approver>
|
<approver>Council</approver>
|
||||||
<dependencies>
|
<dependencies>
|
||||||
<spec>XMPP Core</spec>
|
<spec>XMPP Core</spec>
|
||||||
<spec>XEP-0084</spec>
|
<spec>XEP-0049</spec>
|
||||||
<spec>XEP-0153</spec>
|
<spec>XEP-0153</spec>
|
||||||
</dependencies>
|
</dependencies>
|
||||||
<supersedes/>
|
<supersedes/>
|
||||||
@ -28,6 +28,12 @@
|
|||||||
<email>daniel@gultsch.de</email>
|
<email>daniel@gultsch.de</email>
|
||||||
<jid>daniel@gultsch.de</jid>
|
<jid>daniel@gultsch.de</jid>
|
||||||
</author>
|
</author>
|
||||||
|
<revision>
|
||||||
|
<version>0.2.1</version>
|
||||||
|
<date>2020-05-25</date>
|
||||||
|
<initials>mb</initials>
|
||||||
|
<remark>Fix XEP numbers</remark>
|
||||||
|
</revision>
|
||||||
<revision>
|
<revision>
|
||||||
<version>0.2.0</version>
|
<version>0.2.0</version>
|
||||||
<date>2018-11-08</date>
|
<date>2018-11-08</date>
|
||||||
@ -66,7 +72,7 @@
|
|||||||
</iq>]]></example>
|
</iq>]]></example>
|
||||||
</section1>
|
</section1>
|
||||||
<section1 topic='Conversion' anchor='conversion'>
|
<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>
|
<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>
|
||||||
<section1 topic='Implementation Notes' anchor='impl'>
|
<section1 topic='Implementation Notes' anchor='impl'>
|
||||||
|
Loading…
Reference in New Issue
Block a user