Rewrite of the abstract.

sysapps · Mar 5, 2013 · de69622 · de69622
1 parent eae6fb2
commit de69622
Show file tree

Hide file tree

Showing 2 changed files with 18 additions and 10 deletions.
diff --git a/images/apptypes.png b/images/apptypes.png
diff --git a/index.html b/index.html
@@ -45,16 +45,24 @@
   </head>
 
   <body>
-    <section id='abstract'>
-      This document specifies the runtime and security model of Web Applications.
-      It is describing how an application is defined trough an application
-      manifest, how it can be installed, updated and packaged. It is also
-      specifying how such an application can put in background, put back in
-      foreground or waken up.<br>
-      Finaly, the document describes the security model for such applications.
-      This includes the permission model and the different security rules that
-      would apply.
-    </section>
+
+  <section id='abstract'>
+      <p>
+        This document specifies two classes of Web application: <em>hosted Web applications</em> and <em>packaged applications</em>. These applications differ from traditional  Web applications in their life cycle, security model, and access to APIs that are not normally available to Web applications. Conceptually, the application manifest indicates that an application can be &quot;installed&quot; on an end-user's device. What distinguishes a traditional Web application from a hosted web application is  an application manifest: this is a JSON resource that contains application specific metadata (e.g., the name of the application), and optionally various security related permission requests to resources on the Web and/or services and capabilities on the device.
+    </p>
+      <figure>
+        <img src="images/apptypes.png" alt="">
+        <figcaption>
+          The figure shows the overlap between traditional web applications, hosted web applications, and packaged applications. Web applications make use of standard Web technologies but don't make use of of an application manifest. On the other hand, hosted applications make use of an application manifest, while packaged applications have both an application manifest and are packaged using [[!ZIP]].
+        </figcaption>
+      </figure>
+      <p>
+        Installation of hosted or packaged applications onto a device can be initiated through  either linking to an application manifest or through the use of the <code> ApplicationRegistry</code> API. This API gives a developer a degree of control over the installation process, as well as providing a means to programmatically unistall an application.
+      </p>
+      <p>
+        This specification also specifies aspects related to the application's lifecycle that are outside the control of the developer. These events sometimes result in <em>system messages</em> being generated. Developers can register event listeners to listen for these special events during the life cycle of their application.
+      </p>
+  </section>
 
     <section>
       <h2>Terminology</h2>