discovery-api/Overview.src.html
author Rich Tibbett <richt@opera.com>
Mon, 04 Feb 2013 13:47:41 +0100
changeset 371 8b03e17da083
parent 332 e19dc529aacc
child 372 7639401e21f4
permissions -rw-r--r--
Rewrite Step 9 of getNetworkService algorithm following feedback @ http://lists.w3.org/Archives/Public/public-device-apis/2012Sep/0141.html
     1 <!DOCTYPE html>
     2 <!--
     3 
     4   THIS IS THE WORKING VERSION OF THE CURRENT SPECIFICATION!
     5 
     6   This specification is built using ReSpec.js <http://dev.w3.org/2009/dap/ReSpec.js/documentation.html>
     7 
     8   From time to time it's necessary to HTML5 Tidy this document using the tool @ <http://w3c.github.com/tidy-html5/>.
     9 
    10   The command used to format this document (Overview.src.html) is as follows (replacing all = signs with - signs!):
    11 
    12   @> tidy ==new-blocklevel-tags section ==char-encoding utf8 ==tidy-mark no ==indent yes ==indent-spaces 2 ==indent-attributes yes ==wrap 120 ==fix-bad-comments yes -m Overview.src.html
    13 
    14   To publish a new compiled version (Overview.html), we need to open this file (Overview.src.html) in any web browser.
    15   Once it has loaded we press 'Ctrl + Shift + S' (or 'Cmd' + 'Shift' + 'S' on Mac) and then select
    16   'Save as HTML (Source)' from the resulting menu.
    17 
    18   We then replace Overview.html with the produced HTML source of this process.
    19 
    20   Next we run HTML5 Tidy over our new Overview.html file with the following command (replacing all = signs with - signs!):
    21 
    22   @> tidy ==new-blocklevel-tags section ==char-encoding utf8 ==tidy-mark no ==indent yes ==indent-spaces 2 ==indent-attributes yes ==wrap 120 ==hide-comments yes -m Overview.html
    23 
    24   Now the specification is ready to be published :)
    25 
    26 -->
    27 <html>
    28   <head>
    29     <title>
    30       Network Service Discovery
    31     </title>
    32     <meta http-equiv='Content-Type'
    33           content='text/html; charset=utf-8'>
    34     <script type="text/javascript"
    35           class='remove'>
    36 var respecConfig = {
    37           specStatus:   "ED",
    38           //publishDate:  "2012-10-04",
    39           shortName:    "discovery-api",
    40           edDraftURI:   "http://dvcs.w3.org/hg/dap/raw-file/tip/discovery-api/Overview.html",
    41           previousMaturity: "FPWD",
    42           previousPublishDate: "2012-08-07",
    43           editors: [
    44             {
    45               name:       "Rich Tibbett",
    46               //url:        "http://richt.me/",
    47               company:    "Opera Software ASA",
    48               companyURL: "http://opera.com/"
    49             },
    50             {
    51               name:       "Clarke Stevens",
    52               //url:      "",
    53               company:    "CableLabs",
    54               companyURL: "http://cablelabs.com/"
    55             }
    56           ],
    57           noIDLIn:      true,
    58           wg:           "Device APIs Working Group",
    59           wgURI:        "http://www.w3.org/2009/dap/",
    60           wgPublicList: "public-device-apis",
    61           wgPatentURI:  "http://www.w3.org/2004/01/pp-impl/43696/status"
    62       };
    63     </script>
    64     <script src='http://www.w3.org/Tools/respec/respec-w3c-common'
    65           type="text/javascript"
    66           class='remove'
    67           async="">
    68 </script>
    69     <style type="text/css">
    70 /* Custom ReSpec CSS (by Rich Tibbett) */
    71 
    72       /* Add better spacing to sections */
    73       section, .section { margin-bottom: 2em; }
    74 
    75       /* Reduce note & issue render size */
    76       .note, .issue { font-size:0.8em; }
    77 
    78       /* Add addition spacing to <ol> and <ul> for rule definition */
    79       ol.rule li, ul.rule li { padding:0.6em; }
    80 
    81       pre.widl { border: solid thin; background: #EEEEEE; color: black; padding: 0.5em 1em; position: relative; }
    82       pre.widl :link, pre.widl :visited { color: #000; background: transparent; }
    83       pre.widl:before { content: "IDL"; font: bold small sans-serif; padding: 0.5em; background: white; position: absolute; top: 0; margin: -1px 0 0 -4em; width: 1.5em; border: thin solid; border-radius: 0 0 0 0.5em }
    84 
    85       div.example { border: solid thin red; background: #F7DFE5; color: black; padding: 0.5em 1em; position: relative; margin: 1em 0 1em 4.6em; width: auto; }
    86       div.example:before { content: "EXAMPLE"; font: bold small sans-serif; padding: 0.5em; background: red; color: white; position: absolute; top: 0; margin: -1px 0 0 -7.6em; width: 5em; border: thin solid red; border-radius: 0 0 0 0.5em }
    87 
    88       dl.domintro { color: green; margin: 2em 0 2em 2em; padding: 0.5em 1em; border: none; background: #DDFFDD; }
    89       hr + dl.domintro, div.impl + dl.domintro { margin-top: 2.5em; margin-bottom: 1.5em; }
    90       dl.domintro dt, dl.domintro dt * { color: black; text-decoration: none; }
    91       dl.domintro dd { margin: 0.5em 0 1em 2em; padding: 0; }
    92       dl.domintro dd p { margin: 0.5em 0; }
    93       dl.domintro code {font-size: inherit; font-style: italic; }
    94       dl.domintro:before { display: table; margin: -1em -0.5em 0.5em auto; width: auto; content: 'This box is non-normative. Implementation requirements are given below this box.'; color: red; border: solid 2px; background: white; padding: 0 0.25em; }
    95 
    96       table { border-collapse:collapse; border-style:hidden hidden none hidden }
    97       table thead { border-bottom:solid }
    98       table tbody th:first-child { border-left:solid }
    99       table td, table th { border-left:solid; border-right:solid; border-bottom:solid thin; vertical-align:top; padding:0.2em }
   100     </style>
   101   </head>
   102   <body>
   103     <section id='abstract'>
   104       <p>
   105         This specification defines a mechanism for an HTML document to discover and subsequently communicate with
   106         <abbr title="Hypertext Transfer Protocol">HTTP</abbr>-based services advertised via common discovery protocols
   107         within the current network.
   108       </p>
   109     </section>
   110     <section id='sotd'>
   111       <p>
   112         This document represents the early consensus of the group on the scope and features of the proposed API.
   113       </p>
   114     </section>
   115     <section class="informative">
   116       <h3>
   117         Introduction
   118       </h3>
   119       <p>
   120         To enable Web pages to connect and communicate with Local-networked Services provided over HTTP, this
   121         specification introduces the <a href="#navigatornetworkservice"><code>NavigatorNetworkService</code></a>
   122         interface.
   123       </p>
   124       <p>
   125         Using this <abbr title="Application Programming Interface">API</abbr> consists of requesting a well-known
   126         service type, known by developers and advertised by Local-networked Devices. User authorization, where the user
   127         connects the web page to discovered services, is expected before the web page is able to interact with any
   128         Local-networked Services.
   129       </p>
   130       <p>
   131         A web page creates a request to obtain connectivity to services running in the network by specifying a
   132         well-known discovery service type that it wishes to interact with.
   133       </p>
   134       <p>
   135         The user agent, having captured all advertised services on the network from the <a>service discovery
   136         mechanisms</a> included in this recommendation, attempts to match the requested service type to a discovered
   137         service according to the processing described herein.
   138       </p>
   139       <p>
   140         If a service connectivity request is successful then the Web page is provided with the necessary information to
   141         communicate with the authorized Local-networked Service. If the request fails then the Web page will receive an
   142         error callback containing an error code describing the cause of Local-networked Service connectivity failure.
   143       </p>
   144       <p>
   145         Once connected to a Local-networked Service the Web page can send requests and receive responses to the
   146         Local-networked Service via the messaging format and appropriate channel inferred from the service type
   147         authorized via the provided API. The Web page, once connected, can also receive service-pushed events, in the
   148         messaging format supported by the Local-networked Device, if such event subscription functionality is provided
   149         by the connected Local-networked Service.
   150       </p>
   151       <div class="example">
   152         <p>
   153           Example of requesting a DNS-SD advertised service:
   154         </p>
   155         <hr>
   156         <pre class="highlight">
   157 function showServices( services ) {
   158   // Show a list of all the services provided to the web page
   159   for(var i = 0, l = services.length; i &lt; l; i++) console.log( services[i].name );
   160 }
   161 
   162 navigator.getNetworkServices('zeroconf:_boxee-jsonrpc._tcp', showServices);
   163 </pre>
   164       </div>
   165       <div class="example">
   166         <p>
   167           Example of requesting a UPnP advertised service, also handling error conditions:
   168         </p>
   169         <hr>
   170         <pre class="highlight">
   171 function showServices( services ) {
   172   // Show a list of all the services provided to the web page
   173   for(var i = 0, l = services.length; i &lt; l; i++) console.log( services[i].name );
   174 }
   175 
   176 function error( e ) {
   177   console.log( "Error occurred: " + e.code );
   178 }
   179 
   180 navigator.getNetworkServices('upnp:urn:schemas-upnp-org:service:ContentDirectory:1', showServices, error);
   181 </pre>
   182       </div>
   183       <div class="example">
   184         <p>
   185           Example of requesting either a DNS-SD or UPnP advertised service:
   186         </p>
   187         <hr>
   188         <pre class="highlight">
   189 function showServices( services ) {
   190   // Show a list of all the services provided to the web page (+ service type)
   191   for(var i = 0, l = services.length; i &lt; l; i++)
   192      console.log( services[i].name + '(' + services[i].type + ')' );
   193 }
   194 
   195 navigator.getNetworkServices([
   196   'zeroconf:_boxee-jsonrpc._tcp',
   197   'upnp:urn:schemas-upnp-org:service:ContentDirectory:1'
   198 ], showServices);
   199 </pre>
   200       </div>
   201       <p>
   202         For more detailed examples see the <a href="#examples">Examples</a> section.
   203       </p>
   204     </section>
   205     <section id='conformance'>
   206       <p>
   207         Requirements phrased in the imperative as part of algorithms (such as "strip any leading space characters" or
   208         "return false and abort these steps") are to be interpreted with the meaning of the key word ("must", "should",
   209         "may", etc) used in introducing the algorithm.
   210       </p>
   211       <p>
   212         Some conformance requirements are phrased as requirements on attributes, methods or objects. Such requirements
   213         are to be interpreted as requirements on user agents.
   214       </p>
   215       <p>
   216         Conformance requirements phrased as algorithms or specific steps MAY be implemented in any manner, so long as
   217         the end result is equivalent. (In particular, the algorithms defined in this specification are intended to be
   218         easy to follow, and not intended to be performant.)
   219       </p>
   220       <p>
   221         The only conformance class defined by this specification is a <dfn>user agent</dfn>.
   222       </p>
   223       <p>
   224         User agents MAY impose implementation-specific limits on otherwise unconstrained inputs, e.g. to prevent denial
   225         of service attacks, to guard against running out of memory, or to work around platform-specific limitations.
   226       </p>
   227       <p>
   228         When support for a feature is disabled (e.g. as an emergency measure to mitigate a security problem, or to aid
   229         in development, or for performance reasons), user agents MUST act as if they had no support for the feature
   230         whatsoever, and as if the feature was not mentioned in this specification. For example, if a particular feature
   231         is accessed via an attribute in a Web IDL interface, the attribute itself would be omitted from the objects
   232         that implement that interface - leaving the attribute on the object but making it return null or throw an
   233         exception is insufficient.
   234       </p>
   235       <section>
   236         <h3>
   237           Dependencies
   238         </h3>This specification relies on several other underlying specifications.
   239         <dl>
   240           <dt>
   241             HTML
   242           </dt>
   243           <dd>
   244             Many fundamental concepts from HTML are used by this specification. [[!HTML5]]
   245           </dd>
   246           <dt>
   247             WebIDL
   248           </dt>
   249           <dd>
   250             The IDL blocks in this specification use the semantics of the WebIDL specification. [[!WEBIDL]]
   251           </dd>
   252         </dl>
   253       </section>
   254     </section>
   255     <section>
   256       <h3>
   257         Terminology
   258       </h3>
   259       <p>
   260         The construction "a <code>Foo</code> object", where <code>Foo</code> is actually an interface, is sometimes
   261         used instead of the more accurate "an object implementing the interface <code>Foo</code>".
   262       </p>
   263       <p>
   264         The term DOM is used to refer to the API set made available to scripts in Web applications, and does not
   265         necessarily imply the existence of an actual <code>Document</code> object or of any other <code>Node</code>
   266         objects as defined in the DOM Core specifications. [[!DOM4]]
   267       </p>
   268       <p>
   269         An IDL attribute is said to be <em>getting</em> when its value is being retrieved (e.g. by author script), and
   270         is said to be <em>setting</em> when a new value is assigned to it.
   271       </p>
   272       <p>
   273         A <dfn>valid service type</dfn> is any of the following:
   274       </p>
   275       <ul>
   276         <li>a string that begins with <code>upnp:</code> or <code>zeroconf:</code> followed by one or more characters
   277         in the ranges U+0021, U+0023 to U+0027, U+002A to U+002B, U+002D to U+002E, U+0030 to U+0039, U+0041 to U+005A,
   278         U+005E to U+007E.
   279         </li>
   280         <li>a string that begins with <code>dial:</code> followed by an integer version.
   281         </li>
   282       </ul>
   283       <p>
   284         A <a>valid service type</a> provided in the <code>type</code> attribute of the <a href=
   285         "#dom-navigator-getnetworkservices"><code>getNetworkServices()</code></a> method will be matched against the
   286         services currently contained in the <a>list of available service records</a> according to the algorithms
   287         defined in this specification.
   288       </p>
   289       <p>
   290         A <dfn>user-agent generated callback url</dfn> is a Local-network accessible URL endpoint that a <a>user
   291         agent</a> generates and maintains for receiving HTTP NOTIFY requests from UPnP Event sources. It is only
   292         required when the user agent implements UPnP Service Discovery as defined in this specification.
   293       </p>
   294     </section>
   295     <section>
   296       <h2>
   297         Requesting networked services
   298       </h2>
   299       <pre class="widl">
   300 [Supplemental, NoInterfaceObject]
   301 interface <dfn id="navigatornetworkservice">NavigatorNetworkService</dfn> {
   302   // Obtain a Local-networked Service
   303   void <a href="#dom-navigator-getnetworkservices">getNetworkServices</a>( in any type,
   304                            in <a href=
   305 "#navigatornetworkservicesuccesscallback">NavigatorNetworkServiceSuccessCallback</a> successCallback,
   306                            in optional <a href=
   307 "#navigatornetworkserviceerrorcallback">NavigatorNetworkServiceErrorCallback</a> errorCallback );
   308 };
   309 <a class="externalDFN"
   310      href=
   311      "http://www.whatwg.org/specs/web-apps/current-work/complete/timers.html#navigator">Navigator</a> implements <a href=
   312      "#navigatornetworkservice">NavigatorNetworkService</a>;
   313 
   314 [Callback=FunctionOnly, NoInterfaceObject]
   315 interface <dfn id="navigatornetworkservicesuccesscallback">NavigatorNetworkServiceSuccessCallback</dfn> {
   316   void handleEvent( in <a href="#networkservices">NetworkServices</a> services );
   317 };
   318 
   319 [NoInterfaceObject]
   320 interface <dfn id="navigatornetworkserviceerror">NavigatorNetworkServiceError</dfn> {
   321   const unsigned short <a href="#dom-navigatornetworkserviceerror-permission_denied">PERMISSION_DENIED_ERR</a> = 1;
   322   const unsigned short <a href="#dom-navigatornetworkserviceerror-unknown_type_prefix">UNKNOWN_TYPE_PREFIX_ERR</a> = 2;
   323   readonly attribute unsigned short <a href="#dom-navigatornetworkserviceerror-code">code</a>;
   324 };
   325 
   326 [Callback=FunctionOnly, NoInterfaceObject]
   327 interface <dfn id="navigatornetworkserviceerrorcallback">NavigatorNetworkServiceErrorCallback</dfn> {
   328   void handleEvent( in <a href="#navigatornetworkserviceerror">NavigatorNetworkServiceError</a> error );
   329 };
   330 </pre>
   331       <section>
   332         <h2>
   333           Methods
   334         </h2>
   335         <dl class="domintro">
   336           <dt>
   337             <var title="">window</var> . <code title="dom-navigator"><a href=
   338             "http://www.whatwg.org/specs/web-apps/current-work/complete/timers.html#navigator">navigator</a></code> .
   339             <code title="dom-navigator-getNetworkServices"><a href=
   340             "#dom-navigator-getnetworkservices">getNetworkServices</a></code> ( <var title="">type</var> , <var title=
   341             "">successCallback</var> [, <var title="">errorCallback</var> ] )
   342           </dt>
   343           <dd>
   344             <p>
   345               Prompts the user to select discovered network services that have advertised support for the requested
   346               service type.
   347             </p>
   348             <p>
   349               The <var title="">type</var> argument contains one or more <a>valid service type</a> tokens that the web
   350               page would like to interact with.
   351             </p>
   352             <p>
   353               If the user accepts, the <var title="">successCallback</var> is invoked, with zero or more <a href=
   354               "#networkservice"><code>NetworkService</code></a> objects as its argument.
   355             </p>
   356             <p>
   357               If the user declines, the <var title="">errorCallback</var> (if any) is invoked.
   358             </p>
   359           </dd>
   360         </dl>
   361         <div>
   362           <p>
   363             When the <dfn id="dom-navigator-getnetworkservices"
   364                title="dom-navigator-getnetworkservices"><code>getNetworkServices(type, successCallback[,
   365                errorCallback])</code></dfn> method is called, the <a>user agent</a> MUST run the following steps:
   366           </p>
   367           <ol class="rule">
   368             <li>Let <var>requested control types</var> be initially set to an empty array.
   369             </li>
   370             <li>If <var>type</var> is an array consisting of one or more <a>valid service type</a> tokens, then let
   371             <var>requested control types</var> by the value of <var>type</var>, removing any non-<a>valid service
   372             type</a> tokens from the resulting array.
   373             </li>
   374             <li>If <var>type</var> is a string consisting of one <a>valid service type</a> token, then let
   375             <var>requested control types</var> be an array containing one item with a value of <var>type</var>.
   376             </li>
   377             <li>If <var>requested control types</var> is an array that contains at least one or more <a title=
   378             "valid service type">valid service type</a> tokens then continue to the step labeled <em>process</em>
   379             below. Otherwise, the <a>user agent</a> MUST <a href=
   380             "http://www.whatwg.org/specs/web-apps/current-work/complete/webappapis.html#queue-a-task"
   381                   class="externalDFN">queue a task</a> to invoke <var>errorCallback</var>, if it is provided and is an
   382                   object of type <code>Function</code>, with a new <a href=
   383                   "#navigatornetworkserviceerror"><code>NavigatorNetworkServiceError</code></a> object whose <a href=
   384                   "#dom-navigatornetworkserviceerror-code"><code>code</code></a> attribute has the numeric value 2
   385                   (<a href=
   386                   "#dom-navigatornetworkserviceerror-unknown_type_prefix"><code>UNKNOWN_TYPE_PREFIX_ERR</code></a>) as
   387                   its argument, abort any remaining steps and return.
   388             </li>
   389             <li>
   390               <em>Process</em>: Let <var>services found</var> be an empty array.
   391             </li>
   392             <li>For each <var>available service</var> in the <a>list of available service records</a> run the following
   393             steps:
   394               <ol class="rule">
   395                 <li>For each <var>requested control type</var> in <var>requested control types</var>: If <var>available
   396                 service</var>'s <code>type</code> attribute equals the <var>requested control type</var> then let <var>
   397                   matched service</var> equal the value of <var>available service</var> and continue at the step
   398                   labeled <var>attach</var> below.
   399                 </li>
   400                 <li>Continue at the next <var>available service</var>.
   401                 </li>
   402                 <li>
   403                   <em>Attach</em>: If <var>matched service</var> is not empty then run the following steps:
   404                   <ol class="rule">
   405                     <li>Let <var>new service object</var> be a new <a href=
   406                     "#networkservice"><code>NetworkService</code></a> object, mapping the parameters of <var>matched
   407                     service</var> to this new object where possible.
   408                     </li>
   409                     <li>Append <var>new service object</var> to the <var>services found</var> array.
   410                     </li>
   411                   </ol>
   412                 </li>
   413               </ol>
   414             </li>
   415             <li>Return, and run the remaining steps asynchronously.
   416             </li>
   417             <li>Optionally, e.g. based on a previously-established user preference, for security reasons, or due to
   418             platform limitations, the <a>user agent</a> MAY <a href=
   419             "http://www.whatwg.org/specs/web-apps/current-work/complete/webappapis.html#queue-a-task"
   420                   class="externalDFN">queue a task</a> to invoke <var>errorCallback</var>, if it is provided and is an
   421                   object of type <code>Function</code>, with a new <a href=
   422                   "#navigatornetworkserviceerror"><code>NavigatorNetworkServiceError</code></a> object whose <a href=
   423                   "#dom-navigatornetworkserviceerror-code"><code>code</code></a> attribute has the numeric value 1
   424                   (<a href=
   425                   "#dom-navigatornetworkserviceerror-permission_denied"><code>PERMISSION_DENIED_ERR</code></a>) as its
   426                   argument, abort any remaining steps and return.
   427             </li>
   428             <li>The user agent MUST NOT provide the entry script's origin with a <a href=
   429             "#networkservices"><code>NetworkServices</code></a> object without prior permission given by the user.
   430               <p>
   431                 If <var>services found</var> is not an empty array then the <a>user agent</a> MAY choose to prompt the
   432                 user in a user-agent-specific manner for permission to provide the <a href=
   433                 "http://www.whatwg.org/specs/web-apps/current-work/complete/browsers.html#entry-script"
   434                    class="externalDFN">entry script</a>'s <a href=
   435                    "http://www.whatwg.org/specs/web-apps/current-work/complete/origin-0.html#origin"
   436                    class="externalDFN">origin</a> with a <a href="#networkservices"><code>NetworkServices</code></a>
   437                    object representing the <a>user-authorized</a> subset of <var>services found</var>.
   438               </p>
   439               <p>
   440                 Alternatively, the user agent MAY choose to queue a task to invoke <var>successCallback</var> or
   441                 <var>errorCallback</var> immediately based on a previously-established user preference, for security
   442                 reasons, or due to platform limitations. In such an implementation, if <var>successCallback</var> is to
   443                 be fired as a result of a previously-established user preference then the <a>user agent</a> MUST
   444                 continue at the next step of this algorithm.
   445               </p>
   446               <p>
   447                 If permission has been granted by the user to access one or more networked services then the <a>user
   448                 agent</a> SHOULD include an "ongoing local-network communication" indicator.
   449               </p>
   450               <p>
   451                 If permission has been denied by the user, <a>user agent</a> or platform, then the <a>user agent</a>
   452                 MUST <a href="http://www.whatwg.org/specs/web-apps/current-work/complete/webappapis.html#queue-a-task"
   453                    class="externalDFN">queue a task</a> to invoke <var>errorCallback</var>, if it is provided and is an
   454                    object of type <code>Function</code>, with a new <a href=
   455                    "#navigatornetworkserviceerror"><code>NavigatorNetworkServiceError</code></a> object whose <a href=
   456                    "#dom-navigatornetworkserviceerror-code"><code>code</code></a> attribute has the numeric value 1
   457                    (<a href=
   458                    "#dom-navigatornetworkserviceerror-permission_denied"><code>PERMISSION_DENIED_ERR</code></a>) as its
   459                    argument, abort any remaining steps and return.
   460               </p>
   461               <p>
   462                 If the user never responds or no previously-established user preference has been met, this algorithm
   463                 stalls on this step.
   464               </p>
   465             </li>
   466             <li>Let <var>services</var> be an empty array.
   467             </li>
   468             <li>If <var>services found</var> is not an empty array then set <var>services</var> to be an array of one
   469             or more <a href="#networkservice"><code>NetworkService</code></a> objects for which the user granted
   470             permission above - known as the current objects <dfn>user-authorized</dfn> services.
   471             </li>
   472             <li>For each Object <var>service</var> in <var>services</var>, if any, run the following sub-steps:
   473               <ol class="rule">
   474                 <li>Add the <var>service</var>'s <code>url</code> parameter to the <a>entry script origin's
   475                   <abbr title="Uniform Resource Locator">URL</abbr> whitelist</a>.
   476                 </li>
   477                 <li>If <var>service</var>'s <code>type</code> parameter begins with the DOMString "<code>upnp:</code>"
   478                 and the <var>service</var>'s <code>eventsUrl</code> parameter is not empty then <a>setup a UPnP Events
   479                 Subscription</a> for <var>service</var>.
   480                 </li>
   481               </ol>
   482             </li>
   483             <li>Let <var>services manager</var> be a new <a href="#networkservices"><code>NetworkServices</code></a>
   484             object.
   485             </li>
   486             <li>Set <var>services manager</var>'s <a href=
   487             "#dom-networkservices-servicesavailable"><code>servicesAvailable</code></a> attribute to the number of
   488             items currently found in the <a>list of available service records</a> whose <code>type</code> property
   489             matches any of the tokens requested in <var>requested control types</var>.
   490             </li>
   491             <li>Add <var>services</var>, if any, to the <var>services manager</var> object as its collection of
   492             <a>indexed properties</a>. If <var>services</var> is an empty array then the <var>services manager</var>
   493             does not have any <var>indexed properties</var>.
   494             </li>
   495             <li>Set <var>services manager</var>'s <a href="#dom-networkservices-length"><code>length</code></a>
   496             attribute to the number of items in <var>services</var>.
   497             </li>
   498             <li>Add <var>services manager</var> to the <a>list of active service managers</a>.
   499             </li>
   500             <li>The <a>user agent</a> MUST <a href=
   501             "http://www.whatwg.org/specs/web-apps/current-work/complete/webappapis.html#queue-a-task"
   502                   class="externalDFN">queue a task</a> to invoke <var>successCallback</var> with <var>services
   503                   manager</var> as its argument.
   504             </li>
   505           </ol>
   506           <p>
   507             The <a href="http://www.whatwg.org/specs/web-apps/current-work/complete/webappapis.html#task-source"
   508                class="externalDFN">task source</a> for these <a href=
   509                "http://www.whatwg.org/specs/web-apps/current-work/complete/webappapis.html#concept-task"
   510                class="externalDFN">tasks</a> is the <a href=
   511                "http://www.whatwg.org/specs/web-apps/current-work/complete/webappapis.html#user-interaction-task-source"
   512                class="externalDFN">user interaction task source</a>.
   513           </p>
   514           <p>
   515             When a <a href="#networkservice"><code>NetworkService</code></a> object is provided to a Web page, the
   516             <a>user agent</a> MUST add the <code>url</code> property to the <dfn>entry script origin's URL
   517             whitelist</dfn>. This list enables the Web page to override and initiate cross-site resource requests
   518             towards these URLs, and any sub-resources of these URLs, within the current <a href=
   519             "http://www.whatwg.org/specs/web-apps/current-work/complete/browsers.html#entry-script"
   520                class="externalDFN">entry script</a>'s <a href=
   521                "http://www.whatwg.org/specs/web-apps/current-work/complete/origin-0.html#origin"
   522                class="externalDFN">origin</a> via various existing mechanisms (e.g. Web Sockets, Server-Sent Events,
   523                Web Messaging, XMLHttpRequest).
   524           </p>
   525           <p>
   526             If the user navigates away from the <a href=
   527             "http://www.whatwg.org/specs/web-apps/current-work/complete/browsers.html#entry-script"
   528                class="externalDFN">entry script</a>'s <a href=
   529                "http://www.whatwg.org/specs/web-apps/current-work/complete/origin-0.html#origin"
   530                class="externalDFN">origin</a> then the <a>user agent</a> <em class="ct">MUST</em> remove all previously
   531                whitelisted urls from the <a>entry script origin's URL whitelist</a>. There is no persistence to network
   532                service selections provided to a web page. It is not possible to access a previously white-listed
   533                networked service without the necessary user authorization in all of the following cases:
   534           </p>
   535           <ul>
   536             <li>If the current script is reloaded at any point in the same or different window.
   537             </li>
   538             <li>if the current script reinvokes the <a href=
   539             "#dom-navigator-getnetworkservices"><code>getNetworkServices()</code></a> method at any point in its
   540             execution.
   541             </li>
   542             <li>If the user navigates forward or back in their history to reload the current page.
   543             </li>
   544             <li>If a script is running in a different origin.
   545             </li>
   546           </ul>
   547         </div>
   548       </section>
   549       <section>
   550         <h3>
   551           Error Handling
   552         </h3>
   553         <dl class="domintro">
   554           <dt>
   555             <var title="">error</var> . <code title="dom-NavigatorNetworkServiceError-code"><a href=
   556             "#dom-navigatornetworkserviceerror-code">code</a></code>
   557           </dt>
   558           <dd>
   559             <p>
   560               Returns the current error's error code. At the current time, this will be <code>1</code> or
   561               <code>2</code>, for which the corresponding error constants <a href=
   562               "#dom-navigatornetworkserviceerror-permission_denied"><code>PERMISSION_DENIED_ERR</code></a> and <a href=
   563               "#dom-navigatornetworkserviceerror-unknown_type_prefix"><code>UNKNOWN_TYPE_PREFIX_ERR</code></a> are
   564               defined.
   565             </p>
   566           </dd>
   567         </dl>
   568         <p>
   569           The <dfn id="dom-navigatornetworkserviceerror-code"
   570              title="dom-navigatornetworkserviceerror-code"><code>code</code></dfn> attribute of a <a href=
   571              "#navigatornetworkserviceerror"><code>NavigatorNetworkServiceError</code></a> object <em class=
   572              "ct">MUST</em> return the code for the error, which will be one of the following:
   573         </p>
   574         <dl>
   575           <dt>
   576             <dfn id="dom-navigatornetworkserviceerror-permission_denied"
   577                 title="dom-navigatornetworkserviceerror-permission_denied"><code>PERMISSION_DENIED_ERR</code></dfn>
   578                 (numeric value 1)
   579           </dt>
   580           <dd>
   581             The user or user agent denied the page permission to access any services.
   582           </dd>
   583           <dt>
   584             <dfn id="dom-navigatornetworkserviceerror-unknown_type_prefix"
   585                 title="dom-navigatornetworkserviceerror-unknown_type_prefix"><code>UNKNOWN_TYPE_PREFIX_ERR</code></dfn>
   586                 (numeric value 2)
   587           </dt>
   588           <dd>
   589             No <a>valid service type</a> tokens were provided in the method invocation.
   590           </dd>
   591         </dl>
   592       </section>
   593     </section>
   594     <section>
   595       <h2>
   596         Obtaining networked services
   597       </h2>
   598       <p>
   599         The <a href="#networkservices"><code>NetworkServices</code></a> interface represents a collection of zero or
   600         more <dfn>indexed properties</dfn> that are each a <a>user-authorized</a> <a href=
   601         "#networkservice"><code>NetworkService</code></a> object.
   602       </p>
   603       <p>
   604         A <a href="#networkservices"><code>NetworkServices</code></a> object is the top level success callback
   605         parameter from a call to <a href="#dom-navigator-getnetworkservices"><code>getNetworkServices()</code></a>.
   606       </p>
   607       <pre class="widl">
   608 [NoInterfaceObject]
   609 interface <dfn id="networkservices">NetworkServices</dfn> {
   610   readonly attribute unsigned long    <a href="#dom-networkservices-length">length</a>;
   611   getter <a href="#networkservice">NetworkService</a> (unsigned long index);
   612   <a href="#networkservice">NetworkService</a>? <a href=
   613 "#dom-networkservices-getservicebyid">getServiceById</a>(DOMString id);
   614 
   615   readonly attribute unsigned long    <a href="#dom-networkservices-servicesavailable">servicesAvailable</a>;
   616 
   617   // event handler attributes
   618            attribute <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/webappapis.html#eventhandler"
   619      class="externalDFN">EventHandler</a>     <a href="#dom-networkservices-onserviceavailable">onserviceavailable</a>;
   620            attribute <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/webappapis.html#eventhandler"
   621      class="externalDFN">EventHandler</a>     <a href=
   622      "#dom-networkservices-onserviceunavailable">onserviceunavailable</a>;
   623 
   624 };
   625 
   626 <a href="#networkservices">NetworkServices</a> implements <a href=
   627 "http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#interface-eventtarget"
   628      class="externalDFN">EventTarget</a>;
   629 </pre>
   630       <section>
   631         <h2>
   632           Attributes
   633         </h2>
   634         <dl class="domintro">
   635           <dt>
   636             <code title="dom-networkservices-length"><a href="#dom-networkservices-length">length</a></code>
   637           </dt>
   638           <dd>
   639             <p>
   640               Returns the current number of items in the current object's collection of <a href=
   641               "#networkservice"><code>NetworkService</code></a> objects.
   642             </p>
   643           </dd>
   644           <dt>
   645             <code title="dom-networkservices-servicesavailable"><a href=
   646             "#dom-networkservices-servicesavailable">servicesAvailable</a></code>
   647           </dt>
   648           <dd>
   649             <p>
   650               Returns the current number of items matching one of the app-requested <a>valid service type</a> tokens in
   651               the <a>list of available service records</a>.
   652             </p>
   653           </dd>
   654         </dl>
   655         <div>
   656           <p>
   657             The <dfn id="dom-networkservices-length"><code>length</code></dfn> attribute MUST return the number of
   658             <a href="#networkservice"><code>NetworkService</code></a> objects represented by the collection.
   659           </p>
   660           <p>
   661             The <dfn id="dom-networkservices-servicesavailable"><code>servicesAvailable</code></dfn> attribute MUST
   662             return the number of services in the <a>list of available service records</a> whose <code>type</code>
   663             attribute matches any of the <a>valid service type</a> tokens that was initially used to create the current
   664             <a href="#networkservices"><code>NetworkServices</code></a> object.
   665           </p>
   666         </div>
   667       </section>
   668       <section>
   669         <h2>
   670           Methods
   671         </h2>
   672         <dl class="domintro">
   673           <dt>
   674             <code title="networkservices-getter"><a href="#networkservices">services</a></code> [ <var title=
   675             "">index</var> ]
   676           </dt>
   677           <dd>
   678             <p>
   679               Returns the specified <a href="#networkservice"><code>NetworkService</code></a> object.
   680             </p>
   681           </dd>
   682           <dt>
   683             <code title="networkservices-getter"><a href="#networkservices">services</a></code> . <code title=
   684             "dom-networkservices-getservicebyid"><a href=
   685             "#dom-networkservices-getservicebyid">getServiceById</a></code> ( <var title="">id</var> )
   686           </dt>
   687           <dd>
   688             <p>
   689               Returns the <a href="#networkservice"><code>NetworkService</code></a> object with the given identifier,
   690               or null if no service has that identifier.
   691             </p>
   692           </dd>
   693         </dl>
   694         <p>
   695           A <a href="#networkservices"><code>NetworkServices</code></a> object represents the current collection of
   696           zero or more <a href="#networkservice"><code>NetworkService</code></a> objects - its <a>indexed
   697           properties</a>. A <a href="#networkservices"><code>NetworkServices</code></a> object is
   698           <span>immutable</span> meaning that <a>indexed properties</a> cannot be added and <a>indexed properties</a>
   699           cannot be removed for the lifetime of a <a href="#networkservices"><code>NetworkServices</code></a> object.
   700         </p>
   701         <p class="note">
   702           Each service in a <a href="#networkservices"><code>NetworkServices</code></a> object thus has an index; the
   703           first has the index 0, and each subsequent service is numbered one higher than the previous one.
   704         </p>
   705         <p>
   706           The <a href=
   707           "http://www.whatwg.org/specs/web-apps/current-work/multipage/infrastructure.html#supported-property-indices"
   708              class="externalDFN">supported property indices</a> of <a href=
   709              "#networkservices"><code>NetworkServices</code></a> objects at any instant are the numbers from zero to
   710              the number of the <a href="#networkservice"><code>NetworkService</code></a> objects in the collection
   711              minus one.
   712         </p>
   713         <p>
   714           To <a href=
   715           "http://www.whatwg.org/specs/web-apps/current-work/multipage/infrastructure.html#determine-the-value-of-an-indexed-property"
   716              class="externalDFN">determine the value of an indexed property</a> for a given index <var>index</var> in a
   717              <a href="#networkservices"><code>NetworkServices</code></a> object the user agent MUST return the <a href=
   718              "#networkservice"><code>NetworkService</code></a> object that represents the <var>index</var>th item in
   719              the collection.
   720         </p>
   721         <p>
   722           The <dfn id="dom-networkservices-getservicebyid"><code>getServiceById(id)</code></dfn> method <em class=
   723           "ct">MUST</em> return the first <a href="#networkservice"><code>NetworkService</code></a> object in the
   724           collection whose <a href="#dom-networkservice-id"><code>id</code></a> attribute is equal to the value of the
   725           <var>id</var> argument provided. When no <a href="#networkservice"><code>NetworkService</code></a> objects
   726           match the given argument, the method MUST return null.
   727         </p>
   728         <p>
   729           Services available within the local network can connect and disconnect at different times during the
   730           execution of a web page. A <a>user agent</a> can inform a web page when the state of networked services
   731           matching the requested <a>valid service type</a> change. Web pages can use this information to enable in-page
   732           experiences for communicating the state of networked services with the ability to change the particular
   733           service or set of services the page is connected to by re-invoking the <a href=
   734           "#dom-navigator-getnetworkservices"><code>getNetworkServices()</code></a> method.
   735         </p>
   736       </section>
   737       <section>
   738         <h2>
   739           Events
   740         </h2>
   741         <p>
   742           The following are the event handlers (and their corresponding event handler event types) that <em class=
   743           "ct">MUST</em> be supported, as IDL attributes, by all objects implementing the <a href=
   744           "#networkservices"><code>NetworkServices</code></a> interface:
   745         </p>
   746         <table border="1">
   747           <thead>
   748             <tr>
   749               <th>
   750                 <span title="event handlers">Event handler</span>
   751               </th>
   752               <th>
   753                 <span>Event handler event type</span>
   754               </th>
   755             </tr>
   756           </thead>
   757           <tbody>
   758             <tr>
   759               <td>
   760                 <dfn id="dom-networkservices-onserviceavailable"
   761                     title="dom-NetworkServices-onserviceavailable"><code>onserviceavailable</code></dfn>
   762               </td>
   763               <td>
   764                 <a href="#event-serviceavailable"><code>serviceavailable</code></a>
   765               </td>
   766             </tr>
   767             <tr>
   768               <td>
   769                 <dfn id="dom-networkservices-onserviceunavailable"
   770                     title="dom-NetworkServices-onserviceunavailable"><code>onserviceunavailable</code></dfn>
   771               </td>
   772               <td>
   773                 <a href="#event-serviceunavailable"><code>serviceunavailable</code></a>
   774               </td>
   775             </tr>
   776           </tbody>
   777         </table>
   778       </section>
   779     </section>
   780     <section>
   781       <h2>
   782         Communicating with a networked service
   783       </h2>
   784       <p>
   785         The <a href="#networkservice"><code>NetworkService</code></a> interface is used to provide a set of connection
   786         information for an HTTP service endpoint and if available, service events, running on a networked device.
   787       </p>
   788       <pre class="widl">
   789 [NoInterfaceObject]
   790 interface <dfn id="networkservice">NetworkService</dfn> {
   791   readonly attribute DOMString        <a href="#dom-networkservice-id">id</a>;
   792   readonly attribute DOMString        <a href="#dom-networkservice-name">name</a>;
   793   readonly attribute DOMString        <a href="#dom-networkservice-type">type</a>;
   794   readonly attribute DOMString        <a href="#dom-networkservice-url">url</a>;
   795   readonly attribute DOMString        <a href="#dom-networkservice-config">config</a>;
   796 
   797   readonly attribute boolean          <a href="#dom-networkservice-online">online</a>;
   798 
   799   // event handler attributes
   800            attribute <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/webappapis.html#eventhandler"
   801      class="externalDFN">EventHandler</a>     <a href="#dom-networkservice-onserviceonline">onserviceonline</a>;
   802            attribute <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/webappapis.html#eventhandler"
   803      class="externalDFN">EventHandler</a>     <a href="#dom-networkservice-onserviceoffline">onserviceoffline</a>;
   804 
   805            attribute <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/webappapis.html#eventhandler"
   806      class="externalDFN">EventHandler</a>     <a href="#dom-networkservice-onnotify">onnotify</a>;
   807 };
   808 
   809 <a href="#networkservice">NetworkService</a> implements <a href=
   810 "http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#interface-eventtarget"
   811      class="externalDFN">EventTarget</a>;
   812 </pre>
   813       <section>
   814         <h2>
   815           Attributes
   816         </h2>
   817         <dl class="domintro">
   818           <dt>
   819             <var title="">service</var> . <code title="dom-networkservice-id"><a href=
   820             "#dom-networkservice-id">id</a></code>
   821           </dt>
   822           <dd>
   823             <p>
   824               A unique identifier for the given user-selected service instance.
   825             </p>
   826           </dd>
   827           <dt>
   828             <var title="">service</var> . <code title="dom-networkservice-name"><a href=
   829             "#dom-networkservice-name">name</a></code>
   830           </dt>
   831           <dd>
   832             <p>
   833               The name of the user-selected service.
   834             </p>
   835           </dd>
   836           <dt>
   837             <var title="">service</var> . <code title="dom-networkservice-type"><a href=
   838             "#dom-networkservice-type">type</a></code>
   839           </dt>
   840           <dd>
   841             <p>
   842               The <a>valid service type</a> token value of the user-selected service.
   843             </p>
   844           </dd>
   845           <dt>
   846             <var title="">service</var> . <code title="dom-networkservice-url"><a href=
   847             "#dom-networkservice-url">url</a></code>
   848           </dt>
   849           <dd>
   850             <p>
   851               The control URL endpoint (including any required port information) of the user-selected control service
   852               that has been added to the <a>entry script origin's URL whitelist</a>.
   853             </p>
   854           </dd>
   855           <dt>
   856             <var title="">service</var> . <code title="dom-networkservice-config"><a href=
   857             "#dom-networkservice-config">config</a></code>
   858           </dt>
   859           <dd>
   860             <p>
   861               The configuration information associated with the service depending on the requested service type.
   862             </p>
   863           </dd>
   864         </dl>
   865         <p>
   866           The <dfn id="dom-networkservice-id"><code>id</code></dfn> attribute is a unique identifier for the service.
   867           The same service provided at different times or on different objects MUST have the same <a href=
   868           "#dom-networkservice-id"><code>id</code></a> value.
   869         </p>
   870         <p>
   871           The <dfn id="dom-networkservice-name"><code>name</code></dfn> attribute represents a human-readable title for
   872           the service.
   873         </p>
   874         <p>
   875           The <dfn id="dom-networkservice-type"><code>type</code></dfn> attribute reflects the value of the <a>valid
   876           service type</a> of the service.
   877         </p>
   878         <p>
   879           The <dfn id="dom-networkservice-url"><code>url</code></dfn> attribute is an <a href=
   880           "http://www.w3.org/TR/html5/urls.html#absolute-url"
   881              class="externalDFN">absolute URL</a> pointing to the root HTTP endpoint for the service that has been
   882              added to the <a>entry script origin's URL whitelist</a>. Web pages can subsequently use this value for
   883              implicit cross-document messaging via various existing mechanisms (e.g. Web Sockets, Server-Sent Events,
   884              Web Messaging, XMLHttpRequest).
   885         </p>
   886         <p>
   887           The <dfn id="dom-networkservice-config"><code>config</code></dfn> attribute provides the raw configuration
   888           information extracted from the given network service.
   889         </p>
   890       </section>
   891       <section>
   892         <h3>
   893           States
   894         </h3>
   895         <dl class="domintro">
   896           <dt>
   897             <var title="">service</var> . <code title="dom-networkservice-online"><a href=
   898             "#dom-networkservice-online">online</a></code>
   899           </dt>
   900           <dd>
   901             <p>
   902               Returns <code>true</code> if the service is reporting that it is accessible on the local network or
   903               <code>false</code> if the service is reporting that it is no longer accessible (temporarily or
   904               permanently) on the local network.
   905             </p>
   906           </dd>
   907         </dl>
   908         <p>
   909           The <dfn id="dom-networkservice-online"><code>online</code></dfn> attribute indicates whether the service is
   910           reporting itself as being either <var>online</var>, and therefore accessible on the local network, in which
   911           case this attribute will return <code>true</code> or, <var>offline</var>, and therefore not accessible on the
   912           local network, either temporarily or permanently, in which case this attribute will return
   913           <code>false</code>. This attribute MUST default to <code>true</code>.
   914         </p>
   915       </section>
   916       <section>
   917         <h3>
   918           Events
   919         </h3>
   920         <p>
   921           The following are the event handlers (and their corresponding event handler event types) that <em class=
   922           "ct">MUST</em> be supported, as IDL attributes, by all objects implementing the <a href=
   923           "#networkservice"><code>NetworkService</code></a> interface:
   924         </p>
   925         <table border="1">
   926           <thead>
   927             <tr>
   928               <th>
   929                 <span title="event handlers">Event handler</span>
   930               </th>
   931               <th>
   932                 <span>Event handler event type</span>
   933               </th>
   934             </tr>
   935           </thead>
   936           <tbody>
   937             <tr>
   938               <td>
   939                 <dfn id="dom-networkservice-onnotify"
   940                     title="dom-NetworkService-onnotify"><code>onnotify</code></dfn>
   941               </td>
   942               <td>
   943                 <a href="#event-notify"><code>notify</code></a>
   944               </td>
   945             </tr>
   946             <tr>
   947               <td>
   948                 <dfn id="dom-networkservice-onserviceonline"
   949                     title="dom-NetworkService-onserviceonline"><code>onserviceonline</code></dfn>
   950               </td>
   951               <td>
   952                 <a href="#event-serviceonline"><code>serviceonline</code></a>
   953               </td>
   954             </tr>
   955             <tr>
   956               <td>
   957                 <dfn id="dom-networkservice-onserviceoffline"
   958                     title="dom-NetworkService-onserviceoffline"><code>onserviceoffline</code></dfn>
   959               </td>
   960               <td>
   961                 <a href="#event-serviceoffline"><code>serviceoffline</code></a>
   962               </td>
   963             </tr>
   964           </tbody>
   965         </table>
   966       </section>
   967     </section>
   968     <section>
   969       <h2>
   970         Service Discovery
   971       </h2>
   972       <p>
   973         A <a>user agent</a> conforming to this specification MAY implement <abbr title=
   974         "Simple Service Discovery Protocol">SSDP</abbr> [[!UPNP-DEVICEARCH11]], Zeroconf [[!DNS-SD]] + [[!MDNS]] or
   975         <abbr title="Discovery and Launch Protocol">DIAL</abbr> [<a href=
   976         "https://sites.google.com/a/dial-multiscreen.org/dial/dial-protocol-specification">DIAL</a>] <dfn>service
   977         discovery mechanisms</dfn> - the requirements detailed in this section of the specification - to enable Web
   978         pages to request and connect with HTTP services running on networked devices, discovered via either mechanism,
   979         through this API. When a <a>user agent</a> implements either of these <a>service discovery mechanisms</a>, then
   980         it MUST conform to the corresponding algorithms provided in this section of the specification.
   981       </p>
   982       <p>
   983         This section presents how the results of these two <a>service discovery mechanisms</a> will be matched to
   984         requested service types, how the user agent stores available and active services and how their properties are
   985         applied to any resulting <a href="#networkservice"><code>NetworkService</code></a> objects.
   986       </p>
   987       <p>
   988         It is expected that user agents will perform these <a>service discovery mechanisms</a> asynchronously and
   989         periodically update the <a>list of available service records</a> as required. The timing of any <a>service
   990         discovery mechanisms</a> is an implementation detail left to the discretion of the implementer (e.g. by
   991         continuously monitoring the network as a background process or on invocation of this API from a Web page).
   992       </p>
   993       <p>
   994         The <dfn>list of available service records</dfn> is a single dynamic internal lookup table within user agents
   995         that is used to track all the services that have been discovered and are available in the current network at
   996         any given time. At any point during the running of either of the two <a>service discovery mechanisms</a> then
   997         existing entries within this table can be updated, entries can be added and entries can be removed as the
   998         status of networked services changes according to the rules defined in this specification.
   999       </p>
  1000       <p>
  1001         The <dfn>list of active service managers</dfn> is an internal list within user agents that is used to track all
  1002         <a href="#networkservices"><code>NetworkServices</code></a> objects currently being shared with any web pages
  1003         at the current time within the user agent. Each <a href="#networkservices"><code>NetworkServices</code></a>
  1004         object in the <a>list of active service managers</a> represents a collection of zero or more <a href=
  1005         "#networkservice"><code>NetworkService</code></a> objects - known as its <dfn>indexed properties</dfn>.
  1006         <a href="#networkservice"><code>NetworkService</code></a> objects are attached as the <a>indexed properties</a>
  1007         of a <a href="#networkservices"><code>NetworkServices</code></a> object as part of the <a href=
  1008         "#dom-navigator-getnetworkservices"><code>getNetworkServices()</code></a> algorithm.
  1009       </p>
  1010       <p>
  1011         The rule for <dfn>adding an available service</dfn> is the process of adding a new service or updating an
  1012         existing service in the <a>list of available service records</a> that is generally available on the user's
  1013         current network. This rule takes one argument, <var>network service record</var>, and consists of running the
  1014         following steps:
  1015       </p>
  1016       <ol class="rule">
  1017         <li>Let <var>new service registration flag</var> be <code>true</code>.
  1018         </li>
  1019         <li>For each <var>existing service record</var> in the current <a>list of available service records</a>, run
  1020         the following sub-steps:
  1021           <ol class="rule">
  1022             <li>If the <var>existing service record</var>'s <code>id</code> property does not equal <var>network
  1023             service record</var>'s <code>id</code> property then abort any remaining sub-steps and continue at the next
  1024             available <var>existing service record</var>.
  1025             </li>
  1026             <li>Set <var>new service registration flag</var> to <code>false</code>.
  1027             </li>
  1028             <li>Replace the value of <var>existing service record</var> in the current <a>list of available service
  1029             records</a> with the value of <var>network service record</var>.
  1030             </li>
  1031           </ol>
  1032         </li>
  1033         <li>If <var>new service registration flag</var> is set to <code>true</code> then add <var>network service
  1034         record</var> to the <a>list of available service records</a> as a new item.
  1035         </li>
  1036         <li>For each <var>service manager</var> in the <a>list of active service managers</a> run the following steps:
  1037           <ol class="rule">
  1038             <li>Let <var>service type in current service manager flag</var> be <code>false</code>.
  1039             </li>
  1040             <li>For each <var>active service</var> in <var>service manager</var> run the following steps:
  1041               <ol class="rule">
  1042                 <li>If <var>network service record</var>'s <code>type</code> property does not equal <var>active
  1043                 service</var>'s <code>type</code> attribute then abort any remaining sub-steps for this <var>active
  1044                 service</var> and continue at the next available <var>active service</var>.
  1045                 </li>
  1046                 <li>Set the <var>service type in current service manager flag</var> to <code>true</code>.
  1047                 </li>
  1048                 <li>If the <var>new service registration flag</var> is set to <code>false</code>, the <var>network
  1049                 service record</var>'s <code>id</code> property equals the <var>active service</var>'s <code>id</code>
  1050                 attribute and <var>active service</var>'s <a href="#dom-networkservice-online"><code>online</code></a>
  1051                 attribute is currently set to <code>false</code> then set <var>active service</var>'s <a href=
  1052                 "#dom-networkservice-online"><code>online</code></a> attribute to <code>true</code> and then <a href=
  1053                 "http://www.whatwg.org/specs/web-apps/current-work/complete/webappapis.html#queue-a-task"
  1054                       class="externalDFN">queue a task</a> to dispatch a newly created event with the name <a href=
  1055                       "#event-serviceonline"><code>serviceonline</code></a> that uses the <a href=
  1056                       "http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#event"
  1057                       class="externalDFN"><code>Event</code></a> interface, which does not bubble, is not cancellable,
  1058                       and has no default action, at the current <var>active service</var> object.
  1059                 </li>
  1060               </ol>
  1061             </li>
  1062             <li>If the <var>new service registration flag</var> is set to <code>true</code> and the <var>service type
  1063             in current service manager flag</var> is also set to <code>true</code> then increment <var>service
  1064             manager</var>'s <a href="#dom-networkservices-servicesavailable"><code>servicesAvailable</code></a>
  1065             attribute by <code>1</code> and then <a href=
  1066             "http://www.whatwg.org/specs/web-apps/current-work/complete/webappapis.html#queue-a-task"
  1067                   class="externalDFN">queue a task</a> to dispatch a newly created event with the name <a href=
  1068                   "#event-serviceavailable"><code>serviceavailable</code></a> that uses the <a href=
  1069                   "http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#event"
  1070                   class="externalDFN"><code>Event</code></a> interface, which does not bubble, is not cancellable, and
  1071                   has no default action, at the current <var>service manager</var> object.
  1072             </li>
  1073           </ol>
  1074         </li>
  1075       </ol>
  1076       <p>
  1077         The rule for <dfn>removing an available service</dfn> is the general process of removing a service from the
  1078         <a>list of available service records</a> that has left the user's current network or has otherwise expired.
  1079         This rule takes one argument, <var>service identifier</var>, and consists of running the following steps:
  1080       </p>
  1081       <ol class="rule">
  1082         <li>For each <var>existing service record</var> in the current <a>list of available service records</a>, run
  1083         the following sub-steps:
  1084           <ol class="rule">
  1085             <li>If the <var>existing service record</var>'s <code>id</code> property does not match <var>service
  1086             identifier</var> then skip any remaining sub-steps for the current <var>existing service record</var> and
  1087             continue at the next available <var>existing service record</var>.
  1088             </li>
  1089             <li>If the <var>existing service record</var>'s <code>type</code> property begins with the DOMString
  1090             "<code>upnp:</code>" and <var>existing service record</var>'s <code>eventsURL</code> property is set then
  1091             run the rule to <a>terminate an existing UPnP Events Subscription</a>, if one is currently active (as a
  1092             result of having previously called <a>setup a UPnP Events Subscription</a> against the current
  1093             <var>existing service record</var>).
  1094             </li>
  1095             <li>For each <var>service manager</var> in the <a>list of active service managers</a> run the following
  1096             steps:
  1097               <ol class="rule">
  1098                 <li>Let <var>service type in current service manager flag</var> be <code>false</code>.
  1099                 </li>
  1100                 <li>For each <var>active service</var> in <var>service manager</var> run the following steps:
  1101                   <ol class="rule">
  1102                     <li>If <var>existing service record</var>'s <code>type</code> property does not equal the
  1103                     <var>active service</var>'s <code>type</code> attribute then abort any remaining sub-steps for this
  1104                     <var>active service</var> and continue at the next available <var>active service</var>.
  1105                     </li>
  1106                     <li>Set the <var>service type in current service manager flag</var> to <code>true</code>.
  1107                     </li>
  1108                     <li>If <var>existing service record</var>'s <code>id</code> property equals the <var>active
  1109                     service</var>'s <code>id</code> attribute and <var>active service</var>'s <a href=
  1110                     "#dom-networkservice-online"><code>online</code></a> attribute is currently set to
  1111                     <code>true</code> then set <var>active service</var>'s <a href="#dom-networkservice-online"><code>
  1112                       online</code></a> attribute to <code>false</code> and then <a href=
  1113                       "http://www.whatwg.org/specs/web-apps/current-work/complete/webappapis.html#queue-a-task"
  1114                           class="externalDFN">queue a task</a> to dispatch a newly created event with the name <a href=
  1115                           "#event-serviceoffline"><code>serviceoffline</code></a> that uses the <a href=
  1116                           "http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#event"
  1117                           class="externalDFN"><code>Event</code></a> interface, which does not bubble, is not
  1118                           cancellable, and has no default action, at the current <var>active service</var>.
  1119                     </li>
  1120                   </ol>
  1121                 </li>
  1122                 <li>If the <var>service type in current service manager flag</var> is set to <code>true</code> then
  1123                 decrement <var>service manager</var>'s <a href=
  1124                 "#dom-networkservices-servicesavailable"><code>servicesAvailable</code></a> attribute by <code>1</code>
  1125                 and then <a href=
  1126                 "http://www.whatwg.org/specs/web-apps/current-work/complete/webappapis.html#queue-a-task"
  1127                       class="externalDFN">queue a task</a> to dispatch a newly created event with the name <a href=
  1128                       "#event-serviceunavailable"><code>serviceunavailable</code></a> that uses the <a href=
  1129                       "http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#event"
  1130                       class="externalDFN"><code>Event</code></a> interface, which does not bubble, is not cancellable,
  1131                       and has no default action, at the current <var>service manager</var> object.
  1132                 </li>
  1133               </ol>
  1134             </li>
  1135             <li>Remove <var>existing service record</var> from the current <a>list of available service records</a>.
  1136             </li>
  1137           </ol>
  1138         </li>
  1139       </ol>
  1140       <p>
  1141         User agents SHOULD expire a service record from the <a>list of available service records</a> when its
  1142         <code>expiryTimestamp</code> attribute exceeds the current UTC timestamp. When this condition is met the
  1143         <a>user agent</a> SHOULD run the rule for <a>removing an available service</a>, passing in the expired service
  1144         record's <code>id</code> attribute as the only argument.
  1145       </p>
  1146       <section>
  1147         <h4>
  1148           Zeroconf (<abbr title="Multicast DNS">mDNS</abbr> + <abbr title="Domain Name System">DNS</abbr>-<abbr title=
  1149           "Service Discovery">SD</abbr>)
  1150         </h4>
  1151         <p>
  1152           For each DNS response received from a user-agent-initiated Multicast DNS Browse for <abbr title=
  1153           "DNS Pointer Record">PTR</abbr> records with the name <code>_services._dns-sd._udp</code> on the resolved
  1154           recommended automatic browsing domain [[!MDNS]], the <a>user agent</a> MUST run the following steps:
  1155         </p>
  1156         <ol class="rule">
  1157           <li>Let <var>service mDNS responses</var> be an array of PTR records received by issuing a Multicast DNS
  1158           Browse for PTR records with the name of the current discovered service type.
  1159           </li>
  1160           <li>For each Object <var>service mDNS response</var> in <var>service mDNS responses</var>, run the following
  1161           steps:
  1162             <ol>
  1163               <li>Let <var>network service record</var> be an Object consisting of the following empty properties:
  1164               <code>id</code>, <code>name</code>, <code>type</code>, <code>url</code>, <code>config</code>,
  1165               <code>expiryTimestamp</code>.
  1166               </li>
  1167               <li>Set <var>network service record</var>'s <code>id</code> property to the value of the full PTR Service
  1168               Instance Name [[!MDNS]].
  1169               </li>
  1170               <li>Set <var>network service record</var>'s <code>name</code> property to the value of the PTR Service
  1171               Instance Name's <var>Instance</var> component [[!MDNS]].
  1172               </li>
  1173               <li>Set <var>network service record</var>'s <code>type</code> property to the concatenation of the string
  1174               <code>zeroconf:</code> followed be the value of the PTR Service Instance Name's <var>Service</var>
  1175               component [[!MDNS]].
  1176               </li>
  1177               <li>Set <var>network service record</var>'s <code>url</code> property to the resolvable Service URL
  1178               obtained from performing an DNS-SD Lookup [[!DNS-SD]] of the current service from the PTR record provided
  1179               [[!MDNS]].
  1180               </li>
  1181               <li>Set <var>network service record</var>'s <code>config</code> property to the string value of the
  1182               contents of the first DNS-SD TXT record associated with the <var>service mDNS response</var> as defined
  1183               in [[!DNS-SD]].
  1184               </li>
  1185               <li>Set <var>network service record</var>'s <code>expiryTimestamp</code> property to the value of the
  1186               current date, in UTC timestamp format, plus a value of <code>120</code> seconds.
  1187               </li>
  1188               <li>Run the general rule for <a>adding an available service</a>, passing in the current <var>network
  1189               service record</var> as the only argument.
  1190               </li>
  1191             </ol>
  1192           </li>
  1193         </ol>
  1194       </section>
  1195       <section>
  1196         <h5>
  1197           Simple Service Discovery Protocol (<abbr title="Simple Service Discovery Protocol">SSDP</abbr>)
  1198         </h5>
  1199         <p>
  1200           A user agent that implements UPnP service discovery MUST issue a <dfn>search request for UPnP root
  1201           devices</dfn> against the user's current local network according to the full normative text and timing
  1202           provided in 'Section 1.3.2: Search request with M-SEARCH' detailed in [[!UPNP-DEVICEARCH11]].
  1203         </p>
  1204         <p>
  1205           The user agent MUST issue all <a title="search request for UPnP root devices">search requests for UPnP root
  1206           devices</a> with a HTTP request line equal to <code>M-SEARCH * HTTP/1.1</code>, with a HOST header equal to
  1207           the reserved multicast address and port of <code>239.255.255.250:1900</code>, a MAN header equal to
  1208           <code>ssdp:discover</code>, an ST header equal to <code>upnp:rootdevice</code> and a user-agent defined MX
  1209           header equal to a <dfn>maximum UPnP advertisement response wait time</dfn> value between <code>1</code> and
  1210           <code>5</code> seconds.
  1211         </p>
  1212         <p>
  1213           The user agent MUST listen for any incoming responses to any <a>search request for UPnP root devices</a>.
  1214         </p>
  1215         <p>
  1216           For each <dfn>HTTP Response</dfn> following an initial <a>search request for UPnP root devices</a> sent on a
  1217           <a>standard UPnP address and port</a> the user agent MUST run the following steps:
  1218         </p>
  1219         <ol class="rule">
  1220           <li>If the <a>HTTP Response</a> is not a HTTP 200 OK response then this response is invalid and the user
  1221           agent MUST discard this response, abort any remaining steps and return. The user agent MAY issue a new
  1222           <a>search request for UPnP root devices</a> as a result of this error occurring.
  1223           </li>
  1224           <li>If the <a>maximum UPnP advertisement response wait time</a> has been exceeded since the initial <a>search
  1225           request for UPnP root devices</a> was sent then the <a>HTTP Response</a> is invalid and the user agent MUST
  1226           discard this response, abort any remaining steps and return. The user agent MAY stop listening for responses
  1227           from the current <a>search request for UPnP root devices</a> as a result of this error occurring. Equally,
  1228           the user agent MAY issue a new <a>search request for UPnP root devices</a> as a result of this error
  1229           occurring.
  1230           </li>
  1231           <li>Let <var>ssdp device</var> be an Object with a property for each HTTP header received in the <a>HTTP
  1232           Response</a>, with each key being the name of a HTTP response header and each value being that HTTP response
  1233           header's value.
  1234           </li>
  1235           <li>If <var>ssdp device</var> does not contain at least one <var>CACHE-CONTROL</var> entry, at least one
  1236           <var>USN</var> entry, at least one <var>ST</var> entry and at least one <var>LOCATION</var> entry or the
  1237           value of its <var>ST</var> entry is not <code>upnp:rootdevice</code>, then the <a>HTTP Response</a> is
  1238           invalid and the <a>user agent</a> MUST discard this response, abort any remaining steps and return.
  1239           </li>
  1240           <li>The user agent MUST run the rule for <a>obtaining a UPnP Device Description File</a> passing in the first
  1241           occurrence of <var>LOCATION</var> from <var>ssdp device</var> as the <var>device descriptor URL</var>
  1242           argument and the first occurrence of <var>USN</var> from <var>ssdp device</var> as the <var>device
  1243           identifier</var> argument and the first occurrence of <var>CACHE-CONTROL</var> from <var>ssdp device</var>
  1244           (minus the leading string of <code>max-age=</code>) as the <var>device expiry</var> argument.
  1245           </li>
  1246         </ol>
  1247         <p>
  1248           The user agent MUST listen for incoming requests on the <dfn>standard UPnP address and port</dfn> on all
  1249           current local network interface addresses with the port <code>1900</code>.
  1250         </p>
  1251         <p>
  1252           For each <dfn>HTTP Request</dfn> received on a <a>standard UPnP address and port</a> the user agent MUST run
  1253           the following steps:
  1254         </p>
  1255         <ol class="rule">
  1256           <li>If the <a>HTTP Request</a> is not a HTTP NOTIFY request then it is not a valid UPnP Request and the user
  1257           agent MUST discard this request, abort any remaining steps and return.
  1258           </li>
  1259           <li>Let <var>ssdp device</var> be an Object with a property for each HTTP header received in the <a>HTTP
  1260           Request</a>, with each key being the name of a HTTP header and each value being that HTTP header's value.
  1261           </li>
  1262           <li>If <var>ssdp device</var> does not contain at least one <var>CACHE-CONTROL</var> entry, at least one
  1263           <var>USN</var> entry, at least one <var>NT</var> entry, at least one <var>NTS</var> entry and at least one
  1264           <var>LOCATION</var> entry or the value of its <var>NT</var> entry is not <code>upnp:rootdevice</code>, then
  1265           the <a>HTTP Request</a> is a malformed UPnP Request and the <a>user agent</a> MUST discard this request,
  1266           abort any remaining steps and return.
  1267           </li>
  1268           <li>If <var>ssdp device</var>'s <var>NTS</var> entry is equal to <code>ssdp:alive</code> then the user agent
  1269           MUST run the rule for <a>obtaining a UPnP Device Description File</a> passing in the first occurrence of
  1270           <var>LOCATION</var> from <var>ssdp device</var> as the <var>device descriptor URL</var> argument and the
  1271           first occurrence of <var>USN</var> from <var>ssdp device</var> as the <var>device identifier</var> argument
  1272           and the first occurrence of <var>CACHE-CONTROL</var> from <var>ssdp device</var> (minus the leading string of
  1273           <code>max-age=</code>) as the <var>device expiry</var>.<br>
  1274             <br>
  1275             Otherwise, if <var>ssdp device</var>'s <var>NTS</var> entry is equal to <code>ssdp:byebye</code> then the
  1276             user agent MUST run the rule for <a>removing all services from a registered UPnP Device</a> passing in the
  1277             first occurrence of <var>USN</var> from <var>ssdp device</var> as the <var>device identifier</var>
  1278             argument.
  1279           </li>
  1280         </ol>
  1281         <p>
  1282           The rule for <dfn>obtaining a UPnP Device Description File</dfn> is the process of obtaining the contents of
  1283           a standard UPnP Device Description [[!UPNP-DEVICEARCH11]] from a URL-based resource. This rule takes three
  1284           arguments - <var>device descriptor URL</var>, <var>device identifier</var> and <var>device expiry</var> - and
  1285           when called the user agent MUST run the following steps:
  1286         </p>
  1287         <ol class="rule">
  1288           <li>Let <var>device descriptor file</var> contain the contents of the file located at the URL provided in
  1289           <var>device descriptor URL</var> obtained according to the rules defined in 'Section 2.11: Retrieving a
  1290           description using HTTP' in [[!UPNP-DEVICEARCH11]].
  1291           </li>
  1292           <li>If the value provided in <var>device descriptor URL</var> cannot be resolved as a reachable URL on the
  1293           current network or the <var>device descriptor file</var> remains empty then it is invalid and the <a>user
  1294           agent</a> MUST abort any remaining steps and return.
  1295           </li>
  1296           <li>Run the rule for <a>processing a UPnP Device Description File</a>, passing in the current <var>device
  1297           descriptor file</var>, <var>device identifier</var> and <var>device expiry</var> arguments.
  1298           </li>
  1299         </ol>
  1300         <p>
  1301           The rule for <dfn>processing a UPnP Device Description File</dfn> is the process of parsing the contents of a
  1302           standard UPnP Device Description [[!UPNP-DEVICEARCH11]] and registering the UPnP services contained therein
  1303           within the <a>list of available service records</a>.
  1304         </p>
  1305         <p>
  1306           The rule for <a>processing a UPnP Device Description File</a> takes three arguments - <var>device descriptor
  1307           file</var>, <var>device identifier</var> and <var>device expiry</var> - and when called the user agent MUST
  1308           run the following steps:
  1309         </p>
  1310         <ol class="rule">
  1311           <li>Let <var>advertised services</var> be a list of all advertised services obtained from the <var>device
  1312           descriptor file</var> containing the value of the first occurrence of the <code>&lt;serviceList&gt;</code>
  1313           element as it is defined in 'Section 2.3: Device Description' in [[!UPNP-DEVICEARCH11]].
  1314           </li>
  1315           <li>For each <code>&lt;service&gt;</code> element - known as an <var>advertised service</var> - in
  1316           <var>advertised services</var> run the following steps:
  1317             <ol class="rule">
  1318               <li>Let <var>network service record</var> be a new Object consisting of the following empty properties:
  1319               <code>id</code>, <code>deviceId</code>, <code>name</code>, <code>type</code>, <code>url</code>,
  1320               <code>eventsUrl</code>, <code>config</code>, <code>expiryTimestamp</code>.
  1321               </li>
  1322               <li>Set <var>network service record</var>'s <code>id</code> property to the concatenated string value of
  1323               the first occurrence of the <code>&lt;UDN&gt;</code> element in the <var>device descriptor file</var>
  1324               with the <var>advertised service</var>'s <code>&lt;serviceId&gt;</code> sub-element.
  1325               </li>
  1326               <li>Set <var>network service record</var>'s <code>deviceId</code> property to the value of <var>device
  1327               identifier</var>.
  1328               </li>
  1329               <li>Set <var>network service record</var>'s <code>name</code> property to the string value of the first
  1330               occurrence of the <var>advertised service</var>'s <code>&lt;serviceId&gt;</code> sub-element.
  1331               </li>
  1332               <li>Set <var>network service record</var>'s <code>type</code> property to the concatenation of the string
  1333               <code>upnp:</code> followed by the string value of the first occurrence of the <var>advertised
  1334               service</var>'s <code>&lt;serviceType&gt;</code> sub-element.
  1335               </li>
  1336               <li>Set <var>network service record</var>'s <code>url</code> property to the string value of the first
  1337               occurrence of the <var>advertised service</var>'s <code>&lt;controlURL&gt;</code> sub-element.
  1338               </li>
  1339               <li>Set <var>network service record</var>'s <code>config</code> property to the string value of the
  1340               contents of the first occurrence of the <code>&lt;device&gt;</code> element in the <var>device descriptor
  1341               file</var>.
  1342               </li>
  1343               <li>If <var>advertised service</var>'s <code>&lt;eventSubURL&gt;</code> sub-element is not empty, then
  1344               set <var>network service record</var>'s <code>eventsUrl</code> property to the string value of the first
  1345               occurrence of the <var>advertised service</var>'s <code>&lt;eventSubURL&gt;</code> sub-element.
  1346               Otherwise, do not set <var>network service record</var>'s <code>eventsUrl</code> property.
  1347               </li>
  1348               <li>Set <var>network service record</var>'s <code>expiryTimestamp</code> property to the value of the
  1349               current date, in UTC timestamp format, plus the value of <var>device expiry</var>.
  1350               </li>
  1351               <li>Run the general rule for <a>adding an available service</a>, passing in the current <var>network
  1352               service record</var> as the only argument.
  1353               </li>
  1354             </ol>
  1355           </li>
  1356           <li>If <var>device descriptor file</var> contains a <code>&lt;deviceList&gt;</code> element then for each
  1357           <code>&lt;device&gt;</code> element within <code>&lt;deviceList&gt;</code> - herein known as an <var>embedded
  1358           device descriptor file</var> - the user agent MUST run the rule for <a>processing a UPnP Device Description
  1359           File</a>, passing in the current <var>embedded device descriptor file</var> as the <var>device descriptor
  1360           file</var> argument, along with the current <var>device identifier</var> and <var>device expiry</var>
  1361           arguments.
  1362           </li>
  1363         </ol>
  1364         <p>
  1365           The rule for <dfn>removing all services from a registered UPnP Device</dfn> is the process of removing all
  1366           services associated with a device from the <a>list of available service records</a> that has left the user's
  1367           current network or has otherwise timed out or expired. This rule takes one argument, <var>device
  1368           identifier</var>, and consists of running the following steps:
  1369         </p>
  1370         <ol class="rule">
  1371           <li>For each <var>existing service record</var> in the current <a>list of available service records</a>, run
  1372           the following sub-steps:
  1373             <ol class="rule">
  1374               <li>If the <var>existing service record</var>'s <code>deviceId</code> property does not match <var>device
  1375               identifier</var> then skip any remaining sub-steps for the current <var>existing service record</var> and
  1376               continue at the next available <var>existing service record</var>.
  1377               </li>
  1378               <li>Run the general rule for <a>removing an available service</a> passing in <var>existing service
  1379               record</var>'s <code>id</code> property as the only argument.
  1380               </li>
  1381             </ol>
  1382           </li>
  1383         </ol>
  1384         <p>
  1385           When the <a>user agent</a> is to <dfn>setup a UPnP Events Subscription</dfn>, it is to run the following
  1386           steps with the current <var>network service record</var> object as defined in 'Section 4.1.2: SUBSCRIBE with
  1387           NT and CALLBACK' in [[!UPNP-DEVICEARCH11]]:
  1388         </p>
  1389         <ol class="rule">
  1390           <li>If <var>network service record</var>'s <code>eventsUrl</code> property is empty then the <a>user
  1391           agent</a> MUST abort these steps.
  1392           </li>
  1393           <li>Let <var>callback URL</var> be the value of creating a new <a>user-agent generated callback url</a>.
  1394           </li>
  1395           <li>Send a HTTP SUBSCRIBE request with a <em>NT</em> header with a string value of <code>upnp:event</code>, a
  1396           <em>TIMEOUT</em> header with a user-agent defined timeout value (in the form <code>Second-XX</code> where
  1397           <code>XX</code> is the user-agent defined timeout value in seconds) and a <em>CALLBACK</em> header with a
  1398           string value of <var>callback URL</var> towards the <var>network service record</var>'s
  1399           <code>eventsUrl</code> property.
  1400           </li>
  1401           <li>If a non-200 OK response is received from the HTTP SUBSCRIBE request then the <a>user agent</a> MUST
  1402           abort these steps.
  1403           </li>
  1404           <li>On receiving a valid 200 OK response, run the following steps:
  1405             <ol class="rule">
  1406               <li>Let <var>callback ID</var> equal the string value of the first included <em>SID</em> header, if it
  1407               exists.
  1408               </li>
  1409               <li>Let <var>timeout date</var> equal the sum of the current UTC date value plus the integer value of the
  1410               first included <em>TIMEOUT</em> header (minus the leading string of <code>Second-</code>), if it exists.
  1411               </li>
  1412               <li>Run the following steps asynchronously and continue to the step labeled <em>listen</em> below.
  1413               </li>
  1414               <li>
  1415                 <em>Refresh Subscription</em>: Run the following steps at a set interval (X) within the <a>user
  1416                 agent</a>:
  1417                 <ol class="rule">
  1418                   <li>Let <var>current date</var> equal the current UTC date.
  1419                   </li>
  1420                   <li>If <var>current date</var> is less than the <var>timeout date</var> then continue to the step
  1421                   labeled <em>refresh subscription</em> above.
  1422                   </li>
  1423                   <li>Send a HTTP SUBSCRIBE request with a <em>SID</em> header with the string value of <var>callback
  1424                   ID</var> and a user-agent defined <em>TIMEOUT</em> header (in the form <code>Second-XX</code> where
  1425                   <code>XX</code> is the user-agent defined timeout value in seconds) towards the <var>network service
  1426                   record</var>'s <code>eventsUrl</code> property.
  1427                   </li>
  1428                   <li>On receiving a valid 200 OK, update <var>callback ID</var> with the string value of the first
  1429                   included <em>SID</em> header and set <var>timeout date</var> to the sum of the current UTC date value
  1430                   plus the integer value of the first included <em>TIMEOUT</em> header (minus the leading string of
  1431                   <code>Second-</code>), if it exists. If the current date is greater than or equal to <var>timeout
  1432                   date</var> then the <a>user agent</a> SHOULD continue from the step labeled <em>refresh
  1433                   subscription</em> above. For all non 200 OK responses the <a>user agent</a> SHOULD continue from the
  1434                   step labeled <em>refresh subscription</em> above.
  1435                   </li>
  1436                 </ol>
  1437               </li>
  1438               <li>
  1439                 <em>Listen</em>: For each HTTP NOTIFY request received at the <var>callback URL</var> the <a>user
  1440                 agent</a> is to run the following steps:
  1441                 <ol class="rule">
  1442                   <li>Let <var>content clone</var> be the result of obtaining the message body of the HTTP NOTIFY
  1443                   request. If <var>content clone</var> is empty, then the <a>user agent</a> MUST abort these steps.
  1444                   </li>
  1445                   <li>Let <var>notification event</var> be a new simple event that uses the <a href=
  1446                   "http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#event"
  1447                         class="externalDFN"><code>Event</code></a> interface with the name <a href=
  1448                         "#event-notify"><code>notify</code></a>, which does not bubble, is not cancellable, and has no
  1449                         default action.
  1450                   </li>
  1451                   <li>Let the <code>data</code> attribute of <var>notification event</var> have the DOMString value of
  1452                   <var>content clone</var>.
  1453                   </li>
  1454                   <li>
  1455                     <a href="http://www.whatwg.org/specs/web-apps/current-work/complete/webappapis.html#queue-a-task"
  1456                         class="externalDFN">Queue a task</a> to dispatch <var>notification event</var> at the current
  1457                         <a><code>NetworkService</code></a> object.
  1458                   </li>
  1459                   <li>Return a HTTP 200 OK response to the sender of the HTTP NOTIFY request.
  1460                   </li>
  1461                 </ol>
  1462               </li>
  1463             </ol>
  1464           </li>
  1465         </ol>
  1466         <p>
  1467           A <a>user agent</a> can <dfn>terminate an existing UPnP Events Subscription</dfn> at any time for a
  1468           <var>network service record</var> by sending an HTTP UNSUBSCRIBE request - as defined in 'Section 4.1.4:
  1469           Cancelling a subscription with UNSUBSCRIBE' in [[!UPNP-DEVICEARCH11]] - with a HOST header set to that
  1470           <var>active service</var>'s <code>eventsUrl</code> property and a SID header set to the <var>callback
  1471           ID</var> obtained when the initial <a>setup a UPnP Events Subscription</a> action occurred.
  1472         </p>
  1473       </section>
  1474       <section>
  1475         <h5>
  1476           Discovery and Launch Protocol (<abbr title="Discovery and Launch Protocol">DIAL</abbr>)
  1477         </h5>
  1478         <p>
  1479           A user agent that implements DIAL service discovery MUST issue a <dfn>search request for DIAL-enabled
  1480           devices</dfn> against the user's current local network according to the full normative text and timing
  1481           provided in 'Section 1.3.2: Search request with M-SEARCH' detailed in [[!UPNP-DEVICEARCH11]].
  1482         </p>
  1483         <p>
  1484           Let <var>dial version</var> be the version number specified in the <a>valid service type</a> token. Let
  1485           <var>dial search target</var> be the concatentation of the
  1486           <code>urn:dial-multiscreen-org:service:dial:</code> string constant with the <var>dial version</var>
  1487           (currently, <var>dial version</var> can only be <code>1</code>)
  1488         </p>
  1489         <p>
  1490           The user agent MUST issue all <a title="search request for DIAL devices">search requests for DIAL devices</a>
  1491           with a HTTP request line equal to <code>M-SEARCH * HTTP/1.1</code>, with a HOST header equal to the reserved
  1492           multicast address and port of <code>239.255.255.250:1900</code>, a MAN header equal to
  1493           <code>ssdp:discover</code>, an ST header equal to <var>dial search target</var> and a user-agent defined MX
  1494           header equal to a <dfn>maximum DIAL advertisement response wait time</dfn> value between <code>1</code> and
  1495           <code>5</code> seconds.
  1496         </p>
  1497         <p>
  1498           The user agent MUST listen for any incoming responses to a <a>search request for DIAL devices</a>.
  1499         </p>
  1500         <p>
  1501           For each HTTP Response following an initial <a>search request for DIAL devices</a> sent on a <a>standard UPnP
  1502           address and port</a> the user agent MUST run the following steps:
  1503         </p>
  1504         <ol class="rule">
  1505           <li>If the HTTP Response is not a HTTP 200 OK response then this response is invalid and the user agent MUST
  1506           discard this response, abort any remaining steps and return. The user agent MAY issue a new <a>search request
  1507           for DIAL devices</a> as a result of this error occurring.
  1508           </li>
  1509           <li>If the <a>maximum DIAL advertisement response wait time</a> has been exceeded since the initial <a>search
  1510           request for DIAL devices</a> was sent then the <a>HTTP Response</a> is invalid and the user agent MUST
  1511           discard this response, abort any remaining steps and return. The user agent MAY stop listening for responses
  1512           from the current <a>search request for DIAL devices</a> as a result of this error occurring. Equally, the
  1513           user agent MAY issue a new <a>search request for DIAL devices</a> as a result of this error occurring.
  1514           </li>
  1515           <li>Let <var>dial device</var> be an Object with a property for each HTTP header received in the <a>HTTP
  1516           Response</a>, with each key being the name of a HTTP response header and each value being that HTTP response
  1517           header's value.
  1518           </li>
  1519           <li>If <var>dial device</var> does not contain at least one <var>CACHE-CONTROL</var> entry, at least one
  1520           <var>USN</var> entry, at least one <var>ST</var> entry and at least one <var>LOCATION</var> entry or the
  1521           value of its <var>ST</var> entry is not <var>dial search target</var>, then the <a>HTTP Response</a> is
  1522           invalid and the <a>user agent</a> MUST discard this response, abort any remaining steps and return.
  1523           </li>
  1524           <li>The user agent MUST run the rule for <a>obtaining a UPnP Device Description File</a> passing in the first
  1525           occurrence of <var>LOCATION</var> from <var>dial device</var> as the <var>device descriptor URL</var>
  1526           argument and the first occurrence of <var>USN</var> from <var>dial device</var> as the <var>device
  1527           identifier</var> argument and the first occurrence of <var>CACHE-CONTROL</var> from <var>dial device</var>
  1528           (minus the leading string of <code>max-age=</code>) as the <var>device expiry</var> argument.
  1529           </li>
  1530         </ol>
  1531         <p>
  1532           The rule for <dfn>obtaining a DIAL Device Description File</dfn> is the process of obtaining the contents of
  1533           a standard UPnP Device Description [[!UPNP-DEVICEARCH11]] from a URL-based resource. This rule takes three
  1534           arguments - <var>device descriptor URL</var>, <var>device identifier</var> and <var>device expiry</var> - and
  1535           when called the user agent MUST run the following steps:
  1536         </p>
  1537         <ol class="rule">
  1538           <li>Let <var>device descriptor file</var> contain the contents of the file located at the URL provided in
  1539           <var>device descriptor URL</var> obtained according to the rules defined in 'Section 2.11: Retrieving a
  1540           description using HTTP' in [[!UPNP-DEVICEARCH11]].
  1541           </li>
  1542           <li>Let <var>application url</var> be the value of the first occurrence of the <code>Application-URL</code>
  1543           response header field obtained according to the rules defined in 'Section 5.4: Device Description Response'
  1544           in [<a href="https://sites.google.com/a/dial-multiscreen.org/dial/dial-protocol-specification">DIAL</a>]
  1545           </li>
  1546           <li>If the value provided in <var>device descriptor URL</var> cannot be resolved as a reachable URL on the
  1547           current network or the <var>device descriptor file</var> remains empty or <var>application url</var> is
  1548           undefined then it is invalid and the <a>user agent</a> MUST abort any remaining steps and return.
  1549           </li>
  1550           <li>Run the following steps to add the newly discovered DIAL service:
  1551             <ol class="rule">
  1552               <li>Let <var>network service record</var> be a new Object consisting of the following empty properties:
  1553               <code>id</code>, <code>deviceId</code>, <code>name</code>, <code>type</code>, <code>url</code>,
  1554               <code>expiryTimestamp</code>.
  1555               </li>
  1556               <li>Set <var>network service record</var>'s <code>id</code> property to the first occurrence of the
  1557               <code>&lt;UDN&gt;</code> element in the <var>descriptor file</var> prefixed with the <code>dial:</code>
  1558               string constant
  1559               </li>
  1560               <li>Set <var>network service record</var>'s <code>deviceId</code> property to the value of <var>device
  1561               identifier</var>.
  1562               </li>
  1563               <li>Set <var>network service record</var>'s <code>name</code> property to the string value of the first
  1564               occurrence of the <code>&lt;friendlyName&gt;</code> element in the <var>descriptor file</var>.
  1565               </li>
  1566               <li>Set <var>network service record</var>'s <code>type</code> property to <var>dial search target</var>.
  1567               </li>
  1568               <li>Set <var>network service record</var>'s <code>url</code> property to the string value of the
  1569               <var>application url</var>.
  1570               </li>
  1571               <li>Set <var>network service record</var>'s <code>expiryTimestamp</code> property to the value of the
  1572               current date, in UTC timestamp format, plus the value of <var>device expiry</var>.
  1573               </li>
  1574               <li>Run the general rule for <a>adding an available service</a>, passing in the current <var>network
  1575               service record</var> as the only argument.
  1576               </li>
  1577             </ol>
  1578           </li>
  1579         </ol>
  1580       </section>
  1581       <section>
  1582         <h3>
  1583           Network Topology Monitoring
  1584         </h3>
  1585         <div>
  1586           <p>
  1587             When the <a>user agent</a> detects that the user has dropped from their connected network then, for each
  1588             <var>existing service record</var> in the <a>list of available service records</a>, the user agent MUST run
  1589             the general rule for <a>removing an available service</a> passing in each <var>existing service
  1590             record</var>'s <code>id</code> property as the only argument for each call.
  1591           </p>
  1592           <p>
  1593             When the <a>user agent</a> detects that the user has connected to a new network or reconnected to an
  1594             existing network, then it SHOULD restart its discovery mechanisms as defined in the <a href=
  1595             "#service-discovery">Service Discovery</a> section of this specification, maintaining the existing <a>list
  1596             of active service managers</a> currently in use.
  1597           </p>
  1598         </div>
  1599       </section>
  1600     </section>
  1601     <section>
  1602       <h3>
  1603         Events Summary
  1604       </h3>
  1605       <p>
  1606         The following events are dispatched on the <a href="#networkservices"><code>NetworkServices</code></a> and/or
  1607         <a href="#networkservice"><code>NetworkService</code></a> objects:
  1608       </p>
  1609       <table border="1">
  1610         <thead>
  1611           <tr>
  1612             <th>
  1613               <span>Event name</span>
  1614             </th>
  1615             <th>
  1616               <span>Interface</span>
  1617             </th>
  1618             <th>
  1619               <span>Dispatched when...</span>
  1620             </th>
  1621           </tr>
  1622         </thead>
  1623         <tbody>
  1624           <tr>
  1625             <td>
  1626               <dfn id="event-serviceavailable"><code>serviceavailable</code></dfn>
  1627             </td>
  1628             <td>
  1629               <a href="http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#event"
  1630                   class="externalDFN"><code>Event</code></a>
  1631             </td>
  1632             <td>
  1633               When a new service that matches one of the <a>requested type tokens</a> is found in the current network.
  1634             </td>
  1635           </tr>
  1636           <tr>
  1637             <td>
  1638               <dfn id="event-serviceunavailable"><code>serviceunavailable</code></dfn>
  1639             </td>
  1640             <td>
  1641               <a href="http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#event"
  1642                   class="externalDFN"><code>Event</code></a>
  1643             </td>
  1644             <td>
  1645               When an existing service that matches one of the <a>requested type tokens</a> gracefully leaves or
  1646               expires from the current network.
  1647             </td>
  1648           </tr>
  1649           <tr>
  1650             <td>
  1651               <dfn id="event-serviceonline"><code>serviceonline</code></dfn>
  1652             </td>
  1653             <td>
  1654               <a href="http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#event"
  1655                   class="externalDFN"><code>Event</code></a>
  1656             </td>
  1657             <td>
  1658               When a current service renews its service registration within the current network.
  1659             </td>
  1660           </tr>
  1661           <tr>
  1662             <td>
  1663               <dfn id="event-serviceoffline"><code>serviceoffline</code></dfn>
  1664             </td>
  1665             <td>
  1666               <a href="http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#event"
  1667                   class="externalDFN"><code>Event</code></a>
  1668             </td>
  1669             <td>
  1670               When a current service gracefully leaves or otherwise expires from the current network.
  1671             </td>
  1672           </tr>
  1673           <tr>
  1674             <td>
  1675               <dfn id="event-notify"><code>notify</code></dfn>
  1676             </td>
  1677             <td>
  1678               <a href="http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#event"
  1679                   class="externalDFN"><code>Event</code></a>
  1680             </td>
  1681             <td>
  1682               When a valid UPnP Events Subscription Message is received on a <a>user-agent generated callback url</a>
  1683               for a current service. This event never fires for Zeroconf-based services.
  1684             </td>
  1685           </tr>
  1686         </tbody>
  1687       </table>
  1688     </section>
  1689     <section>
  1690       <h3>
  1691         Garbage collection
  1692       </h3>
  1693       <p>
  1694         A user agent MUST only garbage collect a <a><code>NetworkServices</code></a> object and remove its entry from
  1695         the <a>list of active service managers</a> when the user has navigated away from the <a href=
  1696         "http://www.whatwg.org/specs/web-apps/current-work/complete/browsers.html#entry-script"
  1697            class="externalDFN">entry script</a>'s <a href=
  1698            "http://www.whatwg.org/specs/web-apps/current-work/complete/origin-0.html#origin"
  1699            class="externalDFN">origin</a> in which the current <a><code>NetworkServices</code></a> object was provided.
  1700       </p>
  1701       <p>
  1702         A user agent MUST NOT garbage collect individual <a><code>NetworkService</code></a> objects until their parent
  1703         <a><code>NetworkServices</code></a> object has been garbage collected.
  1704       </p>
  1705       <p>
  1706         A user agent MUST garbage collect the <a><code>NetworkService</code></a> <a>indexed properties</a> of a
  1707         <a><code>NetworkServices</code></a> object when that <a><code>NetworkServices</code></a> object itself has been
  1708         garbage-collected.
  1709       </p>
  1710     </section>
  1711     <section>
  1712       <h3>
  1713         Use Cases and Requirements
  1714       </h3>
  1715       <p>
  1716         This section covers what the requirements are for this API, as well as illustrates some use cases.
  1717       </p>
  1718       <ul class="rule">
  1719         <li>Once a user has given permission, user agents should provide the ability for Web pages to communicate
  1720         directly with a Local-networked Service.
  1721           <ul class="rule">
  1722             <li>Example: A web-based TV remote control. A Web page wants to control the current user's TV, changing the
  1723             programming shown or increasing/decreasing/muting the volume of the Local-networked Device. The Web page
  1724             requests a service type that is known to be implemented by television sets to which it has the application
  1725             logic to communicate. Local devices providing the request service types are discovered and presented to the
  1726             user for authorization. The user selects one or more of the discovered television sets to be accessible to
  1727             the current Web page and then clicks 'Share'. The Web page can now communicate directly with the
  1728             user-authorized Local-networked services.
  1729             </li>
  1730           </ul>
  1731         </li>
  1732         <li>Web pages should be able to communicate with Local-networked Services using the messaging channel supported
  1733         by those Devices.
  1734           <ul class="rule">
  1735             <li>Example: A Web page advertises that it is capable of controlling multiple Home Media Servers. The user
  1736             can select their Home Media Server type from a drop-down list, at which point the Web page sends a request
  1737             to the user agent to connect with the associated service type of the Home Media Server. The Media Server
  1738             selected implements a Web Socket channel for bi-directional service communication and so the Web page opens
  1739             a web socket to the requested Media Server and can communicate as required via that appropriate channel.
  1740             </li>
  1741           </ul>
  1742         </li>
  1743         <li>Web pages should be able to communicate with Local-networked Services using the messaging format supported
  1744         by those Devices.
  1745           <ul class="rule">
  1746             <li>Example: A Web page advertises that it is capable of interacting with and controlling multiple types of
  1747             Home Media Server. The user can select their Home Media Server type from a drop-down list or known Media
  1748             Servers, at which point the Web page sends a request to the user agent to connect with the associated
  1749             service type (and, optionally, the associated event type) of the Home Media Server. The communication
  1750             protocols supported by Home Media Servers typically vary between UPnP, JSON-RPC, Protocol Buffers or other
  1751             messaging formats depending on the Home Media Server requested. The Web page is able to communicate with
  1752             the user-selected Home Media Server in the messaging format supported by that Device, which, in this
  1753             example is a simple key/value pair text format.
  1754             </li>
  1755           </ul>
  1756         </li>
  1757         <li>Web pages should not be able to communicate with Local-networked Services that have not been authorized by
  1758         the user thereby maintaining the user's privacy.
  1759           <ul class="rule">
  1760             <li>Example: A Web page requests access to one type of Local-networked service. The user authorizes access
  1761             to that particular service. Other services running on that same device, and on other devices within the
  1762             network, should not be accessible to the current Web page.
  1763             </li>
  1764           </ul>
  1765         </li>
  1766         <li>A user should be able to share one or more Local-networked Services based on a particular service type
  1767         request from a Web page.
  1768           <ul class="rule">
  1769             <li>Example: A Web page is capable of interacting with a specific profile of Local-networked Service. As
  1770             such, it makes a request to the user agent to access those services, of which multiple matches are found.
  1771             The user is capable of selecting one or more of the discovered services to share with the Web page. The Web
  1772             page can then implement a drag-and-drop interface for the user to drag specific actions on to one or more
  1773             of the authorized Local-networked Services.
  1774             </li>
  1775           </ul>
  1776         </li>
  1777         <li>User agents should provide an API exposed to script that exposes the features above. The user is notified
  1778         by UI anytime interaction with Local-networked Services is requested, giving the user full ability to cancel or
  1779         abort the transaction. The user selects the Local-networked Services to be connected to the current Web page,
  1780         and can cancel these at any time. No invocations to these APIs occur silently without user intervention.
  1781         </li>
  1782       </ul>
  1783     </section>
  1784     <section class="informative appendix">
  1785       <h3>
  1786         Examples
  1787       </h3>
  1788       <div class="example">
  1789         <p>
  1790           This sample code exposes a button. When clicked, this button is disabled and the user is prompted to offer a
  1791           network service. The user may also select multiple network services. When the user has authorized a network
  1792           service to be connected to the web page then the web page issues a simple command to get a list of all the
  1793           albums stored on the connected media player service.
  1794         </p>
  1795         <p>
  1796           The button is re-enabled only when the connected network service disconnects for whatever reason (the service
  1797           becomes unavailable on the network, the user disconnects from their current network or the user revokes
  1798           access to the service from the current web page). At this point the user can re-click the button to select a
  1799           new network service to connect to the web page and the above steps are repeated.
  1800         </p>
  1801         <p>
  1802           The provided service type identifier and service interaction used in this example is based on the
  1803           well-defined service type and messaging format supported by the <a href="http://xbmc.org/about/">XBMC Media
  1804           Server</a>.
  1805         </p>
  1806         <hr>
  1807         <pre class="highlight">
  1808 &lt;input type="button" value="Start" onclick="start()" id="startBtn"/&gt;
  1809 &lt;div id="debugconsole"&gt;&lt;/div&gt;
  1810 
  1811 &lt;script&gt;
  1812  var startBtn = document.getElementById('startBtn'),
  1813      debug = document.getElementById('debugconsole');
  1814 
  1815  function start() {
  1816    if(navigator.getNetworkServices) {
  1817       navigator.getNetworkServices('zeroconf:_xbmc-jsonrpc._tcp', gotXBMCService, error);
  1818       startBtn.disabled = true;
  1819    } else {
  1820       debug.innerHTML += "&lt;br&gt;Service Discovery not supported!";
  1821    }
  1822  }
  1823 
  1824  function gotXBMCService(services) {
  1825 
  1826 // Listen for service disconnect messages
  1827 
  1828    services[0].addEventListener('serviceoffline', function ( e ) {
  1829        debug.innerHTML += "&lt;br&gt;" + services[0].name + " disconnected.";
  1830        startBtn.disabled = false;
  1831    }, false);
  1832 
  1833 // Send a service message to get albums list (and process the service response)
  1834 
  1835    var svcXhr = new XMLHttpRequest();
  1836    svcXhr.open("POST", services[0].url + "/getAlbums"); // services[0].url and its sub-resources have been
  1837                                                         // whitelisted for cross-site XHR use in this
  1838                                                         // current browsing context.
  1839 
  1840    svcXhr.setRequestHeader('Content-Type', 'application/json-rpc');
  1841 
  1842    svcXhr.addEventListener('readystatechange', function ( response ) {
  1843      if( response.readyState != 4 || response.status != 200 )
  1844         return;
  1845      debug.innerHTML += "&lt;br&gt;" + services[0].name + " response received: ";
  1846      debug.textContent += JSON.parse(response.responseText);
  1847    }, false);
  1848 
  1849    var svcMsg = [
  1850      { "jsonrpc": "2.0", "method": "AudioLibrary.GetAlbums", "params": { "genreid": -1,
  1851          "artistid": -1, "start": -1, "end": -1 }, "id": "1" }
  1852    ];
  1853 
  1854    svcXhr.send(JSON.stringify(svcMsg));
  1855    debug.innerHTML += "&lt;br&gt;" + services[0].name + " request sent: ";
  1856    debug.textContent += JSON.stringify(svcMsg);
  1857 
  1858  }
  1859 
  1860  function error( err ) {
  1861    debug.innerHTML += "&lt;br&gt;An error occurred obtaining a local network service.";
  1862    startBtn.disabled = false;
  1863  }
  1864 &lt;/script&gt;
  1865 </pre>
  1866       </div>
  1867       <div class="example">
  1868         <p>
  1869           This sample exposes a drop-down list containing a number of common Home-based audio devices. When the user
  1870           selects an audio device from the list provided, they are prompted to authorize a network service based on the
  1871           service type requested. The user may also select multiple network services matching the selected service
  1872           type. In this example, the user selects their make as being <var>Sony</var> and their model as being
  1873           <var>Bravia S1000</var> from which the Web page can derive a service type
  1874           (<var>urn:schemas-upnp-org:service:RenderingControl:1</var>).<br>
  1875           <br>
  1876           Once the user has authorized the device, the web page sends a simple mute command according to the messaging
  1877           format supported by the device.
  1878         </p>
  1879         <hr>
  1880         <pre class="highlight">
  1881 &lt;select name="make" id="make"&gt;
  1882   &lt;option selected="selected" disabled="disabled"&gt;Select make&lt;/option&gt;
  1883   &lt;option&gt;Sony&lt;/option&gt;
  1884   &lt;option&gt;Philips&lt;/option&gt;
  1885   &lt;option&gt;Alba&lt;/option&gt;
  1886 &lt;/select&gt;
  1887 &lt;select name="model" id="model"&gt;&lt;/select&gt;
  1888 &lt;div id="debugconsole"&gt;&lt;/div&gt;
  1889 
  1890 &lt;script&gt;
  1891   var debug = document.getElementById('debugconsole');
  1892 
  1893   var models = {
  1894     "Sony": [
  1895       {"name": "Bravia TV S1000", "type": "upnp", "service": "urn:schemas-upnp-org:service:RenderingControl:1" },
  1896       {"name": "Bravia TV S2000", "type": "zeroconf", "service": "_mediarenderer._http._tcp" },
  1897       {"name": "HiFi WD10", "type": "upnp", "service": "urn:schemas-upnp-org:service:RenderingControl:1" }
  1898     ],
  1899     "Philips": [ /* ... */ ],
  1900     "Alba": [ /* ... */ ]
  1901   };
  1902 
  1903   var makeEl = document.getElementById("make"),
  1904       modelEl = document.getElementById("model");
  1905 
  1906   makeEl.addEventListener('change', function() {
  1907     modelEl.innerHTML = ""; // reset
  1908     var defaultOption = document.createElement("option");
  1909     defaultOption.textContent = "Select model";
  1910     defaultOption.setAttribute("disabled", "disabled");
  1911     defaultOption.setAttribute("selected", "selected");
  1912     modelEl.appendChild(defaultOption);
  1913     for(var i = 0, l = models[makeEl.value].length; i &lt; l; i++) {
  1914       var option = document.createElement("option");
  1915       option.textContent = models[makeEl.value][i]["name"];
  1916       option.setAttribute("value", models[makeEl.value][i]["type"] + ":" + models[makeEl.value][i]["service"]);
  1917       modelEl.appendChild(option);
  1918     }
  1919   }, false);
  1920 
  1921   modelEl.addEventListener('change', function() {
  1922     if(navigator.getNetworkServices &amp;&amp;
  1923          modelEl.value == "upnp:urn:schemas-upnp-org:service:RenderingControl:1") {
  1924       navigator.getNetworkServices(modelEl.value, successCallback, errorCallback);
  1925     } else if (modelEl.value == "zeroconf:_mediarenderer._http._tcp") {
  1926       debug.innerHTML += "&lt;br&gt;Service type is not implemented by this application.";
  1927     } else {
  1928       debug.innerHTML += "&lt;br&gt;Service Discovery is not supported!";
  1929     }
  1930   }, false);
  1931 &lt;/script&gt;
  1932 
  1933 &lt;script&gt;
  1934   function successCallback( services ) {
  1935 
  1936   // Listen for service push notification messages
  1937 
  1938     services[0].addEventListener('notify', function ( msg ) {
  1939          debug.innerHTML += "&lt;br&gt;" + services[0].name + " event received: ";
  1940          debug.textContent += msg.data;
  1941     }, false);
  1942 
  1943  // Send a control signal to mute the service audio
  1944 
  1945     var svcXhr = new XMLHttpRequest();
  1946     svcXhr.open("POST", services[0].url); // services[0].url and its
  1947                                           // sub-resources have been whitelisted for
  1948                                           // cross-site XHR use in this current
  1949                                           // browsing context.
  1950 
  1951     svcXhr.setRequestHeader('SOAPAction', 'urn:schemas-upnp-org:service:RenderingControl:1#SetMute');
  1952     svcXhr.setRequestHeader('Content-Type', 'text/xml; charset="utf-8";');
  1953 
  1954     svcXhr.onreadystatechange = function ( response ) {
  1955       if( response.readyState != 4 || response.status != 200 )
  1956         return;
  1957       debug.innerHTML += "&lt;br&gt;" + services[0].name + " response received: ";
  1958       debug.textContent += response.responseXML;
  1959     }
  1960 
  1961     // Service messaging to mute the provided service
  1962     var svcMsg = '&lt;?xml version="1.0" encoding="utf-8"?&gt;' +
  1963                  '&lt;s:Envelope s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" ' +
  1964                    'xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"&gt;' +
  1965                    '&lt;s:Body&gt;' +
  1966                      '&lt;u:SetMute xmlns:u="urn:schemas-upnp-org:service:RenderingControl:1"&gt;' +
  1967                        '&lt;InstanceID&gt;0&lt;/InstanceID&gt;' +
  1968                        '&lt;Channel&gt;Master&lt;/Channel&gt;' +
  1969                        '&lt;DesiredMute&gt;true&lt;/DesiredMute&gt;' +
  1970                      '&lt;/u:SetMute&gt;' +
  1971                    '&lt;/s:Body&gt;' +
  1972                  '&lt;/s:Envelope&gt;';
  1973 
  1974     svcXhr.send(svcMsg);
  1975     debug.innerHTML += "&lt;br&gt;" + services[0].name + " request sent: ";
  1976     debug.textContent += svcMsg;
  1977   }
  1978 
  1979   function errorCallback( error ) {
  1980     debug.innerHTML += "&lt;br&gt;An error occurred: " + error.code;
  1981   }
  1982 &lt;/script&gt;
  1983 </pre>
  1984       </div>
  1985     </section>
  1986     <section>
  1987       <h3>
  1988         Acknowledgements
  1989       </h3>
  1990       <p>
  1991         Thanks are expressed by the editor to the following individuals for their feedback on this specification to
  1992         date (in alphabetical order):<br>
  1993         <br>
  1994         Gar Bergstedt, Lars-Erik Bolstad, Cathy Chan, Hari G Kumar, Bob Lund, Giuseppe Pascale, Marcin Simonides,
  1995         Clarke Stevens, Christian Söderström, Mark Vickers.
  1996       </p>
  1997       <p>
  1998         Thanks are also expressed by the editor to the following organizations and groups for their support in
  1999         producing this specification to date (in alphabetical order):<br>
  2000         <br>
  2001         CableLabs, Opera Software ASA, W3C Device APIs Working Group, W3C Web and TV Interest Group.
  2002       </p>
  2003     </section>
  2004   </body>
  2005 </html>