[Unicode]   Common Locale Data Repository : Bug Tracking Home | Site Map | Search

CLDR Ticket #8423(closed: fixed)

Opened 4 years ago

Last modified 4 months ago

Subdivision syntax

Reported by: mark Owned by: mark
Component: locale-codes-names Data Locale:
Phase: final Review: pedberg
Weeks: Data Xpath:



Description (last modified by mark) (diff)

We're planning on adding the subdivision codes (http://unicode.org/cldr/trac/ticket/8319).

In so doing, we should also make the following changes:

  1. In http://unicode.org/reports/tr35/#Unicode_Language_and_Locale_Identifiers

define the following:

unicode_subdivision_subtag = alphanum{1,3} ; 1*3alphanum

Add some text to indicate that the valid codes based on those listed in <subdivisionContainment>. That is, a subdivision in a locale tag is valid iff there is some group element in a subdivisionContainment element such that:

  • the type value is the unicode_region_subtag for the tag.
  • the contains value (a space-delimited set) contains unicode_region_subtag + "-" + subdivision.
  1. add a bcp47 entry


<key name="sd" description="Region subdivision">

<type name="SUBDIVISION_CODE" description="Valid subdivision code for the region subtag, based on subdivisionContainment data in supplementalData, as described in LDML."/>



We will need to make one adjustment. The value of a key must be 3 characters or more. I suggest that we prefix any 1 or 2 letter subdivision code with "xxx". Then the codes are 3..5 in length, and anything 4 or 5 letters long just removes the xxx.

  1. In the future—but only when it becomes necessary:
  1. In the DTD for <subdivisionContainment><group>, add an attribute status with value "deprecated"

<group type="US" category="state"contains="CA" status="deprecated"/>

  1. Add a child of <alias> for deprecated subdivision codes, eg.

<subdivision Alias territory="US" type="CA" replacement="OR" reason="deprecated"/> <!-- California -->

This will take an attribute that we don't need for languageAlias, etc.: territory=...


Change History

comment:1 Changed 4 years ago by mark

  • Cc pedberg added

comment:2 Changed 4 years ago by mark

  • Owner changed from anybody to mark
  • Priority changed from assess to major
  • Status changed from new to accepted
  • Component changed from unknown to bcp47
  • type changed from unknown to dtd

comment:3 Changed 4 years ago by mark

  • Description modified (diff)

comment:4 Changed 4 years ago by mark

  • Phase changed from dsub to dvet
  • Milestone changed from UNSCH to 28

comment:5 Changed 4 years ago by mark

  • Phase changed from dvet to dsub

comment:6 Changed 4 years ago by mark

  • Xref set to 8319

comment:7 Changed 4 years ago by mark

Changed xxx to 00. We only need 2 characters, and the 00 are more distinctive. To prevent ambiguity, the 00 are added always.

comment:8 Changed 4 years ago by mark

Put the new bcp47 key into variant.xml. Could move it to its own file if we want.

comment:9 Changed 4 years ago by mark

  • Status changed from accepted to reviewing
  • Review set to pedberg

comment:10 Changed 3 years ago by pedberg

  • Phase changed from dsub to final
  • Status changed from reviewing to closed
  • Xref changed from 8319 to 8319 8949
  • Resolution set to fixed
  • type changed from dtd to spec

Fixed the bc47 description, which still said the subdivision attribute prefix was "00".

comment:11 Changed 4 months ago by mark

  • Component changed from bcp47 to locale-codes

Add a comment

Modify Ticket

as closed
Next status will be 'new'
Next status will be 'closed'

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.