From 7b0926703928bd225c86945e7fb954d3222104c9 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Tue, 24 Jun 2008 21:57:49 +0000 Subject: [PATCH] added note about caps node git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@2010 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0115.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xep-0115.xml b/xep-0115.xml index 1d7be524..2a1bc50b 100644 --- a/xep-0115.xml +++ b/xep-0115.xml @@ -461,7 +461,7 @@ ]]>

The disco#info request is sent by the requesting entity to the generating entity. The value of the 'to' attribute MUST be the exact JID of the generating entity, which in the case of a client will be the full JID &LOCALFULL;.

- +

Note: The generating entity SHOULD NOT include the "caps node" in the list of entities it returns in its disco#items responses; i.e., the caps node is a kind of virtual or phantom node, not a true items node that is associated with the generating entity for service discovery purposes.

The disco 'node' attribute MUST be included for backwards-compatibility. The value of the 'node' attribute SHOULD be generated by concatenating the value of the caps 'node' attribute (e.g., "http://code.google.com/p/exodus") as provided by the generating entity, the "#" character, and the value of the caps 'ver' attribute (e.g., "QgayPKawpkPSDYmwT/WM94uAlu0=") as provided by the generating entity.

The generating entity then returns all of the capabilities it supports.