Re: [vibration] Update implementation report (#33)

> @marcoscaceres, please clarify whether your Formal Objection is limited to this misrepresentation of the implementation status or if you will persist is requesting the Team consider overriding the group's decision to continue work on this deliverable.

I think it's both: 

1. the misrepresentation of the implementation status.
2. The group's decision to continue work.

For 2. the [Scope of the Charter](https://www.w3.org/2024/02/das-wg-charter.html#scope) is:

- reacting to device power status
- preventing the screen from turning off under certain conditions
- preventing the system from turning off under certain conditions
- accessing nearby devices without physical contact
- responding to ambient light levels of the device’s environment
- reacting to changes in motion and orientation of the hosting device
- providing location information, either of the hosting device or a location selected by the user

So my reading of the scope is that haptics/vibrations are not in Scope.  

WebApps WG, on the other hand, has haptics explicitly in [Scope](https://www.w3.org/2024/01/webappswg-charter-2024.html#scope):

* Haptic input devices and their emitted events and/or data.

So it feels inappropriate the continue any evolution of the Vibration API as in DAS (beyond errata, editorial fixes) as haptics are not in scope of the DAS working group. 

-- 
GitHub Notification of comment by marcoscaceres
Please view or discuss this issue at https://github.com/w3c/vibration/issues/33#issuecomment-2138575571 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 30 May 2024 02:49:19 UTC