View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0001400 | 10000-004: Services | public | 2010-10-14 12:42 | 2012-02-09 22:41 | |
Reporter | Matthias Damm | Assigned To | Matthias Damm | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Fixed in Version | 1.02 | ||||
Summary | 0001400: Use of timestamp in DataValue for bad status is inconsistent | ||||
Description | 7.19.2 DataChangeNotification parameter 7.7 DataValue It makes no sense to define a special behaviour for the DataChangeNotification and it makes sense to use at least the server timestamp | ||||
Tags | No tags attached. | ||||
Commit Version | |||||
Fix Due Date | |||||
related to | 0001825 | closed | Matthias Damm | Table 122 - DataValue: Bad StatusCode should mean to NOT use the Value? |
|
Changed DataValue description regarding timestamps in DataChangeNotification definition to be consistent with DataValue structure definition. The source timestamp is valid for bad or uncertain status. Change is part of the draft version "OPC UA Part 4 - Services Draft 1.02.02 Body.doc" |
|
Discussed in Walldorf |
Date Modified | Username | Field | Change |
---|---|---|---|
2010-10-14 12:42 | Matthias Damm | New Issue | |
2011-02-14 06:21 | Randy Armstrong | Status | new => assigned |
2011-02-14 06:21 | Randy Armstrong | Assigned To | => Matthias Damm |
2011-03-12 14:33 | Matthias Damm | Status | assigned => resolved |
2011-03-12 14:33 | Matthias Damm | Resolution | open => fixed |
2011-03-12 14:33 | Matthias Damm | Note Added: 0002382 | |
2011-05-24 08:54 | Randy Armstrong | Status | resolved => closed |
2011-05-24 08:54 | Randy Armstrong | Note Added: 0002758 | |
2012-01-06 20:05 |
|
Relationship added | related to 0001825 |
2012-02-09 22:41 | Jim Luth | Fixed in Version | => 1.02 |