Devices and Sensors Working Group - Activity in 2015

TR publications

• 1 document published.

  • 8 December 2015

    Media Capture Depth Stream Extensions published as a Working Draft. History of Media Capture Depth Stream Extensions

GitHub

w3c/das-charter

• 1 pull request opened.

  • 11 December 2015

    Clarify that multi groups task forces can only do in scope work w3c/das-charter#26, by @dontcallmedom.

w3c/deviceorientation

• 1 issue opened.

  • 4 December 2015

    Add Security and Privacy Section w3c/deviceorientation#24, by @gmandyam.

• 1 issue received 1 new comment.

  • 4 December 2015

    Add Security and Privacy Section w3c/deviceorientation#24 (1 comment by @npdoty)

GitHub

w3c/sensors

• 1 issue opened.

  • 6 November 2015

    About securing sensors data w3c/sensors#71, by @vgalindo.

• 1 issue closed.

  • 12 November 2015

    Possibility to use "Readable Stream" as defined by the Streams API w3c/sensors#70.

• 5 issues received 12 new comments.

  • Latest comment 12 November 2015

    Possibility to use "Readable Stream" as defined by the Streams API w3c/sensors#70 (4 comments by @domenic, @tobie, @zolkis)

  • Latest comment 18 November 2015

    About securing sensors data w3c/sensors#71 (3 comments by @tobie, @vgalindo)

  • Latest comment 12 November 2015

    Sensors for continuously changing real valued properties w3c/sensors#68 (3 comments by @tobie, @zolkis)

  • 12 November 2015

    Addressing finger printing concerns for sensor APIs w3c/sensors#69 (1 comment by @tobie)

  • 4 November 2015

    Spec should allow user agents to reduce or disable sensor read for power saving purposes w3c/sensors#66 (1 comment by @riju)

w3c/das-charter

• 1 issue closed.

  • 16 November 2015

    joint working clause may be in wrong section w3c/das-charter#18.

• 2 issues received 2 new comments.

  • 2 November 2015

    unclear requirement for implementations w3c/das-charter#20 (1 comment by @dontcallmedom)

  • 2 November 2015

    grammar in Media Capture section w3c/das-charter#19 (1 comment by @dontcallmedom)
• 5 pull requests opened.

  • 12 November 2015

    Mention that work on acceleratomer/orientation is an alternative w3c/das-charter#25, by @dontcallmedom.

  • 2 November 2015

    Put note on joint work in a section of its own w3c/das-charter#24, by @dontcallmedom.

  • 2 November 2015

    Fix various typos noted by timeless w3c/das-charter#23, by @dontcallmedom.

  • 2 November 2015

    Adopt same commitment as Web Platform WG on horizontal reviews w3c/das-charter#22, by @dontcallmedom.

  • 2 November 2015

    Mark hardware security services as out of scope w3c/das-charter#21, by @dontcallmedom.

• 5 pull requests merged.

  • 16 November 2015

    Fix various typos noted by timeless w3c/das-charter#23.

  • 16 November 2015

    Mark hardware security services as out of scope w3c/das-charter#21.

  • 16 November 2015

    Adopt same commitment as Web Platform WG on horizontal reviews w3c/das-charter#22.

  • 16 November 2015

    Put note on joint work in a section of its own w3c/das-charter#24.

  • 16 November 2015

    Mention that work on acceleratomer/orientation is an alternative w3c/das-charter#25.

w3c/deviceorientation

• 1 pull request opened.

  • 12 November 2015

    bring the spec up to date w3c/deviceorientation#23, by @timvolodine.

• 1 pull request merged.

  • 13 November 2015

    bring the spec up to date w3c/deviceorientation#23.

• 1 pull request received 3 new comments.

  • Latest comment 13 November 2015

    bring the spec up to date w3c/deviceorientation#23 (3 comments by @richtr, @timvolodine)

w3c/screen-wake-lock

• 1 issue opened.

  • 3 November 2015

    shouldn't this be part of the permissions API? w3c/screen-wake-lock#59, by @jimmywarting.

TR publications

• 1 document published.

  • 15 October 2015

    Generic Sensor API published as a First Public Working Draft. History of Generic Sensor API

GitHub

w3c/sensors

• 5 issues opened.

  • 28 October 2015

    Possibility to use "Readable Stream" as defined by the Streams API w3c/sensors#70, by @ClaesNilsson.

  • 28 October 2015

    Addressing finger printing concerns for sensor APIs w3c/sensors#69, by @draggett.

  • 28 October 2015

    Sensors for continuously changing real valued properties w3c/sensors#68, by @draggett.

  • 28 October 2015

    Current draft links to tobie's github w3c/sensors#67, by @jyasskin.

  • 27 October 2015

    Spec should allow user agents to reduce or disable sensor read for power saving purposes w3c/sensors#66, by @markafoltz.

