View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006154 | 10000-019: Dictionary Reference | Spec | public | 2020-10-15 07:08 | 2022-06-22 13:32 |
| Reporter | Matthias Damm | Assigned To | Jeff Harding | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Target Version | 1.05.02 | Fixed in Version | 1.05.02 RC1 | ||
| Summary | 0006154: Clarification for use of Dictionary Object below Server | ||||
| Description | We define a Dictionary Object below Server of type DictionaryFolderType. The intention of this folder was to expose complete dictionaries in an information management server (not in every single device). We see now that this folder is used to provide a list of DictionaryEntries below this folder that are used by a specification e.g. PADIM. This looks like a miss-use to me but it is legal from an OPC UA information model point of view. We should at least clarify if this is an expected use-case or if this is not the intention. This would influence the assumption about the availability of this folder in embedded systems. | ||||
| Tags | No tags attached. | ||||
| Commit Version | |||||
| Fix Due Date | |||||
|
|
There is no description of how the Dictionary reference can have a dangling target node. |
|
|
I think we do not have a problem with dangling target nodes / references. My assumption was that a server is using HasDictionaryEntry from a server specific instance / type e.g. a temperature measurement variable to the corresponding DictionaryEntryType Object. The target node would be always present. The way we defined the attributes of the DictionaryEntryType Object node makes it easy for the server to provide the node. My assumption was that the Dictionaries object is not present in normal servers. The essential part is "only present if the Server exposes the hierarchy of the referenced dictionaries" In addition we defined the namespace for IRDI based DictionaryEntryType Objects: "http://opcfoundation.org/UA/Dictionary/IRDI" The PA-DIM spec is referring to DictionaryEntryType Objects from this namespace and PA-DIM UANodeset is referring to the IRDI OPC UA namespace (this is still inline with my assumptions). In addition, PA-DIM provides a UANodeset for the IRDI OPC UA namespace that contains the DictionaryEntryType Objects they are using. To have a parent node for these objects, they included the Dictionaries Object defined by OPC UA as parent. This is maybe necessary to get a consistent model for PA-DIM but the reality is that server implementation simply load both UANodesets and as a result, all of these servers expose the Dictionaries Object that references all DictionaryEntryType Objects in a flat list. |
|
|
Not for 1.05 RC but target to complete before final release. |
|
|
Added clarifying statement |
|
|
Agreed to changes edited in Munich F2F. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2020-10-15 07:08 | Matthias Damm | New Issue | |
| 2020-10-20 15:34 | Jim Luth | Assigned To | => Jeff Harding |
| 2020-10-20 15:34 | Jim Luth | Status | new => assigned |
| 2020-10-20 15:36 | Jeff Harding | Note Added: 0013072 | |
| 2020-10-29 07:39 | Matthias Damm | Note Added: 0013087 | |
| 2021-05-04 16:05 | Jeff Harding | Note Added: 0014320 | |
| 2022-05-18 19:04 | Jeff Harding | Target Version | => 1.05.02 |
| 2022-06-01 18:48 | Jeff Harding | Status | assigned => resolved |
| 2022-06-01 18:48 | Jeff Harding | Resolution | open => fixed |
| 2022-06-01 18:48 | Jeff Harding | Fixed in Version | => 1.05.02 |
| 2022-06-01 18:48 | Jeff Harding | Note Added: 0016785 | |
| 2022-06-22 13:32 | Jim Luth | Status | resolved => closed |
| 2022-06-22 13:32 | Jim Luth | Fixed in Version | 1.05.02 => 1.05.02 RC1 |
| 2022-06-22 13:32 | Jim Luth | Note Added: 0016986 |
