Unique identification of text catalog

[PeterKranich]

In BICEPS, localized texts for parameter labels, alert strings, enumerations, etc. can be retrieved from the Localization Service with the provided @ref (text id) and language. Text ids are unique within a device's scope. However, device vendors usually use the same text catalogs and therefore, the same text ids and text strings for multiple products in their portfolio.

In order to reduce the effort for a SDC consumer for managing an individual lookup table per device (e. g. 7000 infusion pumps!), a lookup table that resolves the text ids for multiple devices from the same vendor shall be supported.

Change proposal:

• Text catalog of a device on MDS level shall have a globally unique identifier (e. g. OID)
• Text catalog shall also provide a version in order to detect "breaking changes" (e. g. text string for a text id has been changed between two versions. Adding new text ids or languages does not require a new version)
• Challenges for multi-MDS SDC providers has to be further discussed since multiple devices would share the same BICEPS localization service

[ToddCooper]

SDPi Workshop #3 2024.06.04:

1. General agreement on the need for this extension (pending possible future revision capability TBD)
2. SDPi Extension? Possibly a simple constraint on current localization service & related elements (vs. new elements)

@d-gregorczyk - Has this been discussed?

[ToddCooper]

SDPi Workshop #4 -

Perhaps part of the Localization service.
Still need to determine the best path forward.

[ToddCooper]

SDPi Workshop #4 -
Decision to keep in 2.0 and push History Service to 2.1