moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2025-02-07 10:50:21 -05:00
Code Issues Releases Wiki Activity

Merge branch 'xep-0313' into premerge

Browse Source
This commit is contained in:
Jonas Schäfer 2022-02-22 18:43:48 +01:00
commit bbd3257491
1 changed files with 117 additions and 104 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
xep-0313.xml
View File

@ -29,6 +29,17 @@
</schemaloc>
&mwild;
&ksmith;
<revision>
<version>1.0.1</version>
<date>2022-02-16</date>
<initials>egp</initials>
<remark>
<ul>
<li>Fix inconsistency in example namespaces.</li>
<li>Fix indentation, especially in examples.</li>
</ul>
</remark>
</revision>
<revision>
<version>1.0.0</version>
<date>2021-11-02</date>
@ -230,8 +241,10 @@
</section1>
<section1 topic='Message archives' anchor='archives'>
<p>An archive contains a collection of messages relevant to a particular XMPP address, e.g. a user, MUC, pubsub node, server. Note: while a service might have many "archives" as defined here (one per JID capable of being queried) this is a conceptual distinction,
and a server is not bound to any particular implementation or arrangement of data stores.</p>
<p>An archive contains a collection of messages relevant to a particular XMPP address, e.g. a user, MUC,
pubsub node, server. Note: while a service might have many "archives" as defined here (one per JID
capable of being queried) this is a conceptual distinction, and a server is not bound to any particular
implementation or arrangement of data stores.</p>
<p>Exactly which messages a server archives is up to implementation and deployment policy,
but it is expected that all messages that hold meaningful content, rather than state changes such as Chat State Notifications, would be archived. Rules are specified later in this document.</p>
<p>A stored message consists of at least the following pieces of information:</p>
@ -570,10 +583,10 @@
<field type='hidden' var='FORM_TYPE'>
<value>urn:xmpp:mam:2</value>
</field>
<field type='text-single' var='urn:example:xmpp:free-text-search'>
<field type='text-single' var='{http://example.com/}free-text-search'>
<value>Where arth thou, my Juliet?</value>
</field>
<field type='text-single' var='urn:example:xmpp:stanza-content'>
<field type='text-single' var='{http://example.com/}stanza-content'>
<value>{http://jabber.org/protocol/mood}mood/lonely</value>
</field>
</x>
@ -942,9 +955,9 @@
access. For example authorized parties for a user's archive would likely include
just the user, and a MUC archive for a private room might be restricted
to room members. An implementation MAY choose to allow access to any archive
by server administrators. If a client
requests access to an archive it does not have permissions for the server MUST
return an iq with type error, and the error condition SHOULD be 'forbidden'.</p>
by server administrators. If a client requests access to an archive it does not
have permissions for the server MUST return an iq with type error, and the error
condition SHOULD be 'forbidden'.</p>
<p>A server SHOULD provide a mechanism for a user to disable archiving of
messages with all or specific contacts, such as via the configuration
protocol described in &xep0441;. This allows the user to prevent the