You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are several Places in the model, as well as PostalAddresses. To guarantee interoperability we need to recommend the way to describe countries.
At first sight, I would recommend ISO 3166 codes, but I found that IAAF uses IOC codes that are different. For instance: SLO (IOC) - SVN (ISO3166) for Slovenia.
A colleague of mine suggested using a third schema wich includes both code schemes, also aligned with others such as ITU, NATO, IATA, etc. This could solve some of the problems we have:
More than countries. Hierarchically we can have countries>regions>counties>cities.
Multilingualism. Place names translated into dozens of languages. (e.g. فنلینڈ <- Finland in Urdu).
I have to check if we can customize the list for us. This is, having a easy way to get the code (URI).
The text was updated successfully, but these errors were encountered:
i've just created some datasets focusing on the 'administrative' levels of the iaaf, more specifically regional affiliations (i.e. eaa, caa, etc.) [1] & national federations (i.e. gibraltar amateur athletic association) [2].
There are several
Place
s in the model, as well asPostalAddress
es. To guarantee interoperability we need to recommend the way to describe countries.At first sight, I would recommend ISO 3166 codes, but I found that IAAF uses IOC codes that are different. For instance: SLO (IOC) - SVN (ISO3166) for Slovenia.
A colleague of mine suggested using a third schema wich includes both code schemes, also aligned with others such as ITU, NATO, IATA, etc. This could solve some of the problems we have:
I have to check if we can customize the list for us. This is, having a easy way to get the code (URI).
The text was updated successfully, but these errors were encountered: