adding "Application Lifecycle and Events"

dret · Jul 24, 2015 · b14b2f9 · b14b2f9
1 parent f8918bf
commit b14b2f9
Show file tree

Hide file tree

Showing 4 changed files with 12 additions and 6 deletions.
diff --git a/MD/history.md b/MD/history.md
@@ -1,6 +1,6 @@
 # HTML5 Overview: Change Log
 
-* July 24, 2015: changed status of ["The app: URL Scheme"](http://www.w3.org/TR/app-uri/) and ["TCP and UDP Socket API"](http://www.w3.org/TR/tcp-udp-sockets/) from WD to NOTE
+* July 24, 2015: changed status of ["The app: URL Scheme"](http://www.w3.org/TR/app-uri/) and ["TCP and UDP Socket API"](http://www.w3.org/TR/tcp-udp-sockets/) from WD to NOTE, added ["Application Lifecycle and Events"](http://sysapps.github.io/app-lifecycle/)
 * July 23, 2015: changed status of ["Task Scheduler API Specification"](http://www.w3.org/TR/task-scheduler/) from WD to NOTE
 * July 21, 2015: added ["Preload"](http://www.w3.org/TR/preload/)
 * July 16, 2015: added ["Performance Timeline Level 2"](http://www.w3.org/TR/performance-timeline-2/)

diff --git a/MD/notes.md b/MD/notes.md
@@ -26,7 +26,7 @@ Please keep in mind that [W3C NOTE documents have no official standing and often
 * [Resource Priorities](http://www.w3.org/TR/resource-priorities "This specification defines a means for site developers to programmatically give the User Agent hints on the download priority of a resource. This will allow User Agents to more efficiently manage the order in which resources are downloaded.")
 * [Selectors API Level 2](http://www.w3.org/TR/selectors-api2 "The Selectors API specification defines methods for retrieving element nodes from the DOM by matching against a group of selectors, and for testing if a given element matches a particular selector.")
 * [System Information API](http://www.w3.org/TR/system-info-api "This specification defines an API to provide Web applications with access to various properties of the system which they are running on. Specifically, properties pertaining to the device hardware are addressed. Examples include battery status, current network bandwidth. Additionally, some of those properties offer access to the environment around the device, such as ambient brightness or atmospheric pressure.")
-* [TCP and UDP Socket API](http://www.w3.org/TR/tcp-udp-sockets "This API provides interfaces to raw UDP sockets, TCP Client sockets and TCP Server sockets.")
+* [TCP and UDP Socket API](http://www.w3.org/TR/tcp-udp-sockets "This API provides interfaces to raw UDP sockets, TCP Client sockets and TCP Server sockets. As such, this requires a high level of trust in applications that use this API, since raw sockets can be used to work around the same origin security policy.")
 * [Task Scheduler API Specification](http://www.w3.org/TR/task-scheduler "This specification defines an API to schedule a task at a specified time. When the indicated time is reached, the application that scheduled the task will be notified via a functional event on a service worker. A task event will be delivered to a service worker, regardless of whether the application is active on user agent. Applications such as an alarm clock or an auto-updater may utilize this API to perform certain action at a specified time.")
 * [The Messaging API](http://www.w3.org/TR/messaging-api "This specification defines an API that provides access to messaging functionality in the device, including SMS, MMS and email.")
 * [The app: URL scheme](http://www.w3.org/TR/app-uri "This specification defines the app: URL scheme. The app: URL scheme can be used by packaged applications to obtain resources that are inside a container. These resources can then be used with web platform features that accept URLs.")

diff --git a/README.md b/README.md
@@ -1,10 +1,10 @@
 # HTML5 Overview
 
-HTML5 is more a movement (or maybe it's more appropriate to call it a *brand*) than it is a technology. It says "more power to the browser" but mostly means "more power to the browser *as a programming platform*". Given this focus of HTML5, it is surprisingly hard to find a good place where all the APIs under development are listed. This collection is an attempt to have all that information in one place. The current status captured on this page lists 138 specifications. Since the HTML5 landscape is changing fairly quickly, it is likely that some information on this page is outdated. If that is the case, please submit an issue or create a pull request (please keep in mind that the [MD](README.md) is generated from [XML](html5.xml) via [XSLT](XSLT/xml2md.xsl)). Thanks!
+HTML5 is more a movement (or maybe it's more appropriate to call it a *brand*) than it is a technology. It says "more power to the browser" but mostly means "more power to the browser *as a programming platform*". Given this focus of HTML5, it is surprisingly hard to find a good place where all the APIs under development are listed. This collection is an attempt to have all that information in one place. The current status captured on this page lists 139 specifications. Since the HTML5 landscape is changing fairly quickly, it is likely that some information on this page is outdated. If that is the case, please submit an issue or create a pull request (please keep in mind that the [MD](README.md) is generated from [XML](html5.xml) via [XSLT](XSLT/xml2md.xsl)). Thanks!
 
 Most HTML5 specifications are [W3C](http://www.w3.org/ "World Wide Web Consortium") [TR track documents](http://www.w3.org/2014/Process-20140801/#rec-advance "W3C Technical Reports"), and of those this page lists 95 current specifications, while [a separate page lists 32 specifications that were retired as notes](MD/notes.md) (127 total).
 
-HTML5 specifications are also developed in other places, and this page lists 11 of these other specifications.
+HTML5 specifications are also developed in other places, and this page lists 12 of these other specifications.
 
 Here's a list of all HTML5 specs captured in the [XML source for this page](html5.xml), first W3C TR (except for the [separately listed NOTEs](MD/notes.md)), and then others:
 
@@ -114,8 +114,9 @@ Here's a list of all HTML5 specs captured in the [XML source for this page](html
 * [WebVTT: The Web Video Text Tracks Format](http://www.w3.org/TR/webvtt1 "This specification defines WebVTT, the Web Video Text Tracks format. Its main use is for marking up external text track resources in connection with the HTML <track> element. WebVTT files provide captions or subtitles for video content, and also text video descriptions, chapters for content navigation, and more generally any form of metadata that is time-aligned with audio or video content.")
 * [XMLHttpRequest](http://www.w3.org/TR/XMLHttpRequest "The XMLHttpRequest specification defines an API that provides scripted client functionality for transferring data between a client and a server.")
 
-## Other Specifications (11 Specs)
+## Other Specifications (12 Specs)
 
+* [Application Lifecycle and Events](app-lifecycle "This specification extends ServiceWorkerGlobalScope with APIs for managing the lifecycle of an application and associated events.") ([ED](http://sysapps.github.io/app-lifecycle/ "Editor's Draft"))
 * [Fetch](https://fetch.spec.whatwg.org/ "The Fetch standard defines requests, responses, and the process that binds them; fetching.")
 * [FileSystem API](http://w3c.github.io/filesystem-api/ "The FileSystem API defines functionality on a local sandboxed file system within the same origin of the Web Application that created it. It exposes standard file system operations to Web Applications, such as creation of files and directories, and reading and writing of them (from and to disk), including other programmatic manipulation of files and directories.")
 * [Fullscreen API](https://fullscreen.spec.whatwg.org/ "Fullscreen defines the fullscreen API for the web platform.")

diff --git a/html5.xml b/html5.xml
@@ -81,6 +81,11 @@
             <title>Generic Sensor API</title>
             <abstract>This specification defines a framework for exposing sensor data to the Open Web Platform in a consistent way. It does so by defining a blueprint for writing specifications of concrete sensors along with an abstract Sensor interface that can be extended to accommodate different sensor types.</abstract>
         </spec>
+        <spec id="app-lifecycle" ed="http://sysapps.github.io/app-lifecycle/" status="other">
+            <class ref="monitoring">[[ explanation needed ]]</class>
+            <title>Application Lifecycle and Events</title>
+            <abstract>This specification extends ServiceWorkerGlobalScope with APIs for managing the lifecycle of an application and associated events.</abstract>
+        </spec>
         <spec id="ambient-light" status="WD">
             <class ref="device">Provides access to light sensor of an device.</class>
             <title>Ambient Light Events</title>
@@ -733,7 +738,7 @@
         </spec>
     </specs>
     <log>
-        <entry date="2015-07-24">changed status of <a href="http://www.w3.org/TR/app-uri/"><q>The app: URL Scheme</q></a> and <a href="http://www.w3.org/TR/tcp-udp-sockets/"><q>TCP and UDP Socket API</q></a> from WD to NOTE</entry>
+        <entry date="2015-07-24">changed status of <a href="http://www.w3.org/TR/app-uri/"><q>The app: URL Scheme</q></a> and <a href="http://www.w3.org/TR/tcp-udp-sockets/"><q>TCP and UDP Socket API</q></a> from WD to NOTE, added <a href="http://sysapps.github.io/app-lifecycle/"><q>Application Lifecycle and Events</q></a></entry>
         <entry date="2015-07-23">changed status of <a href="http://www.w3.org/TR/task-scheduler/"><q>Task Scheduler API Specification</q></a> from WD to NOTE</entry>
         <entry date="2015-07-21">added <a href="http://www.w3.org/TR/preload/"><q>Preload</q></a></entry>
         <entry date="2015-07-16">added <a href="http://www.w3.org/TR/performance-timeline-2/"><q>Performance Timeline Level 2</q></a></entry>