Weekly github digest (Device and Sensors WG specifications)

Issues
------
* w3c/sensors (+3/-11/💬23)
  3 issues created:
  - What's the rationale of moving security checks outside of normative requirements? (by tobie)
    https://github.com/w3c/sensors/issues/287
  - bikeshed link errors (by rwaldron)
    https://github.com/w3c/sensors/issues/284
  - Split security-questionnaire.md into smaller chunks for each concrete sensor API and add Rick's comments from https://github.com/w3c/sensors/pull/270#issuecomment-330579933 (by alexshalamov)
    https://github.com/w3c/sensors/issues/281

  7 issues received 23 new comments:
  - #287 What's the rationale of moving security checks outside of normative requirements? (8 by tobie, pozdnyakov, danbri, lknik, alexshalamov)
    https://github.com/w3c/sensors/issues/287
  - #269 Undefined values makes GS a pain to work with using TypeScript (5 by kenchris, alexshalamov)
    https://github.com/w3c/sensors/issues/269
  - #7 Sensor discovery (4 by larsgk, anssiko)
    https://github.com/w3c/sensors/issues/7
  - #223 Should a "suspended" state be added (2 by tobie, alexshalamov)
    https://github.com/w3c/sensors/issues/223
  - #284 bikeshed link errors (2 by alexshalamov, pozdnyakov)
    https://github.com/w3c/sensors/issues/284
  - #193 Security issues when used in combination with other APIs (1 by lknik)
    https://github.com/w3c/sensors/issues/193
  - #281 Split security-questionnaire.md into smaller chunks for each concrete sensor API and add Rick's comments (1 by alexshalamov)
    https://github.com/w3c/sensors/issues/281

  11 issues closed:
  - Take into account user gestures as an input for security policy enforcement https://github.com/w3c/sensors/issues/196
  - Should a "suspended" state be added https://github.com/w3c/sensors/issues/223
  - Should a "suspended" state be added https://github.com/w3c/sensors/issues/223
  - Missing browsing-context focus/unfocus hooks in HTML spec. https://github.com/w3c/sensors/issues/222
  - Define algorithm for suspending / resuming activated sensor objects https://github.com/w3c/sensors/issues/227
  - bikeshed link errors https://github.com/w3c/sensors/issues/284
  - Split security-questionnaire.md into smaller chunks for each concrete sensor API and add Rick's comments https://github.com/w3c/sensors/issues/281
  - Find a clearer name for the sensor concept https://github.com/w3c/sensors/issues/162
  - Security issues when used in combination with other APIs https://github.com/w3c/sensors/issues/193
  - Simplify extension of the Permissions API for concrete sensor implementations https://github.com/w3c/sensors/issues/22
  - granularity of Permission name for concrete/ fusion sensors  https://github.com/w3c/sensors/issues/132

* w3c/accelerometer (+0/-2/💬2)
  1 issues received 2 new comments:
  - #23 Why unrestricted double for acceleration readings? (2 by pozdnyakov)
    https://github.com/w3c/accelerometer/issues/23

  2 issues closed:
  - Why unrestricted double for acceleration readings? https://github.com/w3c/accelerometer/issues/23
  - Add use cases to spec https://github.com/w3c/accelerometer/issues/18

* w3c/dap-charter (+1/-2/💬1)
  1 issues created:
  - Adapt normative deliverable list to process 2017 requirements (by dontcallmedom)
    https://github.com/w3c/dap-charter/issues/35

  1 issues received 1 new comments:
  - #35 Adapt normative deliverable list to process 2017 requirements (1 by dontcallmedom)
    https://github.com/w3c/dap-charter/issues/35

  2 issues closed:
  - Stop joint work on media capture task force https://github.com/w3c/dap-charter/issues/27
  - Restart work on DeviceOrientation Event API https://github.com/w3c/dap-charter/issues/31



Pull requests
-------------
* w3c/sensors (+11/-11/💬24)
  11 pull requests submitted:
  - Make 'Conditions to expose sensor readings' must (by pozdnyakov)
    https://github.com/w3c/sensors/pull/288
  - Remove duplicate Service Worker inline issue (by alexshalamov)
    https://github.com/w3c/sensors/pull/286
  - A small fix in 'Reading change threshold' description (by pozdnyakov)
    https://github.com/w3c/sensors/pull/285
  - Fix typo: treshold => threshold (by alexshalamov)
    https://github.com/w3c/sensors/pull/283
  - Split security & privacy questionnaire (by alexshalamov)
    https://github.com/w3c/sensors/pull/282
  - Introduce "condition to update latest reading" (by alexshalamov)
    https://github.com/w3c/sensors/pull/280
  - Introduce Default Sensor concept (by pozdnyakov)
    https://github.com/w3c/sensors/pull/279
  - Fix mistypes (by pozdnyakov)
    https://github.com/w3c/sensors/pull/278
  - Introduce a Reading Change Treshold concept (by pozdnyakov)
    https://github.com/w3c/sensors/pull/277
  - Fix typos (by anssiko)
    https://github.com/w3c/sensors/pull/276
  - Fix #193: Define extension spec Security & Privacy expectations (by anssiko)
    https://github.com/w3c/sensors/pull/275

  9 pull requests received 24 new comments:
  - #288 Make 'Conditions to expose sensor readings' must (7 by tobie, pozdnyakov, anssiko, alexshalamov)
    https://github.com/w3c/sensors/pull/288
  - #274 Define sensor.hasReading accessor bound to [[lastEventFiredAt]]. Fixes gh-269 (7 by pozdnyakov, anssiko, rwaldron)
    https://github.com/w3c/sensors/pull/274
  - #279 Introduce Default Sensor concept (4 by anssiko, pozdnyakov)
    https://github.com/w3c/sensors/pull/279
  - #270 Answer Security and Privacy self review questionnaire (1 by alexshalamov)
    https://github.com/w3c/sensors/pull/270
  - #207 Add 'user triggered activation' as mitigation strategy (1 by alexshalamov)
    https://github.com/w3c/sensors/pull/207
  - #272 Fix Bikeshed custom header rendering bug (1 by anssiko)
    https://github.com/w3c/sensors/pull/272
  - #275 Fix #193: Define extension spec Security & Privacy expectations (1 by anssiko)
    https://github.com/w3c/sensors/pull/275
  - #277 Introduce a Reading Change Treshold concept (1 by anssiko)
    https://github.com/w3c/sensors/pull/277
  - #282 Split security & privacy questionnaire (1 by anssiko)
    https://github.com/w3c/sensors/pull/282

  11 pull requests merged:
  - Remove duplicate Service Worker inline issue
    https://github.com/w3c/sensors/pull/286
  - Introduce "condition to update latest reading"
    https://github.com/w3c/sensors/pull/280
  - A small fix in 'Reading change threshold' description
    https://github.com/w3c/sensors/pull/285
  - Introduce Default Sensor concept
    https://github.com/w3c/sensors/pull/279
  - Fix typo: treshold => threshold
    https://github.com/w3c/sensors/pull/283
  - Split security & privacy questionnaire
    https://github.com/w3c/sensors/pull/282
  - Introduce a Reading Change Treshold concept
    https://github.com/w3c/sensors/pull/277
  - Fix mistypes
    https://github.com/w3c/sensors/pull/278
  - Redefine [=sensor=] concept
    https://github.com/w3c/sensors/pull/273
  - Fix typos
    https://github.com/w3c/sensors/pull/276
  - Fix #193: Define extension spec Security & Privacy expectations
    https://github.com/w3c/sensors/pull/275

