14:02:07 RRSAgent has joined #dap 14:02:07 logging to https://www.w3.org/2018/03/08-dap-irc 14:02:25 RRSAgent, make log public 14:02:28 present+ Fuqiao_Xue 14:02:33 Meeting: DAS Working Group teleconference 14:02:35 RRSAgent, make minutes v2 14:02:35 I have made the request to generate https://www.w3.org/2018/03/08-dap-minutes.html xfq 14:02:39 Chair: Anssi_Kostiainen 14:02:45 scribenick: xfq 14:03:00 xfq_ has joined #dap 14:03:04 scribenick: xfq_ 14:03:33 Topic: Welcome, scribe selection, agenda review, announcements 14:04:15 present+ Wanming_Lin 14:04:57 anssik: We met in Jan. Made lots of progress since then. 14:04:59 ... Will talk about publication plan and new charter today. 14:05:06 Topic: Sensor APIs wide review response 14:05:20 https://github.com/w3c/sensors/issues/299 14:06:11 https://github.com/w3c/sensors/issues/299#issuecomment-369924348 14:06:27 anssik: In the TAG issue (https://github.com/w3ctag/design-reviews/issues/207), we got a lot of feedback 14:06:28 ... also got feedback from PING 14:06:57 Search "Proposed changes:" 14:07:50 anssik: Search "Proposed changes:" in this issue to find PRs corresponding to the feedbacks 14:08:14 s/from PING/from Security IG and PING/ 14:09:08 Summary: Based on the group's assessment, TAG review feedback did not yield normative changes to the specifications under wide review. The review comments helped improve various informative aspects of the specifications and readability was further improved. The review comments further reinforced group's view that the specifications are ready to advance to Candidate Recommendation stage in the near future. 14:09:23 present+ alexander_shalomov 14:09:38 present+ Anssi_Kostiainen 14:09:58 present+ Mikhail_Pozdnyakov 14:10:08 anssik: the sensors specs are ready to go to CR 14:10:26 Topic: Sensor APIs issue review 14:10:46 https://github.com/w3c/sensors/projects/4 14:11:13 anssik: I would like to congratulate the group to close all Level 1 issues 14:11:37 Throw exception when screen coordinate system is not supported 14:11:44 https://github.com/w3c/accelerometer/issues/35 14:12:09 s/Level 1 issues/Level 1 issues of Generic Sensor/ 14:12:45 anssik: propose to discuss open issues of concrete sensors specs today 14:13:51 anssik: I personally think feature detection of this is useful 14:13:51 ... WDYT? 14:19:02 RRSAgent, make minutes v2 14:19:02 I have made the request to generate https://www.w3.org/2018/03/08-dap-minutes.html xfq_ 14:21:48 OrientationSensor interface to provide Euler angles 14:21:58 https://github.com/w3c/orientation-sensor/issues/43 14:22:15 [silence] 14:22:15 anssik: ok, we will make it in L1 14:25:36 alexander_shalomov: manual conversion in JS is needed currently 14:25:37 ... if you search "how to use motion sensors on the web", the results use old APIs 14:26:55 anssik: we need to decide if this feature is in scope [in L1] 14:28:04 anssik: should we decide to defer this to L2, or in a new CR of L1? 14:28:16 s/decide to// 14:28:35 GeomagneticOrientationSensor interface 14:28:44 alexander_shalomov: L2, I think. 14:28:47 https://github.com/w3c/orientation-sensor/issues/15 14:28:48 anssik: ok then. 14:30:48 Improve guidance on UI for user consenting 14:31:01 anssik: we'll defer orientation-sensor#15 to L2 too 14:31:04 https://github.com/w3c/sensors/issues/352 14:32:04 anssik: this is a very recent issue 14:32:04 ... it's about guidance on UI for user consenting 14:33:13 ... what the spec does now is providing extension points 14:33:18 https://github.com/w3c/sensors/pull/353 14:33:42 https://w3c.github.io/sensors/#security-and-privacy 14:35:02 ... this PR basically adds a note 14:35:04 ... in my opinion the issue is addressed 14:35:19 ... any comment? 14:36:13 Mikhail_Pozdnyakov: in my opinion, this is beyond our scope 14:36:17 ... the mitigation strategies already mitigate the potential risks 14:37:15 anssik: this spec is a huge improvement over the previous APIs in terms of security and privacy 14:37:50 ... propose to close this issue; feel free to comment/reopen if you have further comments. 14:38:00 Topic: Sensor APIs CR readiness 14:38:30 https://github.com/w3c/sensors/issues/355 14:38:57 anssik: I created a meta issue 14:39:02 Generic Sensor API - https://w3c.github.io/sensors/ 14:39:02 Ambient Light Sensor - https://w3c.github.io/ambient-light/ 14:39:02 Accelerometer - https://w3c.github.io/accelerometer/ 14:39:02 Gyroscope - https://w3c.github.io/gyroscope/ 14:39:03 Magnetometer - https://w3c.github.io/magnetometer/ 14:39:03 Orientation Sensor - https://w3c.github.io/orientation-sensor/ 14:39:46 ... the CR scope is clear 14:39:48 ... I went through the CR requirements in the Process 14:40:20 ... we have requested wide review 14:40:36 s/requested/requested and received/ 14:40:58 must show that the specification has met all Working Group requirements, or explain why the requirements have changed or been deferred, 14:42:03 https://w3c.github.io/sensors/usecases 14:42:13 https://w3c.github.io/motion-sensors/ 14:42:28 ... based on my assessment, the specs meet the requirements set forth in the DAS WG Charter 14:42:29 ... and satisfy Sensor Use Cases as demonstrated in Motion Sensors Explainer 14:42:49 must document changes to dependencies during the development of the specification, 14:43:23 must document how adequate implementation experience will be demonstrated, 14:43:32 ... see changes to dependencies in the issue 14:44:07 ... we have test suites and preliminary implementation reports 14:44:26 Propose: The CR exit criterion is two interoperable deployed implementations of each feature. 14:44:42 must specify the deadline for comments, which must be at least four weeks after publication, and should be longer for complex documents, 14:44:46 ... CR exit criteria means "when are we ready to move to the next stage (PR)?" 14:44:54 Proposal: This Candidate Recommendation is expected to advance to Proposed Recommendation no earlier than [six weeks after its publication]. 14:45:39 must show that the specification has received wide review, 14:46:01 Wide review received, see tracker https://github.com/w3c/sensors/issues/299 14:46:02 ... we will use six weeks for the deadline for comments, because there're multiple specs 14:46:19 may identify features in the document as "at risk". These features may be removed before advancement to Proposed Recommendation without a requirement to publish a new Candidate Recommendation. 14:47:07 Proposal: No features are marked as 'at-risk'. 14:47:51 ... "at risk" means if you're not confident whether a feature will be in the final recommendation, you can mark it "at risk" and remove it before PR 14:47:51 ... I don't identify such features in the sensors specs 14:48:19 ... I'll send a Call for Consensus for the CR 14:49:34 Mikhail_Pozdnyakov: for Chrome implementation we don't need throw exception when screen coordinate system is not supported 14:50:00 s/when screen coordinate system is not supported/[when screen coordinate system is not supported]/ 14:50:53 Topic: Rechartering 14:54:25 anssik: W3C Management (hopefully) reviewed the draft charter yesterday 14:54:28 ... do you have more info, xfq? 14:54:32 xfq: not currently, will check. 14:55:02 Topic: AOB 14:55:26 anssik: I'll be on vacation 14:55:51 RRSAgent, make minutes v2 14:55:51 I have made the request to generate https://www.w3.org/2018/03/08-dap-minutes.html xfq_ 15:13:04 xfq has left #dap 15:21:33 xfq has joined #dap 15:21:45 xfq has left #dap 15:29:16 xfq has joined #dap 15:29:28 Zakim, bye 15:29:28 leaving. As of this point the attendees have been Fuqiao_Xue, Wanming_Lin, alexander_shalomov, Anssi_Kostiainen, Mikhail_Pozdnyakov 15:29:28 Zakim has left #dap 15:29:37 RRSAgent, bye 15:29:37 I see no action items