• 15 issues closed.

  • 30 October 2015

    Current draft links to tobie's github w3c/sensors#67.

  • 16 October 2015

    Add a threshold option w3c/sensors#25.

  • 16 October 2015

    Add a timeout property? w3c/sensors#44.

  • 16 October 2015

    Relation to REST APIs and W3C Web of Things activities w3c/sensors#18.

  • 16 October 2015

    Ability to lookup a cached SensorReading without polling the sensor w3c/sensors#47.

  • 16 October 2015

    Should sensor EventTarget be immediately available or should they be accessed through a promise? w3c/sensors#9.

  • 16 October 2015

    What precisely, do we mean by "generic"? w3c/sensors#10.

  • 16 October 2015

    When there are multiple sensors of a given type, how do we identify which one to instantiate? w3c/sensors#26.

  • 16 October 2015

    Does `SensorObserver` need a stop() method? w3c/sensors#48.

  • 16 October 2015

    Is a Promise-returning, "oneshot" method useful? w3c/sensors#49.

  • 16 October 2015

    Address questions around exposing high-level, low-level, and uncalibrated sensors w3c/sensors#51.

  • 6 October 2015

    Handle sensors with multiple values w3c/sensors#2.

  • 6 October 2015

    Should sensors require a privileged context? w3c/sensors#14.

  • 6 October 2015

    Agree on coarseness of frequency option w3c/sensors#6.

  • 3 October 2015

    Have a good feature detection story w3c/sensors#5.

• 11 issues received 14 new comments.

  • Latest comment 30 October 2015

    Current draft links to tobie's github w3c/sensors#67 (3 comments by @tabatkins, @tobie)

  • Latest comment 16 October 2015

    Relation to REST APIs and W3C Web of Things activities w3c/sensors#18 (2 comments by @tobie)

  • 30 October 2015

    Possibility to use "Readable Stream" as defined by the Streams API w3c/sensors#70 (1 comment by @tobie)

  • 27 October 2015

    Provide a way of tying sensor requests to animation frames w3c/sensors#4 (1 comment by @markafoltz)

  • 16 October 2015

    Add a threshold option w3c/sensors#25 (1 comment by @tobie)

  • 16 October 2015

    Ability to lookup a cached SensorReading without polling the sensor w3c/sensors#47 (1 comment by @tobie)

  • 16 October 2015

    Should sensor EventTarget be immediately available or should they be accessed through a promise? w3c/sensors#9 (1 comment by @tobie)

  • 16 October 2015

    When there are multiple sensors of a given type, how do we identify which one to instantiate? w3c/sensors#26 (1 comment by @tobie)

  • 16 October 2015

    Does `SensorObserver` need a stop() method? w3c/sensors#48 (1 comment by @tobie)

  • 16 October 2015

    Is a Promise-returning, "oneshot" method useful? w3c/sensors#49 (1 comment by @tobie)

  • 16 October 2015

    Address questions around exposing high-level, low-level, and uncalibrated sensors w3c/sensors#51 (1 comment by @tobie)

w3c/das-charter

• 3 issues opened.

  • 16 October 2015

    unclear requirement for implementations w3c/das-charter#20, by @mwichmann.

  • 15 October 2015

    grammar in Media Capture section w3c/das-charter#19, by @mwichmann.

  • 15 October 2015

    joint working clause may be in wrong section w3c/das-charter#18, by @mwichmann.

• 11 issues closed.

  • 13 October 2015

    Needs updated milestones w3c/das-charter#3.

  • 13 October 2015

    Needs updated dependency list w3c/das-charter#1.

  • 13 October 2015

    Add usual asynchronous decision making paragraph to decisions w3c/das-charter#11.

  • 13 October 2015

    Extensible charter? w3c/das-charter#5.

  • 13 October 2015

    is Web Bluetooth something DAP can/should adopt? w3c/das-charter#6.

  • 13 October 2015

    Trim list of deliverables w3c/das-charter#9.

  • 13 October 2015

    Any reason to keep app launcher / Web intent? w3c/das-charter#8.

  • 13 October 2015

    Do we want to work on PIM APIs again? w3c/das-charter#2.

  • 13 October 2015

    Do we need to to say explicitly we will maintain the Vibration API? w3c/das-charter#7.

  • 13 October 2015

    Add links to existing drafts w3c/das-charter#10.

  • 13 October 2015

    links to previous charters are broken - 404 w3c/das-charter#15.

• 3 issues received 3 new comments.

  • 13 October 2015

    Needs updated dependency list w3c/das-charter#1 (1 comment by @dontcallmedom)

  • 13 October 2015

    is Web Bluetooth something DAP can/should adopt? w3c/das-charter#6 (1 comment by @dontcallmedom)

  • 13 October 2015

    Trim list of deliverables w3c/das-charter#9 (1 comment by @dontcallmedom)
• 2 pull requests opened.

  • 7 October 2015

    Fix a typo w3c/das-charter#17, by @anssiko.

  • 6 October 2015

    Add a note on moving media capture to Timed Media WG w3c/das-charter#16, by @dontcallmedom.

• 5 pull requests merged.

  • 13 October 2015

    Use new document license w3c/das-charter#13.

  • 13 October 2015

    Include text to simplify addition of new deliverables w3c/das-charter#14.

  • 7 October 2015

    Add a note on moving media capture to Timed Media WG w3c/das-charter#16.

  • 7 October 2015

    Fix a typo w3c/das-charter#17.

  • 5 October 2015

    Add deviceorientation-like spec to list of deliverables w3c/das-charter#12.

w3c/deviceorientation

• 1 issue received 1 new comment.

  • 1 October 2015

    Specify the onfoo event listener attributes in Web IDL w3c/deviceorientation#17 (1 comment by @foolip)

TR publications

• 4 documents published.

  • 8 September 2015

    MediaStream Recording published as a Working Draft. History of MediaStream Recording

  • 4 September 2015

    Wake Lock API published as a Working Draft. History of Wake Lock API

  • 3 September 2015

    Ambient Light Events published as a Working Draft. History of Ambient Light Events

  • 3 September 2015

    Proximity Events published as a Working Draft. History of Proximity Events

Participants

