Multiple semicolon-separated values do not solve the main problem - figuring out the language of the "name" tag. If a region uses one value in the name tag, "default_language" should be set to just one language.
If the whole region uses "xx - yy" convention in the name tag, default_language could be set to "xx - yy" -- allowing tools to parse name tag into two languages (although this would be an error prone method). "official_language" is not a good tag name because it does not match the meaning, e.g. the official languages of Canada are both en & fr, but "name" tag is always in English except for Quebec, where it is in French. Are there any objections to this (fuzzy) approach? Should the tag be called something else? * Use the largest possible admin region to set the "default_language" tag to a single language code. "default_language"Z does not mean the official language of the region. It only specifies the language of the "name" tag. * A region may contain a sub-region with a different default_language. * If a region uses mixed languages in all of its name tags, eg. "[name in en] - [name in zh]", set default_language="en - zh". Try to keep it to a somewhat parsable value to help data consumers. * In some rare cases, additional non-admin regions might be required for the default_language. Try to avoid it if possible. On Thu, Apr 26, 2018 at 5:41 PM Daniel Koć <daniel@koć.pl> wrote: > W dniu 26.04.2018 o 15:36, Martin Koppenhoefer pisze: > > > 2018-04-26 14:16 GMT+02:00 Daniel Koć <daniel@koć.pl>: > >> >> Isn't it like this: >> >> Country Belgium - official_language=de;fr;nl >> Region Brussels-Capital - official_language=fr;nl >> City Eupen - official_language=de >> >> What would be wrong with this scheme? > > > > it is only about "official languages" and it would somehow imply we would > not want names added through ground truth for cases where the language the > name is in, would not be recognized as an official language. > > > Sure, that's why I suggested common_language=* (common_language=xx + > name:xx=* is just like saying "name=* is in xx"). > > Could you explain this problem using some examples? > > I also don't know what this would imply for areas without formal > government / disputed areas. Whose "official" language would we tag? > > > That's interesting case. How do we tag the borders for such areas? > > If countries/regions with known official_language=* are overlapping, the > language would be known for both and you have to choose one or show both > (the same as official_language=xx;yy). > > Another solution would be to use some special values, like "none" or > "disputed" for this area (unfortunately "no" is a code for Norwegian > language). > > -- > "My method is uncertain/ It's a mess but it's working" [F. Apple] > > _______________________________________________ > talk mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/talk >
_______________________________________________ talk mailing list [email protected] https://lists.openstreetmap.org/listinfo/talk
