W3C home > Mailing lists > Public > public-i18n-archive@w3.org > April to June 2022

[i18n-activity] Label by text possibly with natural language, without metadata attached (#1548)

From: himorin / Atsushi Shimono via GitHub <sysbot+gh@w3.org>
Date: Wed, 25 May 2022 07:31:09 +0000
To: public-i18n-archive@w3.org
Message-ID: <issues.opened-1247681049-1653463867-sysbot+gh@w3.org>
himorin has just created a new issue for https://github.com/w3c/i18n-activity:

== Label by text possibly with natural language, without metadata attached ==
## Proposed comment

MLNamedOperands in 7.7. MLGraphBuilder, etc.

> typedef record<DOMString, MLOperand> MLNamedOperands;
> MLOperand input(DOMString name, MLOperandDescriptor desc);

There is in total 5 defined types as `typedef record <DOMString, spec_defined_type>`, to label data passed or points in processing by DOMString. As in [Example 7](https://www.w3.org/TR/webnn/#example-a68b3273), these labels are kind of key to label data, but are also defined when building Graph.
// Execute the compiled graph with the specified inputs.
const inputs = {
  'input1': inputBuffer1,
  'input2': inputBuffer2,
const outputs = {'output': outputBuffer};
context.compute(graph, inputs, outputs);

These labels are strongly linked to each Graph wrote as code, and purely used within writing code. But considering some kind of interactive processing tool, like Jupyter or visual trial user interface (e.g. [function in IBM DOM](https://www.ibm.com/docs/ja/odm/8.11.0?topic=tool-using-rest-api-test), user is required to fill inputs (and possibly outputs) by pairs of these label and user input.
For these use cases, labels in DOMString are required to be displayed at UI, which requires consideration of metadata.

## Instructions: 

This follows the process at https://w3c.github.io/i18n-activity/guidelines/review-instructions.html

1. Create the review comment you want to propose by replacing the prompts above these instructions, but **LEAVE ALL THE INSTRUCTIONS INTACT** 

2. Set a label to identify the spec: this starts with s: followed by the spec's short name. If you are unable to do that, ask a W3C staff contact to help.

3. Ask the i18n WG to review your comment.

4. After discussion with the i18n WG, raise an issue in the repository of the WG that owns the spec. Use the text above these instructions as the starting point for that comment, but add any suggestions that arose from the i18n WG. In the other WG's repo, add an 'i18n-needs-resolution' label to the new issue. If you think any of the participants in layout requirements task force groups would be interested in following the discussion, add also the appropriate i18n-\*lreq label(s).

5. Delete the text below that says 'url_for_the_issue_raised', then add in its place the URL for the issue you raised in the other WG's repository. Do NOT remove the initial '§ '. Do NOT use \[...](...) notation – you need to delete the placeholder, then paste the URL.

6. Remove the 'pending' label, and add a 'needs-resolution' tag to this tracker issue. 

7. If you added an \*lreq label, add the label 'spec-type-issue', add the corresponding language label, and a label to indicate the relevant typographic feature(s), eg. 'i:line_breaking'. The latter represent categories related to the Language Enablement Index, and all start with i:.

8. Edit this issue to **REMOVE ALL THE INSTRUCTIONS & THE PROPOSED COMMENT**, ie. the line below that is '---' and all the text before it to the very start of the issue.


**This is a tracker issue.** Only discuss things here if they are i18n WG internal meta-discussions about the issue. **Contribute to the actual discussion at the following link:**

§ url_for_the_issue_raised

Please view or discuss this issue at https://github.com/w3c/i18n-activity/issues/1548 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 25 May 2022 07:31:10 UTC

This archive was generated by hypermail 2.4.0 : Monday, 4 July 2022 18:09:47 UTC