View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0009308 | 10000-004: Services | Spec | public | 2023-12-12 18:10 | 2024-03-19 20:41 |
Reporter | Jim Luth | Assigned To | Matthias Damm | ||
Priority | normal | Severity | feature | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Fixed in Version | 1.05.04 RC1 | ||||
Summary | 0009308: External localization of Event Messages | ||||
Description | In the Harmonization Working Group several CSs have showed interst in a feature that allows:
For example, a RecourceId could represent the "template" for different lanuages like The event would provide the event field RecourceId + the data to construct the message (e.g. {„System“, „Aggregat A1B2D4“, 0x80004005}). That allows higher-level applications to store the message and potentially even provide additional languages at a later time. In addition, a standardized way to expose the "templates" behind the RecourceId should be provided. Not neccecarily all servers would support this. We should consider making the RecouceId a reasonable data type to easily access that information, e.g. QualifiedName or maybe NodeId. | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
Commit Version | 1.05.04 RC | ||||
Fix Due Date | 2024-01-15 | ||||
related to | 0005487 | closed | Jeff Harding | Feature Requests | External localization of Event Messages |
|
Discussion during Dallas Meeting Create a structure containing Each Event Field that needs to be localized need a counterpart with that structure. Each Variable need a counterpart with that structure. We should define a best practice for names (e.g. Message + MessageResourceId). In addition, server provides StringTable with the templates for resources clients can access. That should solve the direct communication part. Could potentially also be used for Publisher, putting string tables into the Metadata. Another issue that came up during discussion: What is the big picture? How is localization managed in a system with many servers? What about aggrgating servers. |
|
Notes from 2020-07-28 Telecon: We had a long discussion and think we came to an elegant solution that will work in all places the LocalizedText datatype is used. We will define our own locale for "UA machine readable" and store a Uuencoded UA binary structure in the Text string that contains all of the data necessary for the Client to constrict the final string based on the string fragments and replaceable parameters in the UA binary structure. Further details need to be worked out and discussed further. |
|
discuss this issue in UA working group call - proposed a solution using a specific locale - attached slides help illustrate it |
|
Thinking about this a bit more I think we can introduce this as follows: With this approach it is not limited to events and would apply to all uses of LocalizedText in all parts. Specifically if a session is established with the special multiple language LocaleId as the first priority then all LocalizedText will be returned by the server as JSON encoded arrays of all available languages for that LocalizedText Variable. Existing client are not affected as they will be requesting specific localeIds. |
|
These notes outline 2 different mechanisms for providing localized text messages. We should consider the pros and cons of each - events-only vs all localized text, performance, efficiency, scalability, complexity, resource requirements, etc. |
|
Commit Date 2023-09-01 |
|
All text in Part 3 and Part 4 has been reviewed and accepted. Cloning this issue to both Parts for final integration into editor drafts. |
|
Added following text received as input: 5.4 Locale Negotiation |
|
Agreed to changes edited in Dallas F2F. |
Date Modified | Username | Field | Change |
---|---|---|---|
2023-12-12 18:10 | Jim Luth | New Issue | |
2023-12-12 18:10 | Jim Luth | Status | new => assigned |
2023-12-12 18:10 | Jim Luth | Assigned To | => Matthias Damm |
2023-12-12 18:10 | Jim Luth | Issue generated from: 0005487 | |
2023-12-12 18:10 | Jim Luth | Note Added: 0020513 | |
2023-12-12 18:10 | Jim Luth | Note Added: 0020514 | |
2023-12-12 18:10 | Jim Luth | Note Added: 0020515 | |
2023-12-12 18:10 | Jim Luth | Note Added: 0020516 | |
2023-12-12 18:10 | Jim Luth | Note Added: 0020517 | |
2023-12-12 18:10 | Jim Luth | Note Added: 0020518 | |
2023-12-12 18:10 | Jim Luth | Note Added: 0020519 | |
2023-12-12 18:10 | Jim Luth | Relationship added | related to 0005487 |
2023-12-12 18:11 | Jim Luth | Project | Feature Requests => 10000-004: Services |
2023-12-12 18:15 | Jim Luth | Category | Api Change => Spec |
2023-12-12 18:15 | Jim Luth | Commit Version | => 1.05.04 RC |
2023-12-12 18:15 | Jim Luth | Fix Due Date | => 2024-01-15 |
2024-03-18 01:33 | Matthias Damm | Status | assigned => resolved |
2024-03-18 01:33 | Matthias Damm | Resolution | open => fixed |
2024-03-18 01:33 | Matthias Damm | Note Added: 0020926 | |
2024-03-19 20:41 | Jim Luth | Status | resolved => closed |
2024-03-19 20:41 | Jim Luth | Fixed in Version | => 1.05.04 RC1 |
2024-03-19 20:41 | Jim Luth | Note Added: 0020947 |