diff --git a/xep-0313.xml b/xep-0313.xml index 1b9259d5..174eb58e 100644 --- a/xep-0313.xml +++ b/xep-0313.xml @@ -29,10 +29,12 @@ &ksmith; 0.4 - 2015-01-23 + 2015-09-21 ks/mw -

Switch the sentinel message back to the iq result. - Various small fixes to the document.

+ +

Switch the sentinel message back to the iq result.

+

Various small fixes to the document.

+
0.3 @@ -157,12 +159,12 @@ allows clients to accurately page through messages.

- + ]]> - + @@ -178,13 +180,13 @@

When querying a pubsub node's archive, the 'node' attribute is added to the <query> element.

- + ]]>

By default all messages match a query, and filters are used to request a subset of the archived messages. Filters are specified in a &xep0004; data form included with the query. The hidden FORM_TYPE field - MUST be set to this protocol's namespace, 'urn:xmpp:mam:0'. Three further fields are defined by this + MUST be set to this protocol's namespace, 'urn:xmpp:mam:1'. Three further fields are defined by this XEP and MUST be supported by servers, though all of them are optional for the client. These fields are:

  • start
  • @@ -203,10 +205,10 @@ regardless of the to/from addresses on each message.

    - + - urn:xmpp:mam:0 + urn:xmpp:mam:1 juliet@capulet.lit @@ -235,10 +237,10 @@ date/time of the most recent message stored in the archive.

    - + - urn:xmpp:mam:0 + urn:xmpp:mam:1 2010-06-07T00:00:00Z @@ -252,10 +254,10 @@ ]]> - + - urn:xmpp:mam:0 + urn:xmpp:mam:1 2010-08-07T00:00:00Z @@ -273,10 +275,10 @@ stanzas stored in the archive.

    - + - urn:xmpp:mam:0 + urn:xmpp:mam:1 2010-08-07T00:00:00Z @@ -294,7 +296,7 @@ - + 28482-98726-73623 09af3-cc343-b409f @@ -317,9 +319,9 @@ from the previous query.

    - + - urn:xmpp:mam:0> + urn:xmpp:mam:1> 2010-08-07T00:00:00Z @@ -334,7 +336,7 @@ - + 23452-4534-1 390-2342-22 @@ -349,14 +351,14 @@

    In order for the client find out about additional fields the server might support, it can send an iq stanza of type='get' addressed to the archive like this:

    - +
    - + - urn:xmpp:mam:0 + urn:xmpp:mam:1 @@ -370,10 +372,10 @@

    If it understands any of the additional fields, it can use them in subsequent queries.

    - + - urn:xmpp:mam:0 + urn:xmpp:mam:1 Where arth thou, my Juliet? @@ -406,7 +408,7 @@

    - + - + A MUC archive MUST NOT include 'private message' results (those sent directly between occupants, not shared in the room) in the results

    -

    A PubSub service offering MAM SHOULD store each of the items published to each node. When responding to MAM requests it MUST construct the message stanza within the <forwarded> element in the same manner as the notifications sent to subscribers for the item, except that specifying the 'from' 'to' and 'id' attributes are OPTIONAL. Pubsub items must be returned one per message stanza (i.e. there MUST NOT be multiple <item> elemetns within the <items> element).

    +

    A PubSub service offering MAM SHOULD store each of the items published to each node. When responding to MAM requests it MUST construct the message stanza within the <forwarded> element in the same manner as the notifications sent to subscribers for the item, except that specifying the 'from' 'to' and 'id' attributes are OPTIONAL. Pubsub items must be returned one per message stanza (i.e. there MUST NOT be multiple <item> elements within the <items> element).

    - + @@ -507,7 +509,7 @@
- + ]]> @@ -517,7 +519,7 @@ - + @@ -539,7 +541,7 @@ - + romeo@montague.lit @@ -553,7 +555,7 @@ MAY be different to the preferences sent by the client):

- + romeo@montague.lit @@ -645,7 +647,7 @@

If a server or other entity hosts archives and supports MAM queries, it MUST advertise - the 'urn:xmpp:mam:0' feature in response to &xep0030; requests made to archiving JIDs + the 'urn:xmpp:mam:1' feature in response to &xep0030; requests made to archiving JIDs (i.e. JIDs hosting an archive, such as users' bare JIDs):

... - + ...