a couple of minor maintenance items on the https://www.isotc211.org/ website

[ReesePlews]

hello @ronaldtse @strogonoff @ribose-jeffreylau ( cc: @ejbleys )

there are a couple of minor maintenance issues (known at this time) on the TC211 Resources page ( https://www.isotc211.org )

i do not know if this page requires some "compilation" after edits are made so i am filing a ticket. if you can tell or show me the procedures for making these changes i will take care of any future minor issues. thank you.

1) name change of the XMG...

i did not know the name of the XMG "Xml Maintenance Group" has changed after the Wuhan Plenary.

the new name (from TC211 Resolution 2025-05) is:
Implementation Schema Maintenance Group (ISMG)

on the https://www.isotc211.org page

could you please update the following descriptive instances shown below (red boxes)

i dont think actual repository name should be changed, as there could be some procedural code here and offsite that makes use of that repository path. just the descriptive text will be enough.

2) removal of the TMG "Multi-Lingual Glossary of Terms (MLGT) spreadsheet releases" link

the TMG is no longer publicly distributing the excel spreadsheet releases of the MLGT. please remove this link and text shown in the red box.

[strogonoff]

@ReesePlews

What should be our strategy of making sure the preexisting references to “XMG” and “XML Maintenance Group” continue to make sense for future readers?

For example, this mentions “Typo reported by XMG”:

isotc211.github.io/2005/gmi/dataQualityInformation.xsd

Line 6 in d38bfdf

<xs:documentation>2012-12-08: Documentation of LE_ProcessStepReport_Type. Typo reported by XMG: "occured" replaced by "occurred".</xs:documentation>

Since it is not possible to update all references (some of them are on external resources, for one), I assume we should note the previously used name somewhere.

[strogonoff]

The link to MLGT spreadsheets was removed.

[ReesePlews]

@ReesePlews

What should be our strategy of making sure the preexisting references to “XMG” and “XML Maintenance Group” continue to make sense for future readers?

hello @strogonoff my intention was to only change the descriptions of the group name. changing the links would just be too much to deal with, in my opinion. also, that decision should be given more consideration, if proposed, which i was not proposing at this time. the xmg is not my group, so i was just reporting these minor name change descriptions.

i hope that is clear.

thanks for removing the TMG link.

[strogonoff]

@ReesePlews

hello @strogonoff my intention was to only change the descriptions of the group name. changing the links would just be too much to deal with, in my opinion. also, that decision should be given more consideration, if proposed, which i was not proposing at this time. the xmg is not my group, so i was just reporting these minor name change descriptions.

I understand that. My point is that if we update group’s name everywhere, without leaving any notice about the previous name, then any external links will be confusing. Imagine you navigate a link to XMG and you see a website for ISMG; now you will be stuck thinking whether the link was correct.

The most obvious solution is to update the name and add a note mentioning the previous name.

It would go a long way towards not gaslighting people in a way.

[ReesePlews]

thanks @strogonoff that is a lot more work than i envisioned this change would be.

as this is not my advisory group, i cannot be the one to request that much work from you. please talk with @ronaldtse and @ejbleys to come up with a suitable solution. i was only relaying something someone noticed in the meeting that the group name had changed and the website was not updated. thank you.

[strogonoff]

OK. It’s not a lot of work to add a small note, but I would like to confirm the phrasing. cc @ronaldtse

[strogonoff]

@ronaldtse

I’m thinking of adding something like this:

ISO/TC 211 Implementation Schema Maintenance Group (ISMG) used to be known as ISO/TC 211 XML Maintenance Group (XMG) before 2025.

somewhere closer to the bottom of the main page and/or the about page.

If no objections are raised by tomorrow, I will do this as part of this issue.