generated from IHE/supplement-template
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Added Unique Localized Text Catalog Identification section to volume 3.
- Loading branch information
1 parent
33d8816
commit 8ceac6c
Showing
2 changed files
with
28 additions
and
0 deletions.
There are no files selected for viewing
26 changes: 26 additions & 0 deletions
26
...ceps-content-module/tf3-ch-8.3.2.9.8-localized-text-catalog-identification.adoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
[#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. | ||
|
||
Text ids are unique within a device scope. However, <<acronym_pocd>> vendors usually use the same text catalog for several of their products. | ||
|
||
In order to reduce the effort for a <<actor_somds_consumer>> for managing individual lookup tables per <<actor_somds_provider>>, a lookup table that resolves the text ids for multiple <<actor_somds_provider>> from the same <<acronym_pocd>> vendor is desirable for a <<actor_somds_consumer>>. | ||
|
||
.R0709 | ||
[sdpi_requirement#r0709,sdpi_req_level=should] | ||
**** | ||
A <<actor_somds_provider>> that has implemented the *<<acronym_biceps>> LOCALIZATION SERVICE* should provide a unique text catalog identifier in the *pm:MdsDescriptor+++<wbr/>+++/ProductionSpecification*. | ||
NOTE: The unique text catalog identifier can be an *urn* of type *uuid* or *oid*, e. g. *"urn:oid:1.3.6.1.4.1.1234.4.1.2.1"*. | ||
**** | ||
|
||
.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 along with the unique text catalog identifier in the *pm:MdsDescriptor+++<wbr/>+++/ProductionSpecification*. | ||
NOTE: The version number can be part of unique text catalog identifier, e. g. the last sub-node of the *OID*. In this case, it is not necessary that the <<actor_somds_provider>> provides a text catalog verion number in the *pm:MdsDescriptor+++<wbr/>+++/ProductionSpecification*. | ||
**** | ||
|
||
*TBD*: #which codes can be used for the text catalog id and the version in the ProductSpecification? Do we need new codes? Can we define SDPi OIDs or some similar for that?# |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters