From a037ddd440241ea71e67a61c32877622c77fc10b Mon Sep 17 00:00:00 2001
From: Peter Saint-Andre <stpeter@jabber.org>
Date: Fri, 16 Feb 2007 06:06:59 +0000
Subject: [PATCH] 1.1 published

git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@598 4b5297f7-1745-476d-ba37-a9c6900126ab
---
 xep-0092.xml | 31 ++++++++++++++++++++++++++-----
 1 file changed, 26 insertions(+), 5 deletions(-)

diff --git a/xep-0092.xml b/xep-0092.xml
index 14adfd00..0a2e8fe5 100644
--- a/xep-0092.xml
+++ b/xep-0092.xml
@@ -23,22 +23,22 @@
   </schemaloc>
   &stpeter;
   <revision>
-    <version>1.1pre1</version>
-    <date>in progress, last updated 2007-02-08</date>
+    <version>1.1</version>
+    <date>2007-02-15</date>
     <initials>psa</initials>
-    <remark>Per a vote of the XMPP Council, changed from Historical and Active to Standards Track and Draft; recommended use of Entity Capabilities instead of Software Version when presence information is available; added proviso to security considerations regarding disclosure of operating system information.</remark>
+    <remark><p>Per a vote of the XMPP Council, changed from Historical and Active to Standards Track and Draft; recommended use of Entity Capabilities instead of Software Version when presence information is available; added proviso to security considerations regarding disclosure of operating system information; added section on Service Discovery.</p></remark>
   </revision>
   <revision>
     <version>1.0</version>
     <date>2003-10-08</date>
     <initials>psa</initials>
-    <remark>Per a vote of the Jabber Council, changed status to Active.</remark>
+    <remark><p>Per a vote of the Jabber Council, changed status to Active.</p></remark>
   </revision>
   <revision>
     <version>0.1</version>
     <date>2003-05-22</date>
     <initials>psa</initials>
-    <remark>Initial version.</remark>
+    <remark><p>Initial version.</p></remark>
   </revision>
 </header>
 <section1 topic='Introduction' anchor='intro'>
@@ -78,6 +78,27 @@
   ]]></example>
   <p>The standard error conditions described in &xep0086; apply (e.g., service unavailable if the entity does not support the namespace).</p>
 </section1>
+<section1 topic='Determining Support' anchor='disco'>
+  <p>In order for a requesting entity to determine if a responding entity supports result set management, it SHOULD send a &xep0030; information request to the responding entity:</p>
+  <example caption='Requesting entity queries responding entity regarding protocol support'><![CDATA[
+<iq from='stpeter@jabber.org/roundabout'
+    to='conference.jabber.org'
+    id='disco1'>
+  <query xmlns='http://jabber.org/protocol/disco#info'/>
+</iq>
+  ]]></example>
+  <example caption='Responding entity communicates protocol support'><![CDATA[
+<iq from='conference.jabber.org'
+    to='stpeter@jabber.org/roundabout'
+    id='disco1'>
+  <query xmlns='http://jabber.org/protocol/disco#info'>
+    ...
+    <feature var='jabber:iq:version'/>
+    ...
+  </query>
+</iq>
+  ]]></example>
+</section1>
 <section1 topic='Security Considerations' anchor='security'>
   <p>Revealing the application's underlying operating system may open the user or system to attacks directed against that operating system; therefore, an application MUST provide a way for a human user or administrator to disable sharing of information about the operating system.</p>
 </section1>