Devices and Sensors WG - 2021 Q2 virtual meeting

[anssiko]

Devices and Sensors WG - 2021 Q2 virtual meeting

Please find joining instructions (login first), agendas, and invites from the W3C Calendaring tool:

🆕 New work
⏰ April 06 2021, 05:00 - 06:00 UTC
Meeting minutes

🔋 Other device capabilities
⏰ April 06 2021, 15:00 - 17:00 UTC
Meeting minutes

🔒 Privacy and architecture
⏰ April 07 2021, 05:00 - 07:00 UTC
Meeting minutes

📡 Sensors
⏰ April 08 2021, 05:00 - 07:00 UTC
Meeting minutes

[willmorgan]

I will attend to "sponsor" the screen brightness API, whatever time works 👍

[anssiko]

@willmorgan thanks! I just tagged your name next to that topic in the agenda. This is also an API candidate to be brought into the WG once sufficiently incubated first, so noted that in New work section as well.

[anssiko]

What you should know

Chime in on this issue if you have a scheduling conflict. Some usual suspects to drive discussions have been identified below. Additional agenda proposals are welcome.

Please follow the links in the OP for the latest. We'll push another update to your calendars when the schedule and agenda stabilizes.

Thank you,

Chairs @anssiko @reillyeon and Team Contact @xfq

Proposed meeting schedule

🆕 New work
⏰ April 06 2021, 05:00 - 06:00 UTC

🔋 Other device capabilities
⏰ April 06 2021, 15:00 - 17:00 UTC

🔒 Privacy and architecture
⏰ April 07 2021, 05:00 - 07:00 UTC

📡 Sensors
⏰ April 08 2021, 05:00 - 07:00 UTC

Proposed agenda

🆕 New work

• WICG incubations of interest
  • Contact Picker API @xfq @marcoscaceres
    • Proposed for DAS WG Contact Picker API das-charter#97
  • Screen Brightness API @willmorgan
    • Discuss WICG proposal feedback and readiness Screen Brightness API WICG/proposals#17
• Other Proposals for discussion
  • User Presence API @anssiko
    • Gauge interest for this new capability, standalone and/or an extension to existing Proximity @anssiko
  • Compute Pressure API https://github.com/oyiptong/compute-pressure @kenchris @oyiptong

🔋 Other device capabilities

• Screen Fold API -> Device Posture API @kenchris
  • New tighter scope on device posture
• Screen Wake Lock API @rakuco
  • Recent updates to modernize the spec language e.g. editorial: Tidy up uses of "in parallel". screen-wake-lock#299
  • Auto-releasing wake lock Auto-releasing wake lock depending on the user presence screen-wake-lock#300
• System Wake Lock API @reillyeon
  • Follow up on TPAC resolution to write an explainer
• Battery Status API @anssiko
  • [SecureContext] migration Assess compatibility risk of using [SecureContext] battery#15
  • Changes to align with the implementation Improve getBattery() algorithm battery#30
• Geolocation API @marcoscaceres
  • TAG review changes Geolocation API w3ctag/design-reviews#529
  • Privacy enhancement MUST have express permission to share location geolocation-api#64
  • Explicitly limit permission lifetimes https://github.com/w3c/permissions/issues/231
  • Path to REC Publish as FPWD geolocation-api#42
• Network Information API
  • Follow up on TPAC resolution to revise use cases for 2020
• HTML Media Capture @anssiko
  • Integration into HTML Living Standard per W3C/WHATWG Update

🔒 Privacy and architecture

• Incorporating "AB/TAG experiment" recommendations to specs
  • Review and discuss issues filed in response to this experiment, many privacy related
  • Public record of this feedback at DASWG: Drop Geolocation Sensor in favor of existing APIs das-charter#103 (comment)
• Privacy cross-group collaborations
  • Updates from Privacy CG and PING relevant to the DAS WG
• TAG collaboration
  • Refresh of TAG reviews for specs that have not been reviewed in a while
  • Discuss any TAG design guidelines relevant to the work in scope, e.g. Non privacy related design notes on device APIs w3ctag/design-principles#39

📡 Sensors

• Accelerometer @rakuco
  • GravitySensor spec refinements, explainer updates
  • Permissions Policy Integration Add a Permissions Policy Integration section accelerometer#60 @anssiko @reillyeon
• Proximity @anssiko
  • Ecma TC53 interop reqs, e.g. Behavior of distance attribute when sensor cannot provide distance measurements? proximity#44
  • "near" and "user presence state" interaction Auto-releasing wake lock depending on the user presence screen-wake-lock#300
• Ambient Light Sensor @willmorgan
  • Screen Brightness API spin-off Request for Ambient Light Sensor web developer feedback ambient-light#64 Screen Brightness API WICG/proposals#17 @willmorgan

[anssiko]

Here’s the latest virtual meeting logistics update: https://lists.w3.org/Archives/Public/public-device-apis/2021Apr/0000.html

Notably:

If you don't see the Joining Instructions on the above pages that contain Zoom coordinates, please chime in on IRC http://irc.w3.org/?channels=#dap [note: http(!)] at the beginning of each session and we'll let you in.

[anssiko]

FTR, minutes shared on the mailing list: https://lists.w3.org/Archives/Public/public-device-apis/2021Apr/0007.html

Also updated the OP with links to the minutes.

[rakuco]

@anssiko the event pages in w3.org/events/meetings are linking to the wrong minutes:

• Other device capabilities is linking to the New Work minutes.
• Privacy and architecture is linking to a URL that does not exist

[anssiko]

@rakuco thanks for reporting, the URLs are now fixed.

On this topic, if folks have feedback for the W3C Calendar tool we just beta tested for this meeting, feedback is welcome.

I have couple of feature requests on my mind:

• Add links to the minutes directly to this listing: https://www.w3.org/groups/wg/das/calendar?past=1&tf=0 to avoid the need to click "More information" > Minutes.

• Default to "View Past Events" if there are no planned upcoming events. Otherwise https://www.w3.org/groups/wg/das/calendar is not so useful.

I already opened an issue for the "invite changed spam" you received and there's a fix to that underway, see w3c/calendar#24

If many folks think the Calendar tool made things worse, then let us know are we can revert to the manual way of doing meetings where you get to manage your own calendars manually.