[i18n-activity] String metadata and localization for operator labels (#1999)

xfq has just created a new issue for https://github.com/w3c/i18n-activity:

== String metadata and localization for operator labels ==
## Proposed comment

https://www.w3.org/TR/webnn/#operator-label

> An [operator](https://www.w3.org/TR/webnn/#operators) has a label, a string which may be included in diagnostics such as [exception](https://webidl.spec.whatwg.org/#dfn-exception) messages. When an [operator](https://www.w3.org/TR/webnn/#operators) is created its [label](https://www.w3.org/TR/webnn/#operator-label) is initialized in an [implementation-defined](https://infra.spec.whatwg.org/#implementation-defined) manner and may include the passed [label](https://www.w3.org/TR/webnn/#dom-mloperatoroptions-label).

The WebNN specification defines operator labels as developer-provided strings used for diagnostic purposes.

Section 10.8.1 of the [Internationalization Best Practices for Spec Developers](https://w3c.github.io/bp-i18n-specdev/#errors) document recommends that APIs provide language-independent identifiers for errors and, if natural language error message fields are included, these should include language and direction metadata and ideally match the user interface language negotiated for the request.

I'm not sure whether WebNN operator labels constitute natural language strings akin to error messages. If they are natural language, they should include language and direction metadata and consideration for localization to align with i18n best practices. I propose clarifying the nature of operator labels and ensuring compliance with i18n guidelines.

## 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. **Add one or more t:... labels. These should use ids from specdev establish a link to that doc.**

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/1999 using your GitHub account


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

Received on Friday, 11 April 2025 03:46:13 UTC