--- a/tvprofile/tv-src.html	Thu Jan 19 16:30:38 2012 +0100
+++ b/tvprofile/tv-src.html	Fri Jan 20 12:57:34 2012 +0100
@@ -183,13 +183,29 @@
 		<p>
 		The main goal of this profile is to simplify and harmonize the production and delivery of <a>TV Services</a> to web enabled devices. For the purposes of this document a <dfn>TV service</dfn> is a commercial video service that may include elements of interactivity and that provides a coherent user experience. TV services are usually divided into two main groups: <dfn title="scheduled service">scheduled</dfn> or <dfn title="linear service">linear</dfn> services are the ones that have to be consumed by the user at the particular point in time when they are offered (e.g. a broadcast TV channel); <dfn title="on-demand service">on-demand</dfn> services are the ones that can be consumed by the user at any point in time (e.g. web video portals).
 		<p>
-		In order to consume them, users need a <dfn>device</dfn> that is able to present TV services. Traditionally TV services have been consumed mainly via <a>TV set</a>s or <a>STB</a>s connected to a display. Nowadays users have a wide range of devices (e.g. PC, laptops,smartphones, tablets) available both in their home and outside and expect to be able to access to TV services from any device.
+		In order to consume them, users need a <dfn>device</dfn> that is able to present TV services. Traditionally TV services have been consumed via <a>TV set</a>s or <a>STB</a>s connected to a display. Nowadays users have a wide range of devices (e.g. PC, laptops,smartphones, tablets) available both in their home and outside and expect to be able to access to TV services from any device.
 		<p>
 		<a>TV service</a>s can be delivered to users via a variety of means. The most common means is via a uni-directional TV <dfn>broadcast network</dfn>. Different standards have been defined for such purpose, such as <a>DVB</a>, <a>ATSC</a>, <a>ISDB</a>. <a>TV service</a>s may also be delivered via bi-directional IP connections, mainly via the Internet. An emerging scenario is represented by content streamed directly between devices connected via the <dfn>home network</dfn>. The term <a>home network</a> refers to the networking infrastructure that facilitates communications between devices within the home. This will typically (but not always) be connected to the Internet.
 		<p>
-		To provide a level of interactivity, <a>TV service</a>s may be associated to or delivered as <a>application</a>s. For the purposes of this document the term <dfn>application</dfn> refers to a collection of documents and associated resources that are authored using a set of languages commonly referred to as "web technologies" or "web standards". In order to be able to run <a>application</a>s, <a>device</a>s implement an  <a class="externalDFN">interactive user agent</a> commonly referred to as <dfn>browser</dfn>. The set of languages supported by <a>browser</a>s conforming to this profile are listed in <a href="#app-environment" class="sectionRef"></a>.
+		To provide a level of interactivity, <a>TV service</a>s may be associated to or delivered as <a>application</a>s.
 </section>
 
+<section>
+<h2>Application model</h2>
+	
+	For the purposes of this document the term <dfn>application</dfn> refers to a collection of documents and associated resources that are authored using a set of languages commonly referred to as "web technologies" or "web standards". In order to be able to run <a>application</a>s, <a>device</a>s implement an  <a class="externalDFN">interactive user agent</a> commonly referred to as <dfn>browser</dfn>. The set of languages supported by <a>browser</a>s conforming to this profile are listed in <a href="#app-environment" class="sectionRef"></a>.
+	
+	<section class="informative">
+		<h2>Launching applications</h2>
+	</section>
+	
+	<section>
+	<h2>Client side applications</h2>
+		While <a>application</a>s are commonly hosted on a Web Servers and the associated resources fetched by the <a>browser</a> when required, sometimes a single download and installation on a <a>device</a> is desirable. In order to enable this, <a>device</a>s SHALL support the packaging format defined by the [[!WIDGETS]]] specification. Widgets are typically downloaded and installed on a client machine or device and can run as stand-alone applications, but they can also be embedded into Web pages and run in a <a>browser</a>.
+	</section>
+</section>
+
+
 <section id="app-environment">
 <h2>Application Environment</h2>
  This section lists which languages are supported by <a>browser</a>s conforming to this profile and that can be used to author <a>application</a>s. <a>Browser</a>s may support more languages than the ones listed in this section.