W3C home > Mailing lists > Public > public-dap-commits@w3.org > February 2013

dap commit: Clarify the terms 'new service', 'existing service' and 'current service'

From: Mercurial notifier <cvsmail@w3.org>
Date: Fri, 08 Feb 2013 13:59:38 +0000
Message-Id: <E1U3oUM-0003Dv-QE@mcbain.w3.org>
To: public-dap-commits@w3.org
changeset:   387:abb49f62a775
tag:         tip
user:        Rich Tibbett <richt@opera.com>
date:        Fri Feb 08 14:59:37 2013 +0100
files:       discovery-api/Overview.src.html
description:
Clarify the terms 'new service', 'existing service' and 'current service'


diff -r 7b71fa04e89a -r abb49f62a775 discovery-api/Overview.src.html
--- a/discovery-api/Overview.src.html	Thu Feb 07 15:59:53 2013 +0000
+++ b/discovery-api/Overview.src.html	Fri Feb 08 14:59:37 2013 +0100
@@ -291,6 +291,23 @@
         agent</a> generates and maintains for receiving HTTP NOTIFY requests from UPnP Event sources. It is only
         required when the user agent implements UPnP Service Discovery as defined in this specification.
       </p>
+      <p>
+        In this specification we use the following terms to describe the processes required for Local-networked
+        Services management:
+      </p>
+      <ul>
+        <li>A <dfn>new service</dfn> is a Local-networked Service that has not previously been discovered or registered
+        in the <a>list of available service records</a>.
+        </li>
+        <li>An <dfn>existing service</dfn> is a Local-networked Service that has previously been discovered and is
+        registered in the <a>list of available service records</a>.
+        </li>
+        <li>A <dfn>current service</dfn> is a Local-networked Service, represented by a <a href=
+        "#networkservice"><code>NetworkService</code></a> object, that is currently being shared with a web page via a
+        <a href="#networkservices"><code>NetworkServices</code></a> object registered in the <a>list of active service
+        managers</a>.
+        </li>
+      </ul>
     </section>
     <section>
       <h2>
@@ -1017,10 +1034,10 @@
         "#dom-navigator-getnetworkservices"><code>getNetworkServices()</code></a> algorithm.
       </p>
       <p>
-        The rule for <dfn>adding an available service</dfn> is the process of adding a new service or updating an
-        existing service that is generally available on the user's current network in the <a>list of available service
-        records</a>. This rule takes one argument, <var>network service record</var>, and consists of running the
-        following steps:
+        The rule for <dfn>adding an available service</dfn> is the process of adding a <a>new service</a> or updating
+        an <a>existing service</a> that is generally available on the user's current network in the <a>list of
+        available service records</a>. This rule takes one argument, <var>network service record</var>, and consists of
+        running the following steps:
       </p>
       <ol class="rule">
         <li>For each <var>existing service record</var> in the current <a>list of available service records</a>, run
@@ -1082,9 +1099,10 @@
         </li>
       </ol>
       <p>
-        The rule for <dfn>removing an available service</dfn> is the general process of removing a service from the
-        <a>list of available service records</a> that has left the user's current network or has otherwise expired.
-        This rule takes one argument, <var>service identifier</var>, and consists of running the following steps:
+        The rule for <dfn>removing an available service</dfn> is the general process of removing an <a>existing
+        service</a> from the <a>list of available service records</a> that has left the user's current network or has
+        otherwise expired. This rule takes one argument, <var>service identifier</var>, and consists of running the
+        following steps:
       </p>
       <ol class="rule">
         <li>For each <var>existing service record</var> in the current <a>list of available service records</a>, run
@@ -1648,7 +1666,8 @@
                   class="externalDFN"><code>Event</code></a>
             </td>
             <td>
-              When a new service that matches one of the <a>requested type tokens</a> is found in the current network.
+              When a <a>new service</a> that matches one of the <a>requested type tokens</a> is found in the current
+              network.
             </td>
           </tr>
           <tr>
@@ -1660,7 +1679,7 @@
                   class="externalDFN"><code>Event</code></a>
             </td>
             <td>
-              When an existing service that matches one of the <a>requested type tokens</a> gracefully leaves or
+              When an <a>existing service</a> that matches one of the <a>requested type tokens</a> gracefully leaves or
               expires from the current network.
             </td>
           </tr>
@@ -1673,7 +1692,7 @@
                   class="externalDFN"><code>Event</code></a>
             </td>
             <td>
-              When a current service renews its service registration within the current network.
+              When a <a>current service</a> renews its service registration within the current network.
             </td>
           </tr>
           <tr>
@@ -1685,7 +1704,7 @@
                   class="externalDFN"><code>Event</code></a>
             </td>
             <td>
-              When a current service gracefully leaves or otherwise expires from the current network.
+              When a <a>current service</a> gracefully leaves or otherwise expires from the current network.
             </td>
           </tr>
           <tr>
@@ -1698,7 +1717,7 @@
             </td>
             <td>
               When a valid UPnP Events Subscription Message is received on a <a>user-agent generated callback url</a>
-              for a current service. This event never fires for Zeroconf-based services.
+              for a <a>current service</a>. This event never fires for Zeroconf-based services.
             </td>
           </tr>
         </tbody>
Received on Friday, 8 February 2013 13:59:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 8 February 2013 13:59:40 GMT