View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001253 | 10000-003: Address Space | public | 2010-06-08 22:31 | 2011-03-16 13:42 | |
| Reporter | Matthias Damm | Assigned To | Wolfgang Mahnke | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Fixed in Version | 1.02 | ||||
| Summary | 0001253: Clarify ModelChange events | ||||
| Description | Part 3 states that ModelChange events and the NodeVersion property are bound to each other but the spec does not define which nodes are included in a model change event. From my point of view it makes no sense to include all components of a condition into a model change event if a new condition is created. We discussed this in the UA phone conference on June 8, 2010 and agreed on to add the clarification that only nodes that have a NodeVersion property are included in ModelChange events. | ||||
| Tags | No tags attached. | ||||
| Commit Version | |||||
| Fix Due Date | |||||
|
|
Specified that Nodes having a NodeVersion shall generate ModelChangeEvents, others not. Also defined that this does not apply for semantic change events (needs to be discussed if this is OK) Doc Version 1.02.05 |
|
|
Reviewed in F2F 2011-03-16 |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2010-06-08 22:31 | Matthias Damm | New Issue | |
| 2010-11-16 18:42 | Randy Armstrong | Status | new => assigned |
| 2010-11-16 18:42 | Randy Armstrong | Assigned To | => Wolfgang Mahnke |
| 2011-03-02 08:54 | Wolfgang Mahnke | Status | assigned => resolved |
| 2011-03-02 08:54 | Wolfgang Mahnke | Fixed in Version | => 1.02 |
| 2011-03-02 08:54 | Wolfgang Mahnke | Resolution | open => fixed |
| 2011-03-02 08:54 | Wolfgang Mahnke | Note Added: 0002304 | |
| 2011-03-16 13:42 | Randy Armstrong | Status | resolved => closed |
| 2011-03-16 13:42 | Randy Armstrong | Note Added: 0002423 |
