[wg/das] Device and Sensors WG 2023 Rechartering about strategy HOT 22 CLOSED

no needs-resolution from i18n, but we would recommend to update sections from 3. Success Criteria to 9. Licensing to align with the latest charter template, especially to remove horizontal review on performance.

from strategy.

In 4.1, perhaps we should mention the DAS WG will collaborate with the Web Applications Working Group on a few joint deliverables, including the Contact Picker API, the Screen Wake Lock API, the DeviceOrientation Event Specification and the Geolocation API.

from strategy.

I found it odd that System Wake Lock API is listed twice, with different adopted drafts. That might merit an explanatory note.

I believe these are "Screen Wake Lock API" and "System Wake Lock API"...

from strategy.

Added as a potential PING item for October 5. cc @npdoty

from strategy.

"monitoring" may be the wrong framing for privacy-preserving APIs on the Web: the goal of the platform should not be to monitor users' devices, but to allow users who want to to access certain capabilities.

Maybe:
"providing" location information, and not necessarily location information of the hosting device.
"accessing nearby devices without physical contact"
"responding to ambient light levels"
"reacting to changes in motion or orientation"

Defining these specifically as properties of the hosting device or as ongoing monitoring will overconstrain the designed solution in ways that don't align well with privacy.

from strategy.

If the plan is to coordinate with the Web Apps Working Group on the location deliverables (and other deliverables), then the charter should say so directly.

from strategy.

If the plan is to coordinate with the Web Apps Working Group on the location deliverables (and other deliverables), then the charter should say so directly.

Does it not? Are you thinking of some language more explicit than, "This work is a joint deliverable with the Web Applications Working Group"?

from strategy.

The Coordination section indicates that the Web Apps group works on File and Web Manifest and that will be a point of coordination. So maybe you could just add to that section that the plan is also to coordinate with Web Apps on geolocation (either just Geolocation API, or maybe geolocation and motion more generally).

from strategy.

Also, the charter table of contents uses inconsistent labeling on dependencies vs coordination.

from strategy.

APA has no accessibility concerns with the proposed Charter, but wish to ask whether there might be scope to update the Vibration API to support high-fidelity haptics. We inquire because we were presented Use Cases Requiring High-Fidelity Haptics during TPAC 2023.

from strategy.

I found it odd that System Wake Lock API is listed twice, with different adopted drafts. That might merit an explanatory note.

from strategy.

I agree with @npdoty that 'monitor' sounds more like tracking and less like a desirable thing for the user. Suggest presenting a user-centered use case, such as "ambient light sensor enables automatic adjustment of HDR videos and images to maintain viewability in different environments"

from strategy.

draft copied to https://github.com/w3c/charter-drafts/blob/gh-pages/2023/das-wg-charter.html, all PR at das-charter repo merged. (and links in the description updated)

from strategy.

@plehegar , all: PR for provided comments raised at w3c/charter-drafts#465

from strategy.

"discretion of the Chairs or the Director." s/or the Director//

from strategy.

AC review: https://lists.w3.org/Archives/Member/w3c-ac-members/2023OctDec/0032.html

from strategy.

w3c/charter-drafts#476

from strategy.

email on proposed changed text out to reviewers

from strategy.

email on proposed changed text out to reviewers

received one comment on itemized text in Scope.

from strategy.

email on proposed changed text out to reviewers

received one comment on itemized text in Scope.

Proposed small change looks good to me.

from strategy.

no other comment provided during 7 days review period.

@npdoty @svgeesus I've opened a PR for this change as w3c/charter-drafts#480

from strategy.

charter out, and announced

from strategy.