From 52c2e60950d628690c31f00c1376a5991afbf48c Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Tue, 22 Sep 2009 20:56:03 +0000 Subject: [PATCH] minor clarification git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@3460 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0016.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xep-0016.xml b/xep-0016.xml index 4ade7b32..a5de7176 100644 --- a/xep-0016.xml +++ b/xep-0016.xml @@ -138,7 +138,7 @@
  • <domain> (the domain itself matches, as does any user@domain or domain/resource)
  • If the type is "group", then the 'value' attribute SHOULD contain the name of a group in the user's roster. (If a client attempts to update, create, or delete a list item with a group that is not in the user's roster, the server SHOULD return to the client an <item-not-found/> stanza error.)

    -

    If the type is "subscription", then the 'value' attribute MUST be one of "both", "to", "from", or "none" as defined RFC 3921, where "none" includes entities that are totally unknown to the user and therefore not in the user's roster at all.

    +

    If the type is "subscription", then the 'value' attribute MUST be one of "both", "to", "from", or "none" as defined RFC 3921, where "none" includes entities that are totally unknown to the user and therefore not in the user's roster at all. These values are exact matches, so that "both" means a bidirectional subscription (not "from" or "to" only).

    If no 'type' attribute is included, the rule provides the "fall-through" case.

    The 'action' attribute MUST be included and its value MUST be either "allow" or "deny". An implementation MUST NOT block communications from one of a user's resources to another, even if the user happens to define a rule that would otherwise result in that behavior.

    The 'order' attribute MUST be included and its value MUST be a non-negative integer that is unique among all items in the list. (If a client attempts to create or update a list with non-unique order values, the server MUST return to the client a <bad-request/> stanza error.)