Clarify the terms 'new service', 'existing service' and 'current service'
authorRich Tibbett <richt@opera.com>
Fri, 08 Feb 2013 14:59:37 +0100
changeset 387abb49f62a775
parent 386 7b71fa04e89a
child 388 f6ad389be556
Clarify the terms 'new service', 'existing service' and 'current service'
discovery-api/Overview.src.html
     1.1 --- a/discovery-api/Overview.src.html	Thu Feb 07 15:59:53 2013 +0000
     1.2 +++ b/discovery-api/Overview.src.html	Fri Feb 08 14:59:37 2013 +0100
     1.3 @@ -291,6 +291,23 @@
     1.4          agent</a> generates and maintains for receiving HTTP NOTIFY requests from UPnP Event sources. It is only
     1.5          required when the user agent implements UPnP Service Discovery as defined in this specification.
     1.6        </p>
     1.7 +      <p>
     1.8 +        In this specification we use the following terms to describe the processes required for Local-networked
     1.9 +        Services management:
    1.10 +      </p>
    1.11 +      <ul>
    1.12 +        <li>A <dfn>new service</dfn> is a Local-networked Service that has not previously been discovered or registered
    1.13 +        in the <a>list of available service records</a>.
    1.14 +        </li>
    1.15 +        <li>An <dfn>existing service</dfn> is a Local-networked Service that has previously been discovered and is
    1.16 +        registered in the <a>list of available service records</a>.
    1.17 +        </li>
    1.18 +        <li>A <dfn>current service</dfn> is a Local-networked Service, represented by a <a href=
    1.19 +        "#networkservice"><code>NetworkService</code></a> object, that is currently being shared with a web page via a
    1.20 +        <a href="#networkservices"><code>NetworkServices</code></a> object registered in the <a>list of active service
    1.21 +        managers</a>.
    1.22 +        </li>
    1.23 +      </ul>
    1.24      </section>
    1.25      <section>
    1.26        <h2>
    1.27 @@ -1017,10 +1034,10 @@
    1.28          "#dom-navigator-getnetworkservices"><code>getNetworkServices()</code></a> algorithm.
    1.29        </p>
    1.30        <p>
    1.31 -        The rule for <dfn>adding an available service</dfn> is the process of adding a new service or updating an
    1.32 -        existing service that is generally available on the user's current network in the <a>list of available service
    1.33 -        records</a>. This rule takes one argument, <var>network service record</var>, and consists of running the
    1.34 -        following steps:
    1.35 +        The rule for <dfn>adding an available service</dfn> is the process of adding a <a>new service</a> or updating
    1.36 +        an <a>existing service</a> that is generally available on the user's current network in the <a>list of
    1.37 +        available service records</a>. This rule takes one argument, <var>network service record</var>, and consists of
    1.38 +        running the following steps:
    1.39        </p>
    1.40        <ol class="rule">
    1.41          <li>For each <var>existing service record</var> in the current <a>list of available service records</a>, run
    1.42 @@ -1082,9 +1099,10 @@
    1.43          </li>
    1.44        </ol>
    1.45        <p>
    1.46 -        The rule for <dfn>removing an available service</dfn> is the general process of removing a service from the
    1.47 -        <a>list of available service records</a> that has left the user's current network or has otherwise expired.
    1.48 -        This rule takes one argument, <var>service identifier</var>, and consists of running the following steps:
    1.49 +        The rule for <dfn>removing an available service</dfn> is the general process of removing an <a>existing
    1.50 +        service</a> from the <a>list of available service records</a> that has left the user's current network or has
    1.51 +        otherwise expired. This rule takes one argument, <var>service identifier</var>, and consists of running the
    1.52 +        following steps:
    1.53        </p>
    1.54        <ol class="rule">
    1.55          <li>For each <var>existing service record</var> in the current <a>list of available service records</a>, run
    1.56 @@ -1648,7 +1666,8 @@
    1.57                    class="externalDFN"><code>Event</code></a>
    1.58              </td>
    1.59              <td>
    1.60 -              When a new service that matches one of the <a>requested type tokens</a> is found in the current network.
    1.61 +              When a <a>new service</a> that matches one of the <a>requested type tokens</a> is found in the current
    1.62 +              network.
    1.63              </td>
    1.64            </tr>
    1.65            <tr>
    1.66 @@ -1660,7 +1679,7 @@
    1.67                    class="externalDFN"><code>Event</code></a>
    1.68              </td>
    1.69              <td>
    1.70 -              When an existing service that matches one of the <a>requested type tokens</a> gracefully leaves or
    1.71 +              When an <a>existing service</a> that matches one of the <a>requested type tokens</a> gracefully leaves or
    1.72                expires from the current network.
    1.73              </td>
    1.74            </tr>
    1.75 @@ -1673,7 +1692,7 @@
    1.76                    class="externalDFN"><code>Event</code></a>
    1.77              </td>
    1.78              <td>
    1.79 -              When a current service renews its service registration within the current network.
    1.80 +              When a <a>current service</a> renews its service registration within the current network.
    1.81              </td>
    1.82            </tr>
    1.83            <tr>
    1.84 @@ -1685,7 +1704,7 @@
    1.85                    class="externalDFN"><code>Event</code></a>
    1.86              </td>
    1.87              <td>
    1.88 -              When a current service gracefully leaves or otherwise expires from the current network.
    1.89 +              When a <a>current service</a> gracefully leaves or otherwise expires from the current network.
    1.90              </td>
    1.91            </tr>
    1.92            <tr>
    1.93 @@ -1698,7 +1717,7 @@
    1.94              </td>
    1.95              <td>
    1.96                When a valid UPnP Events Subscription Message is received on a <a>user-agent generated callback url</a>
    1.97 -              for a current service. This event never fires for Zeroconf-based services.
    1.98 +              for a <a>current service</a>. This event never fires for Zeroconf-based services.
    1.99              </td>
   1.100            </tr>
   1.101          </tbody>