Devices and Sensors WG - TPAC 2024 agenda

[anssiko]

[!IMPORTANT] This is a work in progress draft agenda for the Devices and Sensors WG meeting at TPAC 2024.

Registration

• Registration is now open until 13 September 2024: https://www.w3.org/register/tpac2024
• All registered Devices and Sensors WG participants and invited guests welcome. Joint deliverables discussions is also open to all Web Applications WG participants.

Logistics

• 🏨 Venue: Hilton Anaheim in-person & remote
• 🗓️ Meeting invites:
  • 24 September 2024, 09:00–10:30 Pacific Daylight Time (joint meeting)
  • 24 September 2024, 11:00–18:00 Pacific Daylight Time
• ⏰ Schedule: Tuesday 24 September 2024 9:00-18:00 PDT local time (see your local time)
  • ⏰ Start: 9:00 local / 16:00 UTC
  • ⏰ Morning break: 10:30 - 11:00 local / 17:30 - 18:00 UTC
  • ⏰ Lunch: 12:30 - 13:30 local / 19:30 - 20:30 UTC
  • ⏰ Afternoon break: 14:30 - 15:00 local / 21:30 - 22:00 UTC
  • ⏰ End: 18:00 local / 00:00 UTC
• 📞 Zoom details: see 🗓️ Meeting invite > Joining Instructions
• ✍️ IRC: IRC web client or irc://irc.w3.org:6667/#dap
• ✍️ Minutes: https://www.w3.org/2024/09/24-dap-minutes.html

Related meetings

Any related meetings of interest to the DAS WG participants to be listed here.

• Breakouts: Permissions track (schedule grid)

Agenda

[!WARNING] This is a Living Agenda, please expect updates. We'll do the usual agenda bashing at the beginning of the meeting for any last-minute additions subject to available agenda time.

[!TIP] For completeness, this agenda enumerates all the WG's deliverables, including some tentative ones. Due to time limitations, we cannot allocate equal agenda time for every deliverable, and we give preference to deliverables that have issues or proposal that we think will benefit from F2F/hybrid style discussion. "None" indicates no issues proposed to the F2F agenda currently.

⏰ Start joint meeting 9:00 local / 16:00 UTC

👋 Welcome

• Intros
• Agenda bashing

📘 Charter update

• New joint deliverables

🤝 Joint deliverables

Screen Wake Lock API

• https://github.com/w3c/screen-wake-lock/issues/352
• https://github.com/w3c/screen-wake-lock/issues/350

Device Orientation and Motion

• Progress towards a new Candidate Recommendation
  • CfC: https://lists.w3.org/Archives/Public/public-device-apis/2024Mar/0000.html
• Integrating features from the Generic Sensors API

Geolocation API

• Test automation https://github.com/w3c/geolocation/issues/146
• System permissions https://github.com/w3c/geolocation/issues/107 / https://github.com/w3c/permissions/issues/332
• Learnings from the updatable Recommendation journey

Contact Picker API

• ...

⌛ End joint meeting 10:30 local / 17:30 UTC

⏰ Resume WG meeting 11:00 local / 18:00 UTC

🔒 Privacy & Security

• New Privacy Principles and Ethical Principles Notes published by the TAG

🤖 Test automation

• A session to discuss the WG's approach to test automation using WebDriver and recent progress in this space.

⚙️ Sensor Framework

Generic Sensor API

• https://github.com/w3c/sensors/issues/7
• https://github.com/w3c/sensors/issues/463

🔄 Motion Sensors

⭐ Accelerometer

• https://github.com/w3c/accelerometer/issues/69
• https://github.com/w3c/accelerometer/issues/57
• https://github.com/w3c/accelerometer/issues/54

Gyroscope

• https://github.com/w3c/gyroscope/issues/45
• ⭐ Gamepad API gyro support

Magnetometer

• ⭐ Review implementation status & signals, web developer feedback, decide next steps accordingly

Orientation Sensor

• https://github.com/w3c/orientation-sensor/issues/43

🍴 Lunch 12:30 local / 19:30 UTC

⏰ Resume WG meeting 13:30 local / 20:30 UTC

📡 Environment Sensors

Ambient Light Sensor

• https://github.com/w3c/ambient-light/issues/64
• https://github.com/w3c/ambient-light/issues/79

Proximity Sensor

• Review implementation status & signals, web developer feedback, decide next steps accordingly

⭐ Geolocation Sensor

• Discuss a proposal to rescope this API to address background/geofencing use cases only
  • https://github.com/w3c/geolocation-sensor/issues/17
• Background geolocation and geofencing
  • Use cases revisited
  • https://github.com/w3c/geolocation-sensor/issues/22
  • https://w3c.github.io/geolocation-sensor/#use-cases
  • API proposals revisited
  • https://github.com/w3c/geolocation-sensor/issues/62

Screen Brightness API

• https://github.com/WICG/screen-brightness/issues/1

⭐ System Wake Lock API

• Introduction of the Progress Notification API from @ayuishii.

⭐ Compute Pressure API

• Candidate Recommendation transition readiness https://github.com/w3c/compute-pressure/issues/177
• v2 issue triage (post-CR features)
• ...

☕ Afternoon break 14:30 - 15:00 local / 21:30 - 22:00 UTC

⏰ Resume WG meeting 15:00 local / 22:00 UTC

🔋 Device Capabilities

⭐ Vibration API

• Wide review feedback dissemination https://github.com/w3c/vibration/issues/39
• CRS plan

1/2 ⭐ Battery Status API

• New use cases https://github.com/w3c/battery/issues/25
• Energy Saver Mode revisited https://github.com/w3c/battery/blob/gh-pages/energy-saver-mode-explainer.md

⭐ Device Posture API

• Wide review feedback dissemination https://github.com/w3c/device-posture/issues/146
• Candidate Recommendation plan

🫶 Wrap up

• Synthesis of key outcomes, next steps

[rakuco]

🤖 Test automation

• A session to discuss the WG's approach to test automation using WebDriver and recent progress in this space.

Given that there's no ETA for power to be restored at the venue today, I don't think we'll have time to do this, or at least I won't be able to be around.

These are the slides I intended to present: WebDriver and test automation, take 3.pdf

The tl;dr is that we've managed to add WebDriver endpoints to several DAS specs and make their respective web tests in WPT use them too :tada: Big kudos to @JuhaVainio for the help converting many web tests and to @reillyeon for being instrumental in helping define the blueprint for this work when we were focusing on Generic Sensors and for reviewing so many patches in Chromium.

[kenchris]

Given that there's no ETA for power to be restored at the venue today, I don't think we'll have time to do this, or at least I won't be able to be around.

I will probably have the same issue for CP, unfortunately.