dap: discovery-api/Overview.src.html@8b03e17da083 (annotated)

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

author	Rich Tibbett <richt@opera.com>
	Mon, 04 Feb 2013 13:47:41 +0100
changeset 371	8b03e17da083
parent 332	e19dc529aacc
child 372	7639401e21f4
permissions	-rw-r--r--