View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0010322 | 10000-003: Address Space | Spec | public | 2025-05-09 11:02 | 2025-05-09 13:11 |
Reporter | Alexander Allmendinger | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | always |
Status | new | Resolution | open | ||
Summary | 0010322: Clarification on DataTypeDefinition requirements for non-custom DataTypes | ||||
Description | The specification currently states:
After discussion and thinking about the different use cases I would even say, that any of these Types need to have the DataTypeDefinition Attribute, even the ones defined in future OPC UA Core spec versions. Since OPC UA Clients will use this attribute to learn the datatypes there would not be interoperability between a server based on a newer specification with new structures that an older client doesn't know about but has a generic structure handling. Note, this just looks like a spec issue since the most common demo servers have the DataTypeDefinitions set also for all namespace 0 DataTypes. | ||||
Tags | No tags attached. | ||||
Commit Version | |||||
Fix Due Date | |||||
|
I have recently been working on such a generic structure handling and also encountered this section, my impression was that this sentence was more informative:
The following sentences:
|
Date Modified | Username | Field | Change |
---|---|---|---|
2025-05-09 11:02 | Alexander Allmendinger | New Issue | |
2025-05-09 13:11 | Frank Fischer | Note Added: 0022716 |