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

@anssiko wrote: 
>  I'm interested in devices capable of running these implementations: https://caniuse.com/vibration

Before you do that, the WG MUST get clarification from the W3C is Chromium only implementations count as independent implementations. Otherwise, you'll be wasting your and time writing a report that doesn't meet the process requirements. 

I again remind you that, as per "[6.3.2. Implementation Experience](https://www.w3.org/2023/Process-20231103/#implementation-experience)" it's the Team, not the WG or Chair, that makes the determination about what counts as an implementation.   

Please get clarification from @plehegar and @himorin before proceeding with the implementation of report. If they say that Chromium only implementations count, then I don't have a case for my objection on this matter.

Further, both the Team and the report need to be clear on (noting things I have emphasized):

* is each feature of the current specification implemented, and **how is this demonstrated**?
* are there **independent interoperable implementations** of the current specification?
* are there implementations **created by people other than the authors of the specification**?
* are implementations publicly deployed?
* is there implementation experience at all levels of the specification’s ecosystem (authoring, consuming, publishing…)? (e.g., https://chromestatus.com/metrics/feature/timeline/popularity/850)
* are there **reports of difficulties or problems with implementation**?
 
In particular, the report should note things like why certain implementations don't work and implementer feedback. 

>@marcoscaceres, DAS WG is [chartered to maintain](https://www.w3.org/2024/02/das-wg-charter.html#deliverables-maintenance) the Vibration API. Does that address your concern? 

Depends on what "maintain" means to the WG. If maintain means [errata](https://www.w3.org/2023/Process-20231103/#errata), then that is fine, as it only applies to "error that can be resolved by one or more changes in classes 1-3 of section [§ 6.2.3 Classes of Changes](https://www.w3.org/2023/Process-20231103/#correction-classes)."

That is:

1. No changes to text content
1. Changes that do not functionally affect interpretation of the document
1. Other changes that do not add new features

If maintain means working on new features, then that remains a concern. 

In https://github.com/w3c/vibration/issues/33#issuecomment-2120464362, Above you said: 

> With time, it might be that the baseline LCD will move so that we can update this API to consider new features. One of the possible such features under consideration is strength control https://github.com/w3c/vibration/issues/17 that might be soon about to reach the level it could be considered. Contributions welcome in this area too from interested folks.

That seems to imply (and explicitly encourage) feature development of something that is outside the scope of the working group.  



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


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

Received on Monday, 3 June 2024 01:38:15 UTC