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