question: language codes in the MLGT register page

[ReesePlews]

hello @ronaldtse and @strogonoff i was looking at the registers page [ https://isotc211.geolexica.org/registers/ ] with contact metadata for geolexica and i have some questions about the following items shown by "*" . i am not sure if there are problems or incomplete metadata for those records. when you have time can you check. i am not sure where the data came from, why some are capitalized (first letter) and some are not, etc. this is not a priority. thank you

    operating-language-name: العربية
    operating-language-code: ara
    operating-language-country: المملكة العربية السعودية
  * operating-language-character-encoding: 8859part6

    operating-language-name: Dansk
    operating-language-code: dan
    operating-language-country: '208'
 *  operating-language-character-encoding: Type Code

    operating-language-name: German
    operating-language-code: deu
    operating-language-country: '276'
 *  operating-language-character-encoding: 

 *  operating-language-name: polski
    operating-language-code: pol
    operating-language-country: '616'
 *  operating-language-character-encoding: 

  * operating-language-name: svenska
    operating-language-code: swe
    operating-language-country: '752'
    operating-language-character-encoding: '5'

[ReesePlews]

@HassanAkbar if you have time, could you examine this question? thank you

[ronaldtse]

@ReesePlews this is because of the contents of the MLGT Excel file:

[ronaldtse]

I think the MLGT ought to decommission the "sub-registers" and be integrated into ISO 19173...

[ReesePlews]

thanks @ronaldtse, i guess i never really think of them as truly sub-registers, but i dont know how you are integrating them here in geolex. they are stored as separate sheets in the excel MLGT workbook, (there is really no other way) at this time.

i have no problem in the future if they will be properly integrated into our 19173 SMART Terminology Register however we need to be able to keep some or all of this metadata for those "non-english" entries. meaning there may well need to be entry specific (unique) metadata link... like a link to a metadata record. probably it can be one link per entry... not sure why there would be more than one... not sure if we need linage for such metadata, that would be a lot of tracking, behind the scenes if the metadata were within the entry that may be easier than tracking/managing a link...

[ronaldtse]

@ReesePlews we can of course keep the metadata and link them to the concepts. We need to do lineage anyway. But the important part is to get rid of the "sub-registers" concept because it is contrary to what we need in a concept database...

[ReesePlews]

thank you @ronaldtse i agree the sub-register concept is not the direction we want to go, it is not needed given the structure of the revised 19135.

that said, if we end up processing another MLGT from the main excel repo then we will need to deal with this structure again. typically the MLGT is only released every three - four years, however since geolexica has become indispensable for the activities of TC211 members and others within the geospatial domain, there are often calls for published standards to be updated quicker. i hope we can move away from that sooner than later, thanks to the work of you and the team!

[ronaldtse]

Thank you @ReesePlews , hopefully by end of this year we will be able to migrate the Terms Repository...!