Binary file wi-addendum-local-services/Example_scenario_1/Slide1.png has changed

Binary file wi-addendum-local-services/Example_scenario_1/Slide2.png has changed

Binary file wi-addendum-local-services/Example_scenario_1/Slide3.png has changed

Binary file wi-addendum-local-services/Example_scenario_2/Slide1.png has changed

Binary file wi-addendum-local-services/Example_scenario_2/Slide2.png has changed

Binary file wi-addendum-local-services/Example_scenario_2/Slide3.png has changed

Binary file wi-addendum-local-services/Example_scenario_2/Slide4.png has changed

--- a/wi-addendum-local-services/Overview.html	Wed Jul 11 00:16:29 2012 -0400
+++ b/wi-addendum-local-services/Overview.html	Thu Jul 12 08:52:10 2012 +0200
@@ -380,25 +380,29 @@
             <ol class="rule">   
           
               <li>
-                The <a>UPnP enabled User Agent</a> maintains a list of announced services based on received SSDP NOTIFY messages
+                The <a>UPnP enabled User Agent</a> maintains a list of announced UPnP services based on received SSDP NOTIFY messages
                 with <code>NT</code> header equal to <code>urn:schemas-webintents-org:service:WebIntents:1</code>.
               </li>
               <br /> 
               <li>
                 When the navigator.startActivity method [[!WEBINTENTS]] is called the <a>UPnP enabled User Agent</a> checks the list
-                of of announced services for a service with an <code>action.webintents.org</code> header that matches the Action of the invoked intent.
-              </li> 
-              <br />
-              <li>
-                 For each match the <a>UPnP enabled User Agent</a> attempts to retrieve the Web Intents document document from the discovered <a>Web Intents enabled UPnP device</a>. The <a>UPnP enabled User Agent</a>
-                 may also attempt to retrieve the Web Intents document for announced services without an <code>action.webintents.org</code> header.             
-                 The location of the Web Intents document is the value of the <code>location.webintents.org</code> header. If this value is a relative URL the
-                 base URL is the base URL of the <code>LOCATION</code> header.  
-                 <br />  <br />
-                 If the <a>UPnP enabled User Agent</a> fails to retrieve the Web Intents document it silently disregards the received NOTIFY message.
-                 <br />  <br />
-                 If the <code>action.webintents.org</code> header does not match the <code>action</code> attribute in the retrieved Web Intents document 
-                 the <a>UPnP enabled User Agent</a> silently disregards the received NOTIFY message.
+                of of announced services and attempts to retrieve the Web Intents document from the discovered <a>Web Intents enabled UPnP device</a> in the following cases:                
+                <ul>
+                  <li>
+                    The received NOTIFY message contains an <code>action.webintents.org</code> header and this header matches the Action of the invoked intent.
+                  </li>
+                  <li>
+                    The received NOTIFY message does not contain an <code>action.webintents.org</code> header.
+                  </li>                
+                </ul>
+                <br />     
+                The location of the Web Intents document is the value of the <code>location.webintents.org</code> header. If this value is a relative URL the
+                base URL is the base URL of the <code>LOCATION</code> header.  
+                <br />  <br />
+                If the <a>UPnP enabled User Agent</a> fails to retrieve the Web Intents document it silently disregards the received NOTIFY message.
+                <br />  <br />
+                If the <code>action.webintents.org</code> header does not match the <code>action</code> attribute in the retrieved Web Intents document 
+                the <a>UPnP enabled User Agent</a> silently disregards the received NOTIFY message.
               </li>
               <br />         
               <li>
@@ -522,7 +526,13 @@
         <h3>View and control video on remote device through Client page control buttons</h3>
         <p>
           The following scenario describes how a Client page uses Web Intents to discover a remote video view service. The UI stays in the Client page, 
-          which contains the UI controls for the video playback.
+          which contains the UI controls for the video playback. This means that there is a need for continuous communication between the Client page and the Service page,
+          which is "hidden", i.e. it has no UI. The Client page creates a messaging channel and sends the messaging channel port to the Service page trhrough the intent invocation.
+          A high level "TV control" protocol, supporting commands such as "play", "pause" and "stop, runs on top of the messaging channel. 
+        </p>
+        <p>
+          In this example the assumption is that he Client invokes an intent to discover a Service that supports a specified protocol running on top of the message channel So the 
+          "discover" intent Action is used and Type is set to the specific protocol used to communicate with the Service.
         </p>
         
         <p class="issue">
@@ -576,4 +586,4 @@
         </p>
     </section>
   </body>
-</html>
+</html>
\ No newline at end of file