Add Belgian German to dialect-map

[JorisLemay]

Fix

Please add Belgian German in the language-refset-dialect-map.properties file. Vielen Dank für Ihre Aufmerksamkeit für unsere Dreisprachigkeit :) .

suggestion for fix in src/main/resources/language-refset-dialect-map.properties add:

# 120961000172108 | Belgian German language reference set (foundation metadata concept)|
# Combined as: de-be
120961000172108=be

Error/Warning

Command and warning.

$ java --add-opens java.base/java.lang=ALL-UNNAMED -Xms4g \
    -jar                   ./snomed-tools/snomed-to-owl-toolkit/snomed-owl-toolkit-5.3.0-executable.jar \
    -rf2-to-owl            ./snomed-tools/sct-releases/sct-int_and_be-ontology-2025-01-04_13-56-11.owl \
    -rf2-snapshot-archives ./snomed-tools/sct-releases/SnomedCT_InternationalRF2_PRODUCTION_20250101T120000Z.zip,\
./snomed-tools/sct-releases/SnomedCT_ManagedServiceBE_PRODUCTION_BE1000172_20241215T120000Z.zip
 
2025-01-04 12:59:05,518 [WARN  ] [main] org.snomed.otf.owltoolkit.ontology.OntologyService - Please add language reference set 120961000172108 to language-refset-dialect-map.properties and recompile. The dialect ISO code could not be appended to the annotations because it was not found.

[pgwilliams]

😄 Your phrase was worth the effort of translating there; you're welcome. And thanks for providing the config required.

Committed to our develop branch bc22531

I'll have a chat with the team tomorrow about cutting release 5.5 as part of our current round of development work.

[pgwilliams]

@JorisLemay were you able to get going with a locally modified properties file, or should we add capability / instructions on how to do that? It seems like a problem that any new edition is going to encounter.

[JorisLemay]

@JorisLemay were you able to get going with a locally modified properties file, or should we add capability / instructions on how to do that? It seems like a problem that any new edition is going to encounter.

German SCT is not currently in the picture, but it would definitely be nice to include once it’s ready. The principal issue here is managing the requirements for new editions effectively. Here are my proposed options to address this:
1. Add a “Definition of Done” or “Feature Checklist”: Incorporate a check for supported languages (like German SCT) into the owl-toolkit release process. This ensures language compatibility is verified before finalizing a release.
2. Make Language Configurable: Extend the configuration options in a par file used with the release JAR. This could include feature flags for supported languages, OWL format options, or other related configurations to improve flexibility and adaptability.

[kaicode]

I agree that it would be nice to be able to add language refsets without recompiling the jar file.