• 1 participant joined.

  • 1 September 2015

    Lukasz Olejnik (W3C Invited Experts) joined.

• 1 organization joined.

  • 28 September 2015

    Plantronics, Inc. joined.

GitHub

w3c/screen-wake-lock

• 1 issue received 5 new comments.

  • Latest comment 29 September 2015

    Why Document instead of Window? w3c/screen-wake-lock#52 (5 comments by @dontcallmedom, @foolip, @marcoscaceres)
• 1 pull request opened.

  • 4 September 2015

    Adapt to use data-lt instead of title for definitions w3c/screen-wake-lock#58, by @dontcallmedom.

• 1 pull request received 1 new comment.

  • 5 September 2015

    Set up for automatic publishing to TR w3c/screen-wake-lock#46 (1 comment by @tripu)

w3c/deviceorientation

• 2 issues received 8 new comments.

  • Latest comment 23 September 2015

    Absolute-only DeviceOrientationEvents are bad for head tracking in VR w3c/deviceorientation#21 (7 comments by @borismus, @notthetup, @RByers, @tobie)

  • 26 September 2015

    Security considerations w3c/deviceorientation#13 (1 comment by @maryammjd)
• 1 pull request opened.

  • 16 September 2015

    Adding absolutedeviceorientation w3c/deviceorientation#22, by @borismus.

• 1 pull request merged.

  • 25 September 2015

    Adding absolutedeviceorientation w3c/deviceorientation#22.

• 1 pull request received 8 new comments.

  • Latest comment 25 September 2015

    Adding absolutedeviceorientation w3c/deviceorientation#22 (8 comments by @borismus, @timvolodine)

w3c/sensors

• 1 issue opened.

  • 4 September 2015

    Sensor.frequency needs to be setable to allow frequency adaptation w3c/sensors#63, by @tobie.

• 2 issues closed.

  • 26 September 2015

    Add a definitions section to the spec w3c/sensors#52.

  • 23 September 2015

    Dependency on [DOM] due to inheriting from EventTarget w3c/sensors#21.

• 3 issues received 8 new comments.

  • Latest comment 8 September 2015

    Retrofit existing sensor APIs w3c/sensors#1 (3 comments by @ghost, @tobie)

  • Latest comment 8 September 2015

    Sensor.frequency needs to be setable to allow frequency adaptation w3c/sensors#63 (3 comments by @anssiko, @rwaldron, @tobie)

  • Latest comment 3 September 2015

    Should unit option's behavior be defined in the Generic Sensor API? w3c/sensors#62 (2 comments by @anssiko, @rwaldron)
• 2 pull requests opened.

  • 18 September 2015

    Uc update w3c/sensors#65, by @tobie.

  • 17 September 2015

    Usecase update w3c/sensors#64, by @tobie.

• 3 pull requests merged.

  • 23 September 2015

    Updated proposal for Sensor API w3c/sensors#46.

  • 18 September 2015

    Uc update w3c/sensors#65.

  • 17 September 2015

    Usecase update w3c/sensors#64.

• 1 pull request received 1 new comment.

  • 23 September 2015

    Updated proposal for Sensor API w3c/sensors#46 (1 comment by @tobie)

w3c/proximity

• 1 pull request opened.

  • 23 September 2015

    Contiguous IDL w3c/proximity#1, by @anssiko.

• 1 pull request merged.

  • 23 September 2015

    Contiguous IDL w3c/proximity#1.

w3c/ambient-light

• 1 pull request opened.

  • 23 September 2015

    Contiguous IDL w3c/ambient-light#2, by @anssiko.

• 1 pull request merged.

  • 23 September 2015

    Contiguous IDL w3c/ambient-light#2.

w3c/das-charter

• 1 issue opened.

  • 3 September 2015

    links to previous charters are broken - 404 w3c/das-charter#15, by @fhirsch.

• 1 issue received 1 new comment.

  • 3 September 2015

    Any new sensor API? w3c/das-charter#4 (1 comment by @dontcallmedom)

Participants

• 1 participant joined.

  • 25 August 2015

    Josh Soref (W3C Invited Experts) joined.

• 1 organization joined.

  • 22 August 2015

    Viacom inc. joined.

GitHub

w3c/sensors

• 1 issue opened.

  • 31 August 2015

    Should unit option's behavior be defined in the Generic Sensor API? w3c/sensors#62, by @tobie.

• 7 pull requests opened.

  • 28 August 2015

    Add a refresh button to realtime-positioning example. w3c/sensors#61, by @tobie.

  • 27 August 2015

    Add polyfill + example code to realtime positioning use case. w3c/sensors#60, by @tobie.

  • 27 August 2015

    Add example code for second use case w3c/sensors#59, by @tobie.

  • 26 August 2015

    Initial use case doc. w3c/sensors#58, by @tobie.

  • 26 August 2015

    Further refactoring of geo positioning example. w3c/sensors#57, by @tobie.

  • 26 August 2015

    Refactor example code. w3c/sensors#56, by @tobie.

  • 26 August 2015

    Add realtime positioning example using existing Geoloc. w3c/sensors#55, by @tobie.

• 7 pull requests merged.

  • 28 August 2015

    Add a refresh button to realtime-positioning example. w3c/sensors#61.

  • 27 August 2015

    Add polyfill + example code to realtime positioning use case. w3c/sensors#60.

  • 27 August 2015

    Add example code for second use case w3c/sensors#59.

  • 26 August 2015

    Initial use case doc. w3c/sensors#58.

  • 26 August 2015

    Further refactoring of geo positioning example. w3c/sensors#57.

  • 26 August 2015

    Refactor example code. w3c/sensors#56.

  • 26 August 2015

    Add realtime positioning example using existing Geoloc. w3c/sensors#55.