* w3c/ambient-light (+3/-3/💬1)
  3 pull requests submitted:
  - Use value getter operation and fix illuminance attribute type (by alexshalamov)
    https://github.com/w3c/ambient-light/pull/42
  - Add security and privacy questionnaire for Ambient Light Sensor (by alexshalamov)
    https://github.com/w3c/ambient-light/pull/41
  - Define 'Ambient Light Sensor' sensor type (by anssiko)
    https://github.com/w3c/ambient-light/pull/40

  1 pull requests received 1 new comments:
  - #42 Use value getter operation and fix illuminance attribute type (1 by anssiko)
    https://github.com/w3c/ambient-light/pull/42

  3 pull requests merged:
  - Use value getter operation and fix illuminance attribute type
    https://github.com/w3c/ambient-light/pull/42
  - Add security and privacy questionnaire for Ambient Light Sensor
    https://github.com/w3c/ambient-light/pull/41
  - Define 'Ambient Light Sensor' sensor type
    https://github.com/w3c/ambient-light/pull/40

* w3c/accelerometer (+3/-3/💬1)
  3 pull requests submitted:
  - Add security-questionnaire.md for Accelerometer sensor (by alexshalamov)
    https://github.com/w3c/accelerometer/pull/26
  - Use value getter operation and fix attribute types (by alexshalamov)
    https://github.com/w3c/accelerometer/pull/25
  - Define Accelerometer sensor type, clarify latest reading (by anssiko)
    https://github.com/w3c/accelerometer/pull/24

  1 pull requests received 1 new comments:
  - #25 Use value getter operation and fix attribute types (1 by anssiko)
    https://github.com/w3c/accelerometer/pull/25

  3 pull requests merged:
  - Use value getter operation and fix attribute types
    https://github.com/w3c/accelerometer/pull/25
  - Add security-questionnaire.md for Accelerometer sensor
    https://github.com/w3c/accelerometer/pull/26
  - Define Accelerometer sensor type, clarify latest reading
    https://github.com/w3c/accelerometer/pull/24

* w3c/proximity (+4/-4/💬1)
  4 pull requests submitted:
  - Use getter operation for latest reading (by alexshalamov)
    https://github.com/w3c/proximity/pull/27
  - Align with Generic Sensor API current state (by NOtherDev)
    https://github.com/w3c/proximity/pull/26
  - Add security and privacy questionnaire for Proximity sensor (by alexshalamov)
    https://github.com/w3c/proximity/pull/25
  - Define 'Proximity Sensor' sensor type, clarify latest reading (by anssiko)
    https://github.com/w3c/proximity/pull/24

  1 pull requests received 1 new comments:
  - #26 Align with Generic Sensor API current state (1 by dontcallmedom)
    https://github.com/w3c/proximity/pull/26

  4 pull requests merged:
  - Add security and privacy questionnaire for Proximity sensor
    https://github.com/w3c/proximity/pull/25
  - Use getter operation for latest reading
    https://github.com/w3c/proximity/pull/27
  - Align with Generic Sensor API current state
    https://github.com/w3c/proximity/pull/26
  - Define 'Proximity Sensor' sensor type, clarify latest reading
    https://github.com/w3c/proximity/pull/24

* w3c/gyroscope (+4/-3/💬1)
  4 pull requests submitted:
  - Add security and privacy questionnaire (by alexshalamov)
    https://github.com/w3c/gyroscope/pull/23
  - Update attributes description (by pozdnyakov)
    https://github.com/w3c/gyroscope/pull/22
  - Define Gyroscope sensor type, clarify latest reading (by anssiko)
    https://github.com/w3c/gyroscope/pull/21
  - Define Gyroscope sensor type, clarify latest reading (by anssiko)
    https://github.com/w3c/gyroscope/pull/20

  1 pull requests received 1 new comments:
  - #20 Define Gyroscope sensor type, clarify latest reading (1 by anssiko)
    https://github.com/w3c/gyroscope/pull/20

  3 pull requests merged:
  - Add security and privacy questionnaire for Gyroscope sensor
    https://github.com/w3c/gyroscope/pull/23
  - Update attributes description
    https://github.com/w3c/gyroscope/pull/22
  - Define Gyroscope sensor type, clarify latest reading
    https://github.com/w3c/gyroscope/pull/21

