Added Unique Localized Text Catalog Identification section to volume 3 #344
Conversation
|
@d-gregorczyk: if you agree with my proposal, we need to define the codes for entries in the ProductionSpecification for the text catalog id and version. I have not found appropriate codes in the Rosetta DB. There are two codes which may fit for the text catalog id ... but I am not sure: Status: Published Status: Published Howerver, I didn't find anything for the text catalog version. |
|
SDPi Friday 2024.11.29 Review -
@PeterKranich - Propose a definition for the _TEXT_CAT term. |
Added issue entry to CHANGE LOG
|
SDPi Friday 2024.12.13 Review - Discussion issues included:
|
| @@ -0,0 +1,32 @@ | |||
| [#vol3_clause_localized_text_catalog_identification] | |||
There was a problem hiding this comment.
In all those requirements, I do not see restrictions that help increasing or establishing interoperability. It currently boils down to "there is a code one can use in production specification to indicate use of text catalogs", however, there is no way of a general procedure as to how the use of text catalogs is globally applicable to all manufacturers. From this it follows that the requirements displayed herein have no effect of interoperability between manufacturers. Hence, I do not see a reason to craft requirements at all. We may rather sell this chapter as a good practice in case text catalogs are used.
"You are encouraged to signify the use of text catalogs by adding a production specification item to the affected MDSs"
| [#vol3_clause_localized_text_catalog_identification] | ||
| ====== Unique Localized Text Catalog Identification | ||
|
|
||
| In <<acronym_biceps>>, localized texts for parameter labels, alert strings, enumerations, etc. can be retrieved with the provided *LocalizedText/@ref* (text id) and language code from the <<acronym_biceps>> Localization Service. |
There was a problem hiding this comment.
| In <<acronym_biceps>>, localized texts for parameter labels, alert strings, enumerations, etc. can be retrieved with the provided *LocalizedText/@ref* (text id) and language code from the <<acronym_biceps>> Localization Service. | |
| In <<acronym_biceps>>, localized texts for parameter labels, alert strings, enumerations, etc. can be retrieved with the provided *LocalizedText/@Ref* (text id) and language code from the <<acronym_biceps>> Localization Service. | |
| [#vol3_clause_localized_text_catalog_identification] | ||
| ====== Unique Localized Text Catalog Identification | ||
|
|
||
| In <<acronym_biceps>>, localized texts for parameter labels, alert strings, enumerations, etc. can be retrieved with the provided *LocalizedText/@ref* (text id) and language code from the <<acronym_biceps>> Localization Service. |
There was a problem hiding this comment.
| In <<acronym_biceps>>, localized texts for parameter labels, alert strings, enumerations, etc. can be retrieved with the provided *LocalizedText/@ref* (text id) and language code from the <<acronym_biceps>> Localization Service. | |
| In <<acronym_biceps>>, localized texts for parameter labels, alert strings, enumerations, etc. can be retrieved with the provided *LocalizedText/@ref* (text id) and language code from the <<acronym_biceps>> LOCALIZATION SERVICE. | |
| .R0710 | ||
| [sdpi_requirement#r0710,sdpi_req_level=should] | ||
| **** | ||
| A <<actor_somds_provider>> that has implemented the *<<acronym_biceps>> LOCALIZATION SERVICE* and supports versioning of the text catalog should provide a unique version number concatenated with the unique text catalog identifier and separated from the unique text catalog identifier by two colons (*"::"*) in the *pm:MdsDescriptor+++<wbr/>+++/ProductionSpecification+++<wbr/>+++/pm:ProductionSpec*. |
There was a problem hiding this comment.
This requirement is too weak to have a significant effect on interoperability.
|
|
||
| NOTE: *"urn:oid:1.3.6.1.4.1.1234.4.1.2.1::v1.2.2*" is an example of a unique text catalog id with a concatenated text catalog version. | ||
|
|
||
| NOTE: The version number can be part of unique text catalog identifier, e. g. the last sub-node of the *OID*. In this case, the requirement does not apply. |
There was a problem hiding this comment.
According to the requirement, that is exactly how it is not supposed to be modelled as such an identifier would lack the double colon, right?
| .R0711 | ||
| [sdpi_requirement#r0711,sdpi_req_level=shall] | ||
| **** | ||
| A <<actor_somds_provider>> that provides a unique text catalog identifier in the *pm:MdsDescriptor+++<wbr/>+++/pm:ProductionSpecification* list but does not support versioning of the text catalog shall provide a new unique text catalog identifier for each new version of the text catalog. |
There was a problem hiding this comment.
"A provider that does not support versioning of text catalogs shall provide a new identifier for each new version" sounds odd. If versioning is not supported, there is no need to generate new identifiers.
📑 Description
Added Unique Localized Text Catalog Identification section to volume 3.
Proposal is to add the text catalog id and version to the MDS/ProductionSpecification.
☑ Mandatory Tasks
The following aspects have been respected by the pull request assignee and at least one reviewer: