- From: <Frederick.Hirsch@nokia.com>
- Date: Tue, 20 Aug 2013 18:59:42 +0000
- To: <public-device-apis@w3.org>
- CC: <Frederick.Hirsch@nokia.com>
Before starting the CfC to go to CR with Light Events and Proximity I suggest we update the editors drafts to address the issues Dom raised, and also double check that there are no remaining issues from the earlier discussion thread with Anne. I have entered tracker issues against light/proximity for the issues Dom raised: [OPEN] ISSUE-141 : Allow for infinite values in DeviceLightEventInit dictionary ; on [Light Events API] http://www.w3.org/2009/dap/track/issues/141 [OPEN] ISSUE-142 : Allow for infinite values in DeviceProximityEventInit dictionary ; on [Proximity API] http://www.w3.org/2009/dap/track/issues/142 [OPEN] ISSUE-143 : should have a normative dependency on WebIDL, add reference ; on [Light Events API] http://www.w3.org/2009/dap/track/issues/143 [OPEN] ISSUE-144 : should have a normative dependency on WebIDL, add reference ; on [Proximity API] http://www.w3.org/2009/dap/track/issues/144 [OPEN] ISSUE-145 : initialize Default value for LightLevelState to empty string ; on [Light Events API] http://www.w3.org/2009/dap/track/issues/145 I believe the WG has agreed to not make a single specification for these various specifications but did not see a formal resolution to that effect. If I missed it please let me know. I'm going to wait with the CR CfC until we've closed these issues. Thanks regards, Frederick Frederick Hirsch, Nokia Chair, W3C DAP Working Group Related to tracker ACTION-647, ACTION-647
Received on Tuesday, 20 August 2013 19:00:12 UTC