* w3c/magnetometer (+3/-3/💬4)
  3 pull requests submitted:
  - Use value getter operation and use double as attribute type (by alexshalamov)
    https://github.com/w3c/magnetometer/pull/33
  - Add security and privacy questionnaire for Magnetometer (by alexshalamov)
    https://github.com/w3c/magnetometer/pull/32
  - Define Magnetometer sensor type, clarify latest reading (by anssiko)
    https://github.com/w3c/magnetometer/pull/31

  2 pull requests received 4 new comments:
  - #32 Add security and privacy questionnaire for Magnetometer (3 by alexshalamov)
    https://github.com/w3c/magnetometer/pull/32
  - #33 Use value getter operation and use double as attribute type (1 by alexshalamov)
    https://github.com/w3c/magnetometer/pull/33

  3 pull requests merged:
  - Use value getter operation and use double as attribute type
    https://github.com/w3c/magnetometer/pull/33
  - Add security and privacy questionnaire for Magnetometer
    https://github.com/w3c/magnetometer/pull/32
  - Define Magnetometer sensor type, clarify latest reading
    https://github.com/w3c/magnetometer/pull/31

* w3c/orientation-sensor (+3/-3/💬1)
  3 pull requests submitted:
  - Add  security and privacy questionnaire for Orientation Sensor (by alexshalamov)
    https://github.com/w3c/orientation-sensor/pull/47
  - Define Orientation Sensor sensor type, clarify latest reading (by anssiko)
    https://github.com/w3c/orientation-sensor/pull/46
  - Update attributes description (by pozdnyakov)
    https://github.com/w3c/orientation-sensor/pull/45

  1 pull requests received 1 new comments:
  - #45 Update attributes description (1 by kenchris)
    https://github.com/w3c/orientation-sensor/pull/45

  3 pull requests merged:
  - Add  security and privacy questionnaire for Orientation Sensor
    https://github.com/w3c/orientation-sensor/pull/47
  - Define Orientation Sensor sensor type, clarify latest reading
    https://github.com/w3c/orientation-sensor/pull/46
  - Update attributes description
    https://github.com/w3c/orientation-sensor/pull/45

* w3c/battery (+0/-0/💬8)
  1 pull requests received 8 new comments:
  - #13 Allow use in same-origin children (8 by mounirlamouri, dontcallmedom, anssiko, clelland)
    https://github.com/w3c/battery/pull/13

* w3c/dap-charter (+3/-3/💬4)
  3 pull requests submitted:
  - Remove Media Capture Task Force deliverables (by dontcallmedom)
    https://github.com/w3c/dap-charter/pull/38
  - Add finishing of DeviceOrientation as normative deliverable (by dontcallmedom)
    https://github.com/w3c/dap-charter/pull/37
  - Add a gelocation sensor deliverable (by dontcallmedom)
    https://github.com/w3c/dap-charter/pull/36

  3 pull requests received 4 new comments:
  - #38 Remove Media Capture Task Force deliverables (2 by dontcallmedom)
    https://github.com/w3c/dap-charter/pull/38
  - #36 Add a gelocation sensor deliverable (1 by anssiko)
    https://github.com/w3c/dap-charter/pull/36
  - #37 Add finishing of DeviceOrientation as normative deliverable (1 by anssiko)
    https://github.com/w3c/dap-charter/pull/37

  3 pull requests merged:
  - Remove Media Capture Task Force deliverables
    https://github.com/w3c/dap-charter/pull/38
  - Add a gelocation sensor deliverable
    https://github.com/w3c/dap-charter/pull/36
  - Add finishing of DeviceOrientation as normative deliverable
    https://github.com/w3c/dap-charter/pull/37


Repositories tracked by this digest:
-----------------------------------
* https://github.com/w3c/sensors
* https://github.com/w3c/ambient-light
* https://github.com/w3c/accelerometer
* https://github.com/w3c/proximity
* https://github.com/w3c/gyroscope
* https://github.com/w3c/magnetometer
* https://github.com/w3c/orientation-sensor
* https://github.com/w3c/motion-sensors
* https://github.com/w3c/battery
* https://github.com/w3c/wake-lock
* https://github.com/w3c/html-media-capture
* https://github.com/w3c/vibration
* https://github.com/w3c/dap-charter

Received on Tuesday, 26 September 2017 17:00:00 UTC