diff --git a/xep-0184.xml b/xep-0184.xml index 4deeb758..3772f911 100644 --- a/xep-0184.xml +++ b/xep-0184.xml @@ -177,7 +177,7 @@
  • <request/> -- included in a content message by a sending entity that wishes to know if the content message has been received, i.e., delivered to a client controlled by the intended recipient.
  • <received/> -- included in an ack message by a receiving entity that wishes to inform the sending entity that the content message has been received, i.e., delivered to a client controlled by the intended recipient.
    • -

    Specifically, the receiving entity shall return an ack message containing the <received/> extensino if the content message has been delivered to a client controlled by the intended recipient. In general, a client will return a receipt only if the client has processed the content message (e.g., if the client has presented the content message to a human user or has completed any automated processing of the content message, such as generation of an error response if the application determines that the content message cannot be handled). However, the Message Delivery Receipts protocol does not provide notification that a human user has read or understood the content message, that an automated system has completed processed or acted upon the message, etc.

    +

    Specifically, the receiving entity shall return an ack message containing the <received/> extension if the content message has been delivered to a client controlled by the intended recipient. In general, a client will return a receipt only if the client has processed the content message (e.g., if the client has presented the content message to a human user or has completed any automated processing of the content message, such as generation of an error response if the application determines that the content message cannot be handled). However, the Message Delivery Receipts protocol does not provide notification that a human user has read or understood the content message, that an automated system has completed processed or acted upon the message, etc.

    The following is an example of a content message that includes a request for return receipt.

    ]]>

    Note: A sender MUST include an 'id' attribute on every content message that requests a receipt, so that the sender can properly track ack messages.

    -

    The recipient shall generate an ack message if and only if (1) it supports the Message Delivery Receipts protocol and (2) it is configured to return receipts, either globally or for this recipient (otherwise it MUST NOT return a receipt and SHOULD NOT return an error).

    +

    The recipient shall generate an ack message if and only if:

    +
      +
    1. it supports the Message Delivery Receipts protocol; and
      2. +
    2. it is configured to return receipts, either globally or for this recipient.
      3. +
    +

    Otherwise it MUST NOT return a receipt and SHOULD NOT return an error.