Multi-language support for the openEHR terminology
Raise
Analysis
Raise
Analysis
Description
Activity
Show:
Sebastian Iancu December 13, 2022 at 10:37 PM
This was most likely done in Release 2.0.0, having a separate file per language.
Diego Bosca June 24, 2016 at 11:06 AM
Agree. In the end probably not all terms will be translated, but a mechanism to define translations is indeed needed.
Done
Details
Details
Reporter
Pablo Pazos
Pablo PazosLabels
Components
Priority
MajorCreated June 22, 2016 at 7:31 PM
Updated December 13, 2022 at 10:37 PM
Resolved December 13, 2022 at 10:37 PM
Some time ago we discussed different issues with the openEHR terminology spec and XML representation: https://openehr.atlassian.net/wiki/display/spec/openEHR+Terminology
open issues are:
how to improve multiple-language representation in the XML (XSD)
if one or multiple files should be used
discuss if we should add units to the openEHR terminology (or reference the UCUM ones)
Current XMLs:
https://github.com/openEHR/specifications/blob/master/publishing/architecture/computable/terminology/terminology.xml
https://github.com/openEHR/arch_ed-dotnet/blob/master/ArchetypeEditor/Terminology/terminology.xml
this is a related issue https://openehr.atlassian.net/browse/SPECPR-3