[i18n-activity] sorting "alphanumerically" underspecified (#1525)

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

== sorting "alphanumerically" underspecified ==
## Proposed comment Listing

> By default, the collection MUST be sorted alphanumerically by the unique identifier of TDs. The server MAY support sorting by other TD attributes using query arguments: sort_by to select a field (e.g. created) and sort_order to choose the order (i.e. asc or desc for ascending and descending ordering). If the server does not support custom sorting, it MUST reject the request with 501 (Not Implemented) status. If sorting attributes are accepted, they MUST be added consistently to all next links. 

This comment may be moot if the _unique identifier of TDs_ turns out to be a URI. However, if the ID is a name token, even if restricted to US-ASCII, the sort order "alphanumerically" is underspecified. 

Probably "alphanumerically" should be augmented with Unicode code point order, e.g.:

> Be default, the collection MUST be sorted alphanumerically on the unique identifier of the TDs, where "alphanumeric" means in order by Unicode [code point](https://w3c.github.io/i18n-glossary/#def_code_point).

(If you want to join mean in pedantry you can call out that UPPER and lowercase letters don't sort together)

Providing for linguistically-correct ordering is many orders of magnitude harder and should be avoided here. Note that above text recommendation also applies if the `id` can be non-ASCII.

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

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

Received on Thursday, 28 April 2022 19:39:03 UTC