This is the final step before publishing a version of IWXXM to schemas.wmo.int after completion of FT approval procedures. The corresponding PR for the model is at https://github.com/wmo-im/iwxxm-modelling/pull/17.
Basically this involves removal of references to "Release Candidate 2 or RC2" from the UML model (which affects the HTML documents and XMI export), schemas and examples.
There was a glitch: That WAFSSigWxFC.xsd showed a couple of more differences than removal of "RC2". A closer inspection revealed that these were typos should already be in the FT2021-2RC2 commit but in fact they weren't.
Assuming we arrived at a conclusion on how to deal with the glitch, we can still not merge the FT2021-2 branch into the master branch, as we will need to remove the RDF files first. We cannot do this in this PR as the CI script will automatically download RDF files from the codes registry for checking, but as some of the code tables have changed or are new and will only be published with the schemas at the same time, validation carried out by the CI script will fail. We may want to figure out a better way to deal with this "chicken and egg" issue but at the mean time we will have to handle it manually.
This is the final step before publishing a version of IWXXM to schemas.wmo.int after completion of FT approval procedures. The corresponding PR for the model is at https://github.com/wmo-im/iwxxm-modelling/pull/17.
Basically this involves removal of references to "Release Candidate 2 or RC2" from the UML model (which affects the HTML documents and XMI export), schemas and examples.
There was a glitch: That WAFSSigWxFC.xsd showed a couple of more differences than removal of "RC2". A closer inspection revealed that these were typos should already be in the FT2021-2RC2 commit but in fact they weren't.
Assuming we arrived at a conclusion on how to deal with the glitch, we can still not merge the FT2021-2 branch into the master branch, as we will need to remove the RDF files first. We cannot do this in this PR as the CI script will automatically download RDF files from the codes registry for checking, but as some of the code tables have changed or are new and will only be published with the schemas at the same time, validation carried out by the CI script will fail. We may want to figure out a better way to deal with this "chicken and egg" issue but at the mean time we will have to handle it manually.