• 1 pull request closed.

  • 11 August 2015

    Title and Rec track status w3c/sensors#54.

• 1 pull request received 3 new comments.

  • Latest comment 11 August 2015

    Title and Rec track status w3c/sensors#54 (3 comments by @dontcallmedom, @tobie)

w3c/deviceorientation

• 2 issues opened.

  • 13 August 2015

    Absolute-only DeviceOrientationEvents are bad for head tracking in VR w3c/deviceorientation#21, by @borismus.

  • 12 August 2015

    Spec should include a link for where issues are tracked w3c/deviceorientation#20, by @RByers.

• 2 issues received 2 new comments.

  • 13 August 2015

    webkitCompassHeading / webkitCompassAccuracy w3c/deviceorientation#6 (1 comment by @RByers)

  • 13 August 2015

    Absolute-only DeviceOrientationEvents are bad for head tracking in VR w3c/deviceorientation#21 (1 comment by @RByers)

TR publications

• 1 document published.

  • 14 July 2015

    Permissions for Device API Access published as a Note. History of Permissions for Device API Access

Participants

• 1 organization joined.

  • 14 July 2015

    Alibaba Group joined.

• 1 organization left.

  • 2 July 2015

    MStar Semiconductor, Inc. left.

GitHub

w3c/screen-wake-lock

• 3 issues opened.

  • 15 July 2015

    Spec needs to be explicit about resetting release timer on lock release w3c/screen-wake-lock#57, by @marcoscaceres.

  • 14 July 2015

    Book reader usecase not well supported w3c/screen-wake-lock#56, by @sicking.

  • 14 July 2015

    Current API not friendly to components w3c/screen-wake-lock#55, by @sicking.

• 3 issues received 8 new comments.

  • Latest comment 14 July 2015

    System lock should be specified w3c/screen-wake-lock#50 (3 comments by @marcoscaceres, @sicking, @stuartpb)

  • Latest comment 10 July 2015

    Why Document instead of Window? w3c/screen-wake-lock#52 (3 comments by @andrey-logvinov, @stuartpb)

  • Latest comment 16 July 2015

    Current API not friendly to components w3c/screen-wake-lock#55 (2 comments by @annevk, @marcoscaceres)
• 1 pull request opened.

  • 3 July 2015

    Move request flag to Screen interface w3c/screen-wake-lock#54, by @andrey-logvinov.

• 1 pull request merged.

  • 9 July 2015

    Move request flag to Screen interface w3c/screen-wake-lock#54.

• 1 pull request received 1 new comment.

  • 9 July 2015

    Move request flag to Screen interface w3c/screen-wake-lock#54 (1 comment by @boiler23)

w3c/deviceorientation

• 5 issues opened.

  • 15 July 2015

    Add DeviceAcceleration and DeviceRotationRate constructors? w3c/deviceorientation#19, by @foolip.

  • 15 July 2015

    Specify the init*Event() methods? w3c/deviceorientation#18, by @foolip.

  • 15 July 2015

    Specify the onfoo event listener attributes in Web IDL w3c/deviceorientation#17, by @foolip.

  • 15 July 2015

    Spec URL is ugly w3c/deviceorientation#16, by @foolip.

  • 10 July 2015

    Set controls target? w3c/deviceorientation#15, by @anagpuyol.

• 1 issue closed.

  • 10 July 2015

    Set controls target? w3c/deviceorientation#15.

• 2 issues received 2 new comments.

  • 15 July 2015

    [Callback] extended attributes w3c/deviceorientation#9 (1 comment by @foolip)

  • 10 July 2015

    Set controls target? w3c/deviceorientation#15 (1 comment by @richtr)

w3c/sensors

• 1 pull request opened.

  • 8 July 2015

    Title and Rec track status w3c/sensors#54, by @dontcallmedom.

w3c/das-charter

• 1 issue opened.

  • 2 July 2015

    Add usual asynchronous decision making paragraph to decisions w3c/das-charter#11, by @wayneca.

• 2 issues received 6 new comments.

  • Latest comment 8 July 2015

    Any new sensor API? w3c/das-charter#4 (3 comments by @anssiko, @dontcallmedom, @wayneca)

  • Latest comment 8 July 2015

    Extensible charter? w3c/das-charter#5 (3 comments by @dontcallmedom, @wayneca)
• 3 pull requests opened.

  • 8 July 2015

    Include text to simplify addition of new deliverables w3c/das-charter#14, by @dontcallmedom.

  • 7 July 2015

    Use new document license w3c/das-charter#13, by @dontcallmedom.

  • 7 July 2015

    Add deviceorientation-like spec to list of deliverables w3c/das-charter#12, by @dontcallmedom.

Participants

• 1 participant left.

  • 3 June 2015

    Tobie Langel (W3C Invited Experts) left.

GitHub

w3c/das-charter

