View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002390 | 10000-003: Address Space | public | 2013-02-21 21:55 | 2013-08-06 16:39 | |
| Reporter | Assigned To | Wolfgang Mahnke | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | won't fix | ||
| Summary | 0002390: 8.72.6 GeneralModelChangeEventType.Changes property length clarification | ||||
| Description | CMPWG Feb-21-2013: Can the "Changes" property be zero-length? Actually, we think not. We propose adding text (also to Part 5 6.4.32) to say something like: "The 'Changes' property must contain 1 or more entries." You could possibly state that if 0-entries is intended then to use the BaseModelChangeEventType instead. | ||||
| Tags | No tags attached. | ||||
| Commit Version | |||||
| Fix Due Date | |||||
| related to | 0002391 | closed | Wolfgang Mahnke | 10000-005: Information Model | 6.4.32 'Changes' property should be 1 or more in length |
|
|
This issue is addressed in 0002391 and resolved in Part 5. We do not need to duplicate all information from Part 3 and Part 5. Part 5 seeems more appropriate as it defines the data structures. |
|
|
agreed to no-fix in telecon. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2013-02-21 21:55 |
|
New Issue | |
| 2013-02-21 21:59 |
|
Relationship added | related to 0002391 |
| 2013-03-12 17:42 | Jim Luth | Status | new => assigned |
| 2013-03-12 17:42 | Jim Luth | Assigned To | => Wolfgang Mahnke |
| 2013-07-09 15:49 | Wolfgang Mahnke | Status | assigned => resolved |
| 2013-07-09 15:49 | Wolfgang Mahnke | Resolution | open => won't fix |
| 2013-07-09 15:49 | Wolfgang Mahnke | Note Added: 0004764 | |
| 2013-08-06 16:39 | Jim Luth | Status | resolved => closed |
| 2013-08-06 16:39 | Jim Luth | Note Added: 0004900 |
