Summary

  • ICANN says it published a Unified Canadian Aboriginal Syllabics script reference for second-level labels on 5 October, after consultation and public comment.
  • The working-group proposal is designed for a zone that also supports French IDNs; neither document establishes that a registry has adopted or deployed it.

Analysis

The UCAS ruleset makes a difficult registry-review question concrete: a script-level reference can span several language communities while still having to fit beside another script’s rules in a single zone. ICANN announced its publication on 5 October. The underlying proposal is dated 23 April and says it is designed for use in a zone that caters to French IDNs, with features intended to let it operate in the context of a French LGR. That is a design statement, not evidence that a particular French-language registry has put it into production.

The distinction matters because “reference” is not another word for permission. ICANN says second-level Reference Label Generation Rules help reviewers assess IDN tables submitted by generic top-level-domain registries and facilitate registry operations. The reference describes how labels may be formed and how variants are identified. A registry’s table still has to be designed and submitted; the review of that table and its use in a live service are separate steps. The announcement does not name a registry using the new UCAS rules, identify accepted labels or report registrations.

The proposal also makes the ruleset’s scope more complex than one language-to-one-table mapping. It describes Unified Canadian Aboriginal Syllabics as primarily used by First Nations and Inuit in Canada and lists multiple Algonquian syllabic languages. The working group says its development drew on open discussions with experts and communities. Its stated attestation approach looks for contemporary usage through public digital material, print, academic and scientific work, education, revitalization resources and language authorities.

That is evidence of a documented process; it is not proof that every listed community endorsed each rule or that the proposal resolves orthographic choices for all users.

Those choices have technical consequences. The proposal includes repertoire, variant relationships and contextual restrictions. Such rules can help a reviewer understand which strings are treated as valid under the reference and which variant relationships or sequences require special handling. They may reduce ambiguity in a submitted table, but the documents do not claim to eliminate every visual-confusability risk or to settle how a registry must apply its own policy.

The publication chronology needs careful reading. ICANN’s public-comment page says the consultation opened on 12 May and closed on 23 June, with a report due in August. The proposal PDF carries an April date; the reference collection currently labels the UCAS entry with a 13 August version date; the announcement is dated 5 October. These are three different dates attached to proposal, collection version and announcement. The sources do not justify collapsing them into a claim that the work first appeared on 5 October.

ICANN says the final reference collection now covers 30 scripts and 32 languages. That larger set is a common input to review, not a universal registry configuration. The practical test is whether a submitted table’s repertoire, variants and restrictions match the rules its operator intends to deploy, and whether the resulting service actually uses that reviewed table. Publication improves the common reference point; it does not substitute for the registry-specific evidence.

Sources