- From: Marta Pawlowska <m.pawlowska@samsung.com>
- Date: Fri, 17 May 2013 11:19:40 +0200
- To: 'Filip Maj' <fil@adobe.com>, 'Hsin-Yi Tsai' <htsai@mozilla.com>, 'Mounir Lamouri' <mounir@lamouri.fr>
- Cc: public-sysapps@w3.org
+1 for new name -----Original Message----- From: Filip Maj [mailto:fil@adobe.com] Sent: Thursday, May 16, 2013 4:30 AM To: Hsin-Yi Tsai; Mounir Lamouri Cc: public-sysapps@w3.org Subject: Re: Rename "Web Alarms API" to "Task Scheduler" +1 On 5/15/13 7:27 PM, "Hsin-Yi Tsai" <htsai@mozilla.com> wrote: >+ 1 to renaming > >On 2013年05月16日 00:01, Mounir Lamouri wrote: >> Hi, >> >> I would like to start a few discussions regarding the outstanding issues >> we currently have with the Alarm API. To keep things simpler, I will >> restrict every thread to one topic. >> >> First of all, we should change the name of this specification. I think >> that everybody will agree that the name is terrible, doesn't reflect >> what we want to do and let people believe it is trying to do things it >> isn't really designed for. >> >> To start the discussion, I would like to propose to rename the >> specification "Task Scheduler". Task is unfortunately used in other >> specifications like HTML [1] but the naming isn't too overloaded and the >> closest name I can think of would be "event" which is way too much used >> in the Web Platform. >> >> If the specification is renamed "Task Scheduler", I think we should >> rename the "Alarm" interface "ScheduledTask". >> >> Any thoughts on this? >> >> [1] >> >>http://www.whatwg.org/specs/web-apps/current-work/multipage/webappapis.ht >>ml#event-loops >> >> Thanks, >> -- >> Mounir >> > >-- >Hsin-Yi Tsai 蔡欣宜 >Mozilla Taiwan >T: +886-2-87861100 ext:312 >htsai@mozilla.com > >
Received on Friday, 17 May 2013 10:18:29 UTC