perfsonar development work

Author: szymon
Date: 2007-10-11 03:36:20 -0400 (Thu, 11 Oct 2007)
New Revision: 289

Modified:
   trunk/nmwg/doc/dLS/dLS.xml
Log:
Some small figure corrections

Modified: trunk/nmwg/doc/dLS/dLS.xml
===================================================================
--- trunk/nmwg/doc/dLS/dLS.xml  2007-10-10 15:08:35 UTC (rev 288)
+++ trunk/nmwg/doc/dLS/dLS.xml  2007-10-11 07:36:20 UTC (rev 289)
@@ -466,7 +466,7 @@
    |                                                    |
  __V__                      _____                      _V___ 
 |     |                    |     | <_______(1)_______ |     |
-| LS3 | <----------------- | LS2 |                 | LS1 | 
+| LS3 | <----------------- | LS2 |                    | LS1 | 
 |_____|                    |_____| _______(3)_______> |_____|
    |                          ^ ^                       ^ ^
    |                          | |                       | |
@@ -478,10 +478,11 @@
              
              
              </artwork>
+             <postamble>LS2, LS3 and LS4 are in the ring. LS1 wants to join
+              the dLS cloud.</postamble>
            </figure>            
 
-           <t>Let's assume LS2, LS3 and LS4 are in the ring. LS1 wants to 
join
-              the dLS cloud.
+           <t>The algorithm for joining the ring works as follows: 
            </t>
            
             <list type="symbols">
@@ -632,29 +633,26 @@
              
              
              </artwork>
+             <postamble>LS1, LS2 and LS3 are in the ring.  LS1 receives a 
token.</postamble>
            </figure>            
-
-           <t>Let's assume LS1, LS2 and LS3 are in the ring.  LS1 receives a 
token.
-           </t>
            
-            <t>The algorithm for token passing works as follows.
+            <t>The algorithm for token passing works as follows:</t>
             
             <list type="numbers">
-              <t>LS1 receives the token i.e. LSControlRequest message 
+              <t>1. LS1 receives the token i.e. LSControlRequest message 
                     with the http://perfsonar.net/services/LS/token/
                     eventType from its predecessor L3.</t>
-              <t>LS1 updates its local peer list based on token content.</t>
-              <t>LS1 sends LSControlRequest message with the 
+              <t>2. LS1 updates its local peer list based on token 
content.</t>
+              <t>3. LS1 sends LSControlRequest message with the 
                  http://perfsonar.net/services/LS/summary/ eventType 
                  to all peers in the lease (excluding itself).</t>
-              <t>LS2 receiving this message checks its collection and 
updates it
+              <t>3. LS2 receiving this message checks its collection and 
updates it
                  if necessary with service info including "contentSize".</t>
-              <t>LS1 waits for some amount of time.</t>
-              <t>LS1 sends token to next LS (LS2) from the LSRing lower 
scope 
+              <t>4. LS1 waits for some amount of time.</t>
+              <t>5. LS1 sends token to next LS (LS2) from the LSRing lower 
scope 
                  (if it fails, try next one).</t>
             </list> 
             
-            </t>
           </section>
           
         </section>
@@ -681,7 +679,7 @@
           
           <t>
             <xref target="LSControl-Summary-lower" /> and 
-            <xref target="LSControl-Summary-upper" />contains examples of 
the 
+            <xref target="LSControl-Summary-upper" /> contain examples of 
the 
             message format for this exchange.  It is left up to the 
             implementation when the summarization occurs (i.e. at message 
             send time, or also as a periodic event).  
@@ -962,9 +960,9 @@
 
     <!-- Examples Section -->
 
-    <section anchor="structures-and-messages" title="structures and 
Messages">
+    <section anchor="structures-and-messages" title="Structures and 
Messages">
            
-           <section anchor="service-metadata" title="service metadata 
example">
+           <section anchor="service-metadata" title="Service metadata 
example">
              <t>Example of metadata describing information collected and 
stored in
                 Measurement Archive service</t>
              <t>
@@ -1180,6 +1178,7 @@
        <list style="symbols">
          <t>error.ls.foo - </t>
          <t>success.ls.foo - </t>
+         <t>TBD</t>
        </list>
     
     </section>