mirror of
https://github.com/moparisthebest/xeps
synced 2025-02-17 15:40:30 -05:00
XEP-0313: Fix indentation to be somewhat consistent
Also removes trailing whitespace in examples.
This commit is contained in:
parent
21a4b3537b
commit
1a9f110832
12
xep-0313.xml
12
xep-0313.xml
@ -230,8 +230,10 @@
|
|||||||
</section1>
|
</section1>
|
||||||
|
|
||||||
<section1 topic='Message archives' anchor='archives'>
|
<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,
|
<p>An archive contains a collection of messages relevant to a particular XMPP address, e.g. a user, MUC,
|
||||||
and a server is not bound to any particular implementation or arrangement of data stores.</p>
|
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,
|
<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>
|
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>
|
<p>A stored message consists of at least the following pieces of information:</p>
|
||||||
@ -942,9 +944,9 @@
|
|||||||
access. For example authorized parties for a user's archive would likely include
|
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
|
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
|
to room members. An implementation MAY choose to allow access to any archive
|
||||||
by server administrators. If a client
|
by server administrators. If a client requests access to an archive it does not
|
||||||
requests access to an archive it does not have permissions for the server MUST
|
have permissions for the server MUST return an iq with type error, and the error
|
||||||
return an iq with type error, and the error condition SHOULD be 'forbidden'.</p>
|
condition SHOULD be 'forbidden'.</p>
|
||||||
<p>A server SHOULD provide a mechanism for a user to disable archiving of
|
<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
|
messages with all or specific contacts, such as via the configuration
|
||||||
protocol described in &xep0441;. This allows the user to prevent the
|
protocol described in &xep0441;. This allows the user to prevent the
|
||||||
|
Loading…
Reference in New Issue
Block a user