-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added Unique Localized Text Catalog Identification section to volume 3 #344
base: master
Are you sure you want to change the base?
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree it is more an optimization which helps the consumers when they have to manage devices which all use the same text catalog.
Where would you place recommendations? Also in Vol 3 same section?
...oc/volume3/biceps-content-module/tf3-ch-8.3.2.9.8-localized-text-catalog-identification.adoc
Outdated
Show resolved
Hide resolved
[#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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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. | |
...oc/volume3/biceps-content-module/tf3-ch-8.3.2.9.8-localized-text-catalog-identification.adoc
Outdated
Show resolved
Hide resolved
...oc/volume3/biceps-content-module/tf3-ch-8.3.2.9.8-localized-text-catalog-identification.adoc
Outdated
Show resolved
Hide resolved
...oc/volume3/biceps-content-module/tf3-ch-8.3.2.9.8-localized-text-catalog-identification.adoc
Outdated
Show resolved
Hide resolved
Co-authored-by: David Gregorczyk <[email protected]>
📑 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: