-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[wg/webmachinelearning] Web Machine Learning Working Group Charter #488
Comments
charter history table might need to have a link to current running charter (and also additional row of this proposed charter). |
history table updated in w3c/machine-learning-charter@133f23a |
No comment or request from i18n |
APA is OK for this Charter. |
Overall the charter looks good. One minor question: Why has the word "specifications" been replaced by "Recommendations"? The template used to say that, and we changed it once CR Snapshots also gained patent policy protection.
In other words is that an intentional change, or just a cop-paste error from an earlier charter or earlier template? |
thanks for spotting this @svgeesus ! this was something I miss when doing the charter template alignment, now fixed |
The timeline seems slightly too optimistic, unless you are planning to publish a (final) CR snapshot right away? |
@caribouW3 thanks for flagging this, I had missed updating the timeline; I've raised w3c/machine-learning-charter#43 to track fixing this - for sake of clarity, it's entirely clear we won't finish WebNN by the end of this quarter; the charter will be updated with a more up-to-date estimate. |
@caribouW3 charter now updated with a new completion timeline |
+1 (you should update in section 3.3 as well) |
very minor consideration in the motivation section: or |
I'm not a native English speaker, but I think the current capitalization and punctuation correctly reflect the usage of "Speech Recognition" and "Speech Synthesis" as two separate types of processing, both of which are the subject of "enable". |
As part of its scope, the group has a "priority on building blocks required by well-known model architectures". What progress, if any, has been made around webmachinelearning/webnn#350 ? |
significant progress, with a detailed explainer https://github.com/webmachinelearning/webnn/blob/main/device-selection-explainer.md and a matching soon-to-be-merged spec pull request webmachinelearning/webnn#809 - we expect this to be part of our next CR Snapshot (and thus to get wide review soon) |
I can see it now. You may want to consider splitting into multiple sentences? "Computer Vision enables computers to gain understanding from images or videos. Natural Language Processing enables interaction between computers and human languages. Speech Recognition and Speech Synthesis enable computers to recognize and translate spoken language into text and vice versa. Bringing these experiences to the web [...]" |
Splitting into multiple sentences make sense for readability, indeed - done |
No comment from Privacy WG |
New charter proposal, reviewers please take note.
Charter Review
Charter
diff from charter template
diff from previous charter
chair dashboard
What kind of charter is this? Check the relevant box / remove irrelevant branches.
Horizontal Reviews: apply the Github label "Horizontal review requested" to request reviews for accessibility (a11y), internationalization (i18n), privacy, security, and TAG. Also add a "card" for this issue to the Strategy Funnel.
Communities suggested for outreach
Browser vendors, AI systems developers, ML processing units vendors, ML framework developers
Known or potential areas of concern
N/A
Where would charter proponents like to see issues raised? (this strategy funnel issue, a different github repo, email, ...)
https://github.com/w3c/machine-learning-charter/issues
Anything else we should think about as we review?
The sister Web Machine Learning Community Group recently adopted a set of LLM-based browser APIs for incubation - the Working Group is not ready to adopt them as tentative deliverables yet, but is signalling its future interest in doing so to call for the attention of the community on this space.
Note: proposed chairs should be copied @... on this issue.
cc @anssiko
The text was updated successfully, but these errors were encountered: