W3C home > Mailing lists > Public > public-sysapps@w3.org > April 2014

Re: Comment on "Application Lifecycle and Events"

From: Philipp Hoschka <ph@w3.org>
Date: Mon, 07 Apr 2014 17:43:28 +0200
Message-ID: <5342C7A0.5060505@w3.org>
To: "Kostiainen, Anssi" <anssi.kostiainen@intel.com>
CC: "public-sysapps@w3.org" <public-sysapps@w3.org>
Hi Anssi,

thanks - that handles my comment very well!

-Philipp

On 4/7/2014 9:58 AM, Kostiainen, Anssi wrote:
> Hi Philipp, All,
>
> On 05 Apr 2014, at 19:55, Philipp Hoschka <ph@w3.org> wrote:
>
>> (following recommended procedure from StD " If you wish to make comments regarding this document, please send them to public-sysapps@w3.org ")
>>
>> The draft contains the following sentence
>>
>>> Below is a list of use cases derived from the initial input to the System Applications Working Group Charter that are not addressed by the Runtime and Security Model for Web Applications [SYSAPPS-RUNTIME].
>> However, the Runtime and Security Model spec says that the WG is "currently not progressing the approach outlined in this draft".
>>
>> So while the sentence above is probably a true statement, it probably needs either
>> - a bit more explanation/background on the security model and that it has been dropped
>> - and/or to change to say where the use cases that were formerly addressed in the Runtime  and Security Model are now addressed (possibly the manifest spec?)
> I clarified the intro in the Use Cases and Requirements section as follows [1]:
>
> [[
>
> Below is a list of use cases derived from the initial input to the System Applications Working Group Charter that were not addressed by the Runtime and Security Model for Web Applications [SYSAPPS-RUNTIME]  a proposal the group decided to obsolete due to lack of implementers' interest. Currently, the domain initially covered by [SYSAPPS-RUNTIME] is split across multiple specifications and the use cases compatible with the Web security model are being addressed by a set of specifications: Application Lifecycle and Events and its normative dependencies Service Workers [SERVICEWORKERS], Task Scheduler [TASKSCHEDULER], and the Manifest for web applications [appmanifest]. The set of specifications is expected to grow over time to cover more of the domain and use cases.
>
> ]]
>
> Philipp - please let us know if this addresses your concerns, or if you have suggestions for rewording.
>
> Thanks,
>
> -Anssi
>
> [1] https://github.com/sysapps/app-lifecycle/commit/63cbad92a98b4f2726fc060917189a2cd3d33f42
>
Received on Monday, 7 April 2014 15:44:05 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:36:20 UTC