-
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
Wording change: drop links to File API's "object", define platform operand/operator #540
Wording change: drop links to File API's "object", define platform operand/operator #540
Conversation
It would be more intuitive for editors (and more expressive for the readers) if |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As a bonus this allows us to shorten normative references, drop [FileAPI] entirely 🥳
@inexorabletash feel free to review all of https://www.w3.org/TR/webnn/#normative similarly for possible auto-linking bugs e.g. "number".
Yeah, "number" is on my to-do list. Since the reference is in the reshape() steps and #452 and #450 (comment) already discuss issues with it. I'll wait for that to settle down a bit. I normally look for outliers in https://www.w3.org/TR/webnn/#index-defined-elsewhere - I think we're good after "object" and "number" are sorted. |
aeb17b8
to
48f9800
Compare
In case you weren't following the thread above: this has been significantly revised to include basic definitions for platform operand and platform operator which could be improved but I think are not wrong, and simplify references throughout the spec. |
48f9800
to
2cad184
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! Thanks!
9237bf5
to
ce93588
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with a nit, thanks!
The default linking for [=object=] is to FileAPI's blob URL entry object member[1], which is definitely wrong. Replace such references with: * Infra's ordered map[2], when a dictionary is intended, as that's what a JavaScript object is translated into via bindings. * Links to new definitions for "platform operator" and "platform operand" which include the "implementation-defined" phrase so links to the terms can be greatly simplified. These definitions should be further expanded to include "connect", "input" and "output" but that can be tackled later. This reduces the number of "implementation-defined" phrases to just a handful in the spec, which helps with webmachinelearning#462. [1] https://www.w3.org/TR/FileAPI/#blob-url-entry-object [2] https://infra.spec.whatwg.org/#ordered-map Co-authored-by: Anssi Kostiainen <[email protected]> Co-authored-by: Ningxin Hu <[email protected]>
82993c2
to
6ab284b
Compare
I think this is good to go - one more look? |
SHA: 7ec2e18 Reason: push, by huningxin Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
The default linking for [=object=] is to FileAPI's blob URL entry object member[1], which is definitely wrong.
Replace such references with:
Infra's ordered map[2], when a dictionary is intended, as that's what a JavaScript object is translated into via bindings.
Links to new definitions for "platform operator" and "platform operand" which include the "implementation-defined" phrase so links to the terms can be greatly simplified. These definitions should be further expanded to include "connect", "input" and "output" but that can be tackled later.
This reduces the number of "implementation-defined" phrases to just a handful in the spec, which helps with #462.
[1] https://www.w3.org/TR/FileAPI/#blob-url-entry-object
[2] https://infra.spec.whatwg.org/#ordered-map
💥 Error: 405 Method Not Allowed 💥
PR Preview failed to build. (Last tried on Feb 2, 2024, 5:45 PM UTC).
More
PR Preview relies on a number of web services to run. There seems to be an issue with the following one:
🚨 CSS Spec Preprocessor - CSS Spec Preprocessor is the web service used to build Bikeshed specs.
🔗 Related URL
If you don't have enough information above to solve the error by yourself (or to understand to which web service the error is related to, if any), please file an issue.