Consider this localization:
state=California
country=US
OR
Device is in England, country is GBR. How do we represent England here?
locality would commonly be used for cities.
So we may need another field between country and locality.
Possible names: region, state, province
We may also need a new management API so all localization can just be set together.
For instance, if we have "region"="California", country=US. If we set country to CA. There could be a period of time where the device is seen as California inside of Canada. Probably best if the API just sets both country and region (and locality and postalCode) all at the same time.
Consider this localization: state=California country=US
OR
Device is in England, country is GBR. How do we represent England here?
locality would commonly be used for cities. So we may need another field between country and locality. Possible names: region, state, province
We may also need a new management API so all localization can just be set together. For instance, if we have "region"="California", country=US. If we set country to CA. There could be a period of time where the device is seen as California inside of Canada. Probably best if the API just sets both country and region (and locality and postalCode) all at the same time.