• 10 issues opened.

  • 18 June 2015

    Add links to existing drafts w3c/das-charter#10, by @dontcallmedom.

  • 18 June 2015

    Trim list of deliverables w3c/das-charter#9, by @dontcallmedom.

  • 18 June 2015

    Any reason to keep app launcher / Web intent? w3c/das-charter#8, by @dontcallmedom.

  • 18 June 2015

    Do we need to to say explicitly we will maintain the Vibration API? w3c/das-charter#7, by @dontcallmedom.

  • 18 June 2015

    is Web Bluetooth something DAP can/should adopt? w3c/das-charter#6, by @dontcallmedom.

  • 18 June 2015

    Extensible charter? w3c/das-charter#5, by @dontcallmedom.

  • 18 June 2015

    Any new sensor API? w3c/das-charter#4, by @dontcallmedom.

  • 18 June 2015

    Needs updated milestones w3c/das-charter#3, by @dontcallmedom.

  • 18 June 2015

    Do we want to work on PIM APIs again? w3c/das-charter#2, by @dontcallmedom.

  • 18 June 2015

    Needs updated dependency list w3c/das-charter#1, by @dontcallmedom.

• 2 issues received 3 new comments.

  • Latest comment 30 June 2015

    Extensible charter? w3c/das-charter#5 (2 comments by @dontcallmedom, @wayneca)

  • 24 June 2015

    is Web Bluetooth something DAP can/should adopt? w3c/das-charter#6 (1 comment by @carybran)

w3c/sensors

• 19 issues opened.

  • 18 June 2015

    Add a section on how sensors are implemented w3c/sensors#53, by @tobie.

  • 18 June 2015

    Add a definitions section to the spec w3c/sensors#52, by @tobie.

  • 16 June 2015

    Address questions around exposing high-level, low-level, and uncalibrated sensors w3c/sensors#51, by @tobie.

  • 11 June 2015

    Is a Promise-returning, "oneshot" method useful? w3c/sensors#49, by @tobie.

  • 11 June 2015

    Does `SensorObserver` need a stop() method? w3c/sensors#48, by @tobie.

  • 11 June 2015

    Ability to lookup a cached SensorReading without polling the sensor w3c/sensors#47, by @tobie.

  • 11 June 2015

    Add a timeout property? w3c/sensors#44, by @tobie.

  • 11 June 2015

    Add high resolution monotonic timestamps to SensorReadings w3c/sensors#43, by @tobie.

  • 10 June 2015

    API must allow Web devs to easily create fused sensors in JS with an API consistant with native sensors w3c/sensors#42, by @tobie.

  • 10 June 2015

    Make APIs forward-compatible with ES modules w3c/sensors#39, by @tobie.

  • 9 June 2015

    [TreatNonObjectAsNull] not required? w3c/sensors#34, by @riju.

  • 8 June 2015

    frequency is a float? w3c/sensors#33, by @rwaldron.

  • 8 June 2015

    getAll()? w3c/sensors#32, by @rwaldron.

  • 8 June 2015

    SensorIdentifier is bizarre w3c/sensors#30, by @domenic.

  • 8 June 2015

    Do we need a lightweight interface representing available sensors? w3c/sensors#28, by @tobie.

  • 5 June 2015

    When there are multiple sensors of a given type, how do we identify which one to instantiate? w3c/sensors#26, by @tobie.

  • 5 June 2015

    Add a threshold option w3c/sensors#25, by @tobie.

  • 5 June 2015

    Identify the lower level primitives that do the actual sensor polling. w3c/sensors#24, by @tobie.

  • 3 June 2015

    What if requested polling frequency is > time it takes to read data out of the sensor? w3c/sensors#23, by @tobie.

• 3 issues closed.

  • 9 June 2015

    frequency is a float? w3c/sensors#33.

  • 9 June 2015

    [TreatNonObjectAsNull] not required? w3c/sensors#34.

  • 8 June 2015

    SensorIdentifier is bizarre w3c/sensors#30.

• 15 issues received 102 new comments.

  • Latest comment 17 June 2015

    Dependency on [DOM] due to inheriting from EventTarget w3c/sensors#21 (43 comments by @domenic, @gmandyam, @jhusain, @kriskowal, @marcoscaceres, @mattpodwysocki, @rwaldron, @tobie, @zenparsing)

  • Latest comment 11 June 2015

    Simplify extension of the Permissions API for concrete sensor implementations w3c/sensors#22 (10 comments by @domenic, @marcoscaceres, @tobie)

  • Latest comment 8 June 2015

    When there are multiple sensors of a given type, how do we identify which one to instantiate? w3c/sensors#26 (9 comments by @davidmarkclements, @pablochacin, @rwaldron, @tobie)

  • Latest comment 17 June 2015

    Address questions around exposing high-level, low-level, and uncalibrated sensors w3c/sensors#51 (8 comments by @pablochacin, @rwaldron, @tobie)

  • Latest comment 12 June 2015

    Do we need a lightweight interface representing available sensors? w3c/sensors#28 (7 comments by @domenic, @tobie)

  • Latest comment 11 June 2015

    API must allow Web devs to easily create fused sensors in JS with an API consistant with native sensors w3c/sensors#42 (6 comments by @gmandyam, @robman, @tobie)

  • Latest comment 9 June 2015

    getAll()? w3c/sensors#32 (4 comments by @domenic, @rwaldron, @tobie)

  • Latest comment 3 June 2015

    "wakeup" parameter w3c/sensors#15 (3 comments by @domenic, @rwaldron, @tobie)

  • Latest comment 11 June 2015

    Is a Promise-returning, "oneshot" method useful? w3c/sensors#49 (2 comments by @rwaldron, @tobie)

  • Latest comment 9 June 2015

    [TreatNonObjectAsNull] not required? w3c/sensors#34 (2 comments by @riju, @tobie)

  • Latest comment 8 June 2015

    SensorIdentifier is bizarre w3c/sensors#30 (2 comments by @domenic, @tobie)

  • Latest comment 6 June 2015

    Identify the lower level primitives that do the actual sensor polling. w3c/sensors#24 (2 comments by @domenic, @rwaldron)

  • Latest comment 3 June 2015

    What if requested polling frequency is > time it takes to read data out of the sensor? w3c/sensors#23 (2 comments by @domenic)

  • 11 June 2015

    Provide a way of tying sensor requests to animation frames w3c/sensors#4 (1 comment by @anssiko)

  • 5 June 2015

    Add a threshold option w3c/sensors#25 (1 comment by @domenic)
• 12 pull requests opened.

  • 12 June 2015

    Update README and move API sketch to its own file. w3c/sensors#50, by @tobie.

  • 11 June 2015

    Updated proposal for Sensor API w3c/sensors#46, by @tobie.

  • 11 June 2015

    Remove contributors now that respec pulls them directly from GH. w3c/sensors#45, by @tobie.

  • 10 June 2015

    fixing typos w3c/sensors#41, by @dret.

  • 10 June 2015

    Credit where credit is due. w3c/sensors#40, by @tobie.

  • 10 June 2015

    Adding more links to elsewhere.md w3c/sensors#38, by @tobie.

  • 9 June 2015

    Use double WebIDL type instead of float. w3c/sensors#37, by @tobie.

  • 9 June 2015

    Remove redundant [TreatNonObjectAsNull] extended attributed. w3c/sensors#36, by @tobie.

  • 9 June 2015

    Use <dfn> tag for "read from the sensor" w3c/sensors#35, by @AFBarstow.

  • 8 June 2015

    Use DOMString as a sensor identifier. Closes #30. w3c/sensors#31, by @tobie.

  • 8 June 2015

    1st ED w3c/sensors#29, by @tobie.

  • 6 June 2015

    Fix mixed-content problem with URL to respec w3c/sensors#27, by @sideshowbarker.

• 10 pull requests merged.

  • 12 June 2015

    Update README and move API sketch to its own file. w3c/sensors#50.

  • 11 June 2015

    Remove contributors now that respec pulls them directly from GH. w3c/sensors#45.

  • 11 June 2015

    fixing typos w3c/sensors#41.

  • 10 June 2015

    Credit where credit is due. w3c/sensors#40.

  • 10 June 2015

    Adding more links to elsewhere.md w3c/sensors#38.

  • 9 June 2015

    Use double WebIDL type instead of float. w3c/sensors#37.

  • 9 June 2015

    Remove redundant [TreatNonObjectAsNull] extended attributed. w3c/sensors#36.

  • 8 June 2015

    Use DOMString as a sensor identifier. Closes #30. w3c/sensors#31.

  • 8 June 2015

    1st ED w3c/sensors#29.

  • 6 June 2015

    Fix mixed-content problem with URL to respec w3c/sensors#27.

• 1 pull request closed.

  • 10 June 2015

    Use <dfn> tag for "read from the sensor" w3c/sensors#35.

• 5 pull requests received 23 new comments.

  • Latest comment 11 June 2015

    Updated proposal for Sensor API w3c/sensors#46 (18 comments by @marcoscaceres, @tobie)

  • Latest comment 10 June 2015

    Use <dfn> tag for "read from the sensor" w3c/sensors#35 (2 comments by @marcoscaceres, @tobie)

  • 11 June 2015

    fixing typos w3c/sensors#41 (1 comment by @tobie)

  • 9 June 2015

    Use double WebIDL type instead of float. w3c/sensors#37 (1 comment by @rwaldron)

  • 6 June 2015

    Fix mixed-content problem with URL to respec w3c/sensors#27 (1 comment by @tobie)

w3c/deviceorientation

• 1 issue received 1 new comment.

  • 2 June 2015

    Add way of getting current orientation w3c/deviceorientation#11 (1 comment by @hexalys)

Participants

• 2 organizations left.

  • 19 May 2015

    ERICSSON left.

  • 16 May 2015

    UCWEB left.

GitHub

w3c/sensors

• 7 issues opened.

  • 28 May 2015

    Simplify extension of the Permissions API for concrete sensor implementations w3c/sensors#22, by @tobie.

  • 28 May 2015

    Dependency on [DOM] due to inheriting from EventTarget w3c/sensors#21, by @tobie.

  • 27 May 2015

    Allow for async permission request when first accessing sensor data w3c/sensors#20, by @tobie.

  • 18 May 2015

    No way to express an abstract constructor in WebIDL w3c/sensors#19, by @tobie.

  • 15 May 2015

    Relation to REST APIs and W3C Web of Things activities w3c/sensors#18, by @ClaesNilsson.

  • 11 May 2015

    "wakeup" parameter w3c/sensors#15, by @rwaldron.

  • 7 May 2015

    Should sensors require a privileged context? w3c/sensors#14, by @anssiko.

• 15 issues received 68 new comments.

  • Latest comment 28 May 2015

    Relation to REST APIs and W3C Web of Things activities w3c/sensors#18 (20 comments by @anssiko, @ClaesNilsson, @draggett, @h0ru5, @mwichmann, @rwaldron, @tobie)

  • Latest comment 31 May 2015

    Dependency on [DOM] due to inheriting from EventTarget w3c/sensors#21 (10 comments by @domenic, @kriskowal, @smaug----, @tobie)

  • Latest comment 9 May 2015

    Allowing data batching when poll frequency < sensor frequency w3c/sensors#13 (7 comments by @rwaldron, @tobie)

  • Latest comment 8 May 2015

    What precisely, do we mean by "generic"? w3c/sensors#10 (5 comments by @anssiko, @fhirsch, @mwichmann, @tobie)

  • Latest comment 28 May 2015

    Allow for async permission request when first accessing sensor data w3c/sensors#20 (4 comments by @marcoscaceres, @rwaldron, @tobie)

  • Latest comment 18 May 2015

    No way to express an abstract constructor in WebIDL w3c/sensors#19 (4 comments by @domenic, @rwaldron, @tobie)

  • Latest comment 10 May 2015

    Agree on coarseness of frequency option w3c/sensors#6 (4 comments by @rwaldron, @tobie)

  • Latest comment 9 May 2015

    Should sensors be singleton? w3c/sensors#8 (4 comments by @capnmidnight, @rwaldron, @tobie)

  • Latest comment 10 May 2015

    Have a good feature detection story w3c/sensors#5 (2 comments by @tobie)

  • Latest comment 10 May 2015

    Should sensor EventTarget be immediately available or should they be accessed through a promise? w3c/sensors#9 (2 comments by @tobie)

  • Latest comment 8 May 2015

    Handle sensors with multiple values w3c/sensors#2 (2 comments by @rwaldron, @tobie)

  • 28 May 2015

    Simplify extension of the Permissions API for concrete sensor implementations w3c/sensors#22 (1 comment by @tobie)

  • 10 May 2015

    Provide a way of tying sensor requests to animation frames w3c/sensors#4 (1 comment by @tobie)

  • 10 May 2015

    Sensor discovery w3c/sensors#7 (1 comment by @tobie)

  • 7 May 2015

    Should sensors require a privileged context? w3c/sensors#14 (1 comment by @tobie)
• 2 pull requests opened.

  • 12 May 2015

    Add spec index page with basic info. w3c/sensors#17, by @tobie.

  • 11 May 2015

    Remove the promise-based static requestValue() method w3c/sensors#16, by @tobie.

• 2 pull requests merged.

  • 15 May 2015

    Add spec index page with basic info. w3c/sensors#17.

  • 11 May 2015

    Remove the promise-based static requestValue() method w3c/sensors#16.

• 2 pull requests received 9 new comments.

  • Latest comment 13 May 2015

    Add spec index page with basic info. w3c/sensors#17 (8 comments by @anssiko, @domenic, @richtr, @tobie)

  • 11 May 2015

    Remove the promise-based static requestValue() method w3c/sensors#16 (1 comment by @rwaldron)

w3c/screen-wake-lock

• 2 issues opened.

  • 22 May 2015

    Why Document instead of Window? w3c/screen-wake-lock#52, by @domenic.

  • 5 May 2015

    iframes keeping screen awake w3c/screen-wake-lock#51, by @mounirlamouri.

• 5 issues closed.

  • 28 May 2015

    Delegate wake lock relevance to Page Visibility API w3c/screen-wake-lock#48.

  • 5 May 2015

    Use asynchronous lock acquisition w3c/screen-wake-lock#47.

  • 5 May 2015

    Do we really need a way to get actual wake lock status? w3c/screen-wake-lock#43.

  • 5 May 2015

    Racy promises need to be dealt with... w3c/screen-wake-lock#26.

  • 5 May 2015

    wakeLock.isHeld() should probably be asynchronous? w3c/screen-wake-lock#28.

• 8 issues received 17 new comments.

  • Latest comment 28 May 2015

    Why Document instead of Window? w3c/screen-wake-lock#52 (10 comments by @andrey-logvinov, @dglazkov, @domenic, @esprehn, @foolip, @mounirlamouri)

  • 28 May 2015

    Delegate wake lock relevance to Page Visibility API w3c/screen-wake-lock#48 (1 comment by @andrey-logvinov)

  • 19 May 2015

    System lock should be specified w3c/screen-wake-lock#50 (1 comment by @marcoscaceres)

  • 5 May 2015

    iframes keeping screen awake w3c/screen-wake-lock#51 (1 comment by @mikewest)

  • 5 May 2015

    wakeLock.isHeld() should probably be asynchronous? w3c/screen-wake-lock#28 (1 comment by @mounirlamouri)

  • 5 May 2015

    Racy promises need to be dealt with... w3c/screen-wake-lock#26 (1 comment by @mounirlamouri)

  • 5 May 2015

    Do we really need a way to get actual wake lock status? w3c/screen-wake-lock#43 (1 comment by @mounirlamouri)

  • 5 May 2015

    Use asynchronous lock acquisition w3c/screen-wake-lock#47 (1 comment by @mounirlamouri)
• 1 pull request opened.

  • 28 May 2015

    Fix typo "undrelying" w3c/screen-wake-lock#53, by @foolip.

• 2 pull requests merged.

  • 29 May 2015

    Fix typo "undrelying" w3c/screen-wake-lock#53.

  • 28 May 2015

    Delegate lock relevance to Page Visibility API w3c/screen-wake-lock#49.

• 2 pull requests received 2 new comments.

  • 29 May 2015

    Fix typo "undrelying" w3c/screen-wake-lock#53 (1 comment by @boiler23)

  • 28 May 2015

    Delegate lock relevance to Page Visibility API w3c/screen-wake-lock#49 (1 comment by @boiler23)

TR publications

• 1 document published.

  • 14 April 2015

    Media Capture and Streams published as a Last Call Working Draft. History of Media Capture and Streams

Participants

• 1 organization left.

  • 25 April 2015

    Shenzhen Coolpad Technologies Co., Ltd. left.

GitHub

w3c/screen-wake-lock

• 1 issue opened.

  • 2 April 2015

    System lock should be specified w3c/screen-wake-lock#50, by @stuartpb.

• 1 issue received 4 new comments.

  • Latest comment 23 April 2015

    Use asynchronous lock acquisition w3c/screen-wake-lock#47 (4 comments by @andrey-logvinov, @marcoscaceres, @mounirlamouri)

w3c/geolocation

• 1 issue closed.

  • 1 April 2015

    Missing README w3c/geolocation#3.

• 2 issues received 3 new comments.

  • Latest comment 1 April 2015

    Multiple specs per repo is problematic. w3c/geolocation#7 (2 comments by @ashimura, @darobin)

  • 1 April 2015

    Missing README w3c/geolocation#3 (1 comment by @ashimura)

GitHub

w3c/geolocation

• 3 issues opened.

  • 25 March 2015

    Multiple specs per repo is problematic. w3c/geolocation#7, by @marcoscaceres.

  • 25 March 2015

    Add CONTRIBUTING file w3c/geolocation#5, by @marcoscaceres.

  • 25 March 2015

    Missing README w3c/geolocation#3, by @marcoscaceres.

• 1 issue received 14 new comments.

  • Latest comment 31 March 2015

    Multiple specs per repo is problematic. w3c/geolocation#7 (14 comments by @ashimura, @darobin, @gmandyam, @marcoscaceres, @mkruisselbrink)
• 3 pull requests opened.

  • 25 March 2015

    Create contributing.md (closes #4) w3c/geolocation#6, by @marcoscaceres.

  • 25 March 2015

    Added README (closes #3) w3c/geolocation#4, by @marcoscaceres.

  • 18 March 2015

    Modernized the examples a bit.. w3c/geolocation#2, by @marcoscaceres.

• 1 pull request merged.

  • 19 March 2015

    Modernized the examples a bit.. w3c/geolocation#2.

• 1 pull request received 5 new comments.

  • Latest comment 25 March 2015

    Modernized the examples a bit.. w3c/geolocation#2 (5 comments by @marcoscaceres, @mkruisselbrink)

w3c/deviceorientation

• 1 issue received 1 new comment.

  • 24 March 2015

    Security considerations w3c/deviceorientation#13 (1 comment by @richtr)

w3c/screen-wake-lock

• 1 issue opened.

  • 23 March 2015

    Delegate wake lock relevance to Page Visibility API w3c/screen-wake-lock#48, by @andrey-logvinov.

• 1 pull request opened.

  • 23 March 2015

    Delegate lock relevance to Page Visibility API w3c/screen-wake-lock#49, by @andrey-logvinov.

TR publications

• 6 documents published.

  • 10 February 2015

    Vibration API published as a Recommendation. History of Vibration API

  • 12 February 2015

    Media Capture and Streams published as a Working Draft. History of Media Capture and Streams

  • 19 February 2015

    Media Capture from DOM Elements published as a First Public Working Draft. History of Media Capture from DOM Elements

  • 12 February 2015

    Wake Lock API published as a First Public Working Draft. History of Wake Lock API

  • 10 February 2015

    Audio Output Devices API published as a First Public Working Draft. History of Audio Output Devices API

  • 10 February 2015

    Screen Capture published as a First Public Working Draft. History of Screen Capture

GitHub

w3c/deviceorientation

• 1 issue opened.

  • 27 February 2015

    DeviceMotionEventInit interface members w3c/deviceorientation#14, by @jensl.

w3c/screen-wake-lock

• 1 issue opened.

  • 13 February 2015

    Use asynchronous lock acquisition w3c/screen-wake-lock#47, by @owencm.

• 1 issue received 1 new comment.

  • 13 February 2015

    Use asynchronous lock acquisition w3c/screen-wake-lock#47 (1 comment by @andrey-logvinov)
• 3 pull requests opened.

  • 13 February 2015

    Set up for automatic publishing to TR w3c/screen-wake-lock#46, by @dontcallmedom.

  • 5 February 2015

    Changed status to FPWD w3c/screen-wake-lock#45, by @andrey-logvinov.

  • 2 February 2015

    fix reference to use cases w3c/screen-wake-lock#44, by @dontcallmedom.

• 3 pull requests merged.

  • 13 February 2015

    Set up for automatic publishing to TR w3c/screen-wake-lock#46.

  • 5 February 2015

    Changed status to FPWD w3c/screen-wake-lock#45.

  • 3 February 2015

    fix reference to use cases w3c/screen-wake-lock#44.

w3c/ambient-light

• 1 pull request opened.

  • 3 February 2015

    Fix [MEDIAQUERIES4] reference URL. w3c/ambient-light#1, by @anssiko.

• 1 pull request merged.

  • 3 February 2015

    Fix [MEDIAQUERIES4] reference URL. w3c/ambient-light#1.

TR publications

• 3 documents published.

  • 29 January 2015

    Media Capture Depth Stream Extensions published as a Working Draft. History of Media Capture Depth Stream Extensions

  • 27 January 2015

    MediaStream Recording published as a Working Draft. History of MediaStream Recording

  • 27 January 2015

    Mediastream Image Capture published as a Working Draft. History of Mediastream Image Capture

Participants

• 1 participant joined.

  • 20 January 2015

    Frederick Hirsch (W3C Invited Experts) joined.

GitHub

w3c/screen-wake-lock

• 1 issue received 2 new comments.

  • Latest comment 8 January 2015

    Do we really need a way to get actual wake lock status? w3c/screen-wake-lock#43 (2 comments by @domenic, @marcoscaceres)