search

INSPIRE-MIF / 2017.2

Repository for action 2017.2 on alternative encodings
6 stars 11 forks source link

simplification rule : geographical name #71

Open NathalieDelattre opened 5 years ago

NathalieDelattre commented 5 years ago

Simplification geographical names

associating the language code with the attribute name like name_deu : what if users or APIs want to list the name of several countries in the same time knowing that they are in different languages, even inside a country like Belgium, and how to know which languages are used ? The attribute naming should be the same in case of listing or showing all the geographical names at once independently from the language. I would be in favour to associate the name with the nativeness (there we have two options ) ; I think that it is relevant to make a real difference between endonyms and exonyms. Endonyms are the official names and are mandatory exonyms are optionaL;

name_endonym: München name_endonym_language: ger ( which is just an information)

name_exonym: Munich name_exonym_language : eng keep in mind that name_exonym is optional and might not be provided.

In case we meet official spoken languages in a same area and an official name in different languages

Hoping it is clear

heidivanparys commented 5 years ago

I think the first part of this issue may be solved by the model transformation described in https://github.com/INSPIRE-MIF/2017.2/issues/70#issuecomment-468180473

Regarding

Endonyms are the official names

as I had understood it, information regarding whether or not a name is official is recorded in attribute nameStatus, with the values described in http://inspire.ec.europa.eu/codelist/NameStatusValue ?