View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0002462 | 10000-011: Historical Access | Spec | public | 2013-04-25 14:52 | 2023-03-23 18:45 |
Reporter | Paul Hunkar | Assigned To | Paul Hunkar | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | reopened | ||
Product Version | 1.03 | ||||
Fixed in Version | 1.05.03 RC1 | ||||
Summary | 0002462: Events for Historical Changes | ||||
Description | There is a symantic change event, that notifies a client if somethign changed that a client should be aware of, such as an engineerng unit. There should also be a Historical Configuration Change Event. This event would be generate when either a historical nodes historical configuration is changed (added/deleted assigned to a different configuration). This event would allow a client to easily discover if an items historical configuration has changed. There are Audit events available for historical value changes, entering of Annotation and other changes. A client may also want to be able to obtain this same information in a more general manner. I.e. an event that disclose that either a historical value has been edited or an annotation has been entered for the historicalnode. | ||||
Tags | No tags attached. | ||||
Commit Version | |||||
Fix Due Date | |||||
related to | 0002077 | closed | Paul Hunkar | OPC UA specification monitoring mode does not account for historical data changes |
|
Possibly just add text to the spec to indicate the conditions that Semantic Change Events (or a subtype) should be generated. |
|
Added text to better explain when a sematic change event shall be generated, when a model change event and when audit events |
|
Reopened - Semantic Change bit/Event will not be overloaded for HA. Instead Audit Events need to be defined for Historical Configuration changes. |
|
Agreed to only generate Audit event (and model change events) |
|
Agreed to changes edited in Dallas meeting. |
Date Modified | Username | Field | Change |
---|---|---|---|
2013-04-25 14:52 | Paul Hunkar | New Issue | |
2013-09-10 16:29 | Jim Luth | Status | new => acknowledged |
2013-09-10 16:30 | Jim Luth | Note Added: 0004983 | |
2013-09-10 17:20 | Jim Luth | Relationship added | related to 0002077 |
2015-10-09 08:38 | Jim Luth | Project | Feature Requests => 10000-011: Historical Access |
2015-10-09 08:38 | Jim Luth | Category | (No Category) => Api Change |
2015-10-09 08:39 | Jim Luth | Assigned To | => Rod Stein |
2015-10-09 08:39 | Jim Luth | Status | acknowledged => assigned |
2015-10-09 08:39 | Jim Luth | Category | Api Change => Spec |
2015-10-09 08:39 | Jim Luth | Product Version | => 1.03 |
2015-10-09 08:39 | Jim Luth | Target Version | => 1.04 |
2017-01-17 16:44 | Rod Stein | Target Version | 1.04 => |
2017-10-31 15:55 | Jim Luth | Target Version | => ?.?? |
2022-11-29 06:13 | Paul Hunkar | Assigned To | Rod Stein => Paul Hunkar |
2023-01-02 22:35 | Paul Hunkar | Status | assigned => resolved |
2023-01-02 22:35 | Paul Hunkar | Resolution | open => fixed |
2023-01-02 22:35 | Paul Hunkar | Fixed in Version | => 1.05.03 RC1 |
2023-01-02 22:35 | Paul Hunkar | Note Added: 0018381 | |
2023-01-03 20:18 | Jim Luth | Status | resolved => feedback |
2023-01-03 20:18 | Jim Luth | Resolution | fixed => reopened |
2023-01-03 20:18 | Jim Luth | Status | feedback => assigned |
2023-01-03 20:19 | Jim Luth | Note Added: 0018402 | |
2023-01-16 17:35 | Paul Hunkar | Assigned To | Paul Hunkar => |
2023-01-17 15:26 | Paul Hunkar | Assigned To | => Paul Hunkar |
2023-03-23 18:44 | Paul Hunkar | Status | assigned => resolved |
2023-03-23 18:44 | Paul Hunkar | Note Added: 0019009 | |
2023-03-23 18:45 | Jim Luth | Status | resolved => closed |
2023-03-23 18:45 | Jim Luth | Note Added: 0019010 |