diff --git a/xep-0060.xml b/xep-0060.xml index 60792181..e37477f8 100644 --- a/xep-0060.xml +++ b/xep-0060.xml @@ -5333,10 +5333,10 @@ And by opposing end them?

There are many possible triggers for sending a notification to an entity for the currently published item or the last published item, as summarized below:

    -
  1. The entity has explicitly requested one or more items from the node and is authorized to retrieve items.
    2. -
  2. The entity is an authorized subscriber to the node; The publisher sends a publish request, the service sends the currently published item to the entity.
    3. -
  3. The entity is not subscribed but is eligible to do so and has sent presence (potentially containing appropriate entity capabilities data) to a node that is presence-enabled; when the publisher sends a publish request, the service sends the currently published item to the entity.
    4. -
  4. The entity is not subscribed but is eligible to do so and sends presence (potentially containing appropriate entity capabilities data) to a node that is presence-enabled; as a result, the service sends the last published item to the entity.
    5. +
  5. The entity explicitly requests one or more items from the node and is authorized to retrieve items; when the service receives such a request, it sends the items to the entity.
    6. +
  6. The entity is an authorized subscriber to the node; when the publisher sends a publish request, the service sends the currently published item to the entity.
    7. +
  7. The entity is not subscribed but is eligible to do so and sends presence containing appropriate entity capabilities data to a service that supports filtered notifications (effectively establishing a "temporary subscription"); when the service receives such presence, it sends the last published item to the entity.
    8. +
  8. The entity is not subscribed but is eligible to do so and has sent presence containing appropriate entity capabilities data to a service that supports filtered notifications (effectively establishing a "temporary subscription"); when the publisher sends a publish request that matches the entity's expressed notification interests, the service sends the currently published item to the entity.
  9. The entity gains access to the node because of a change to the node access model; as a result, the service sends the last published item to the entity.
  10. The entity is added to the roster group associated with a node access model of "roster"; as a result, the service sends the last published item to the entity.