View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005144 | 10000-007: Profiles | Spec | public | 2019-10-14 15:02 | 2020-09-18 17:03 |
| Reporter | David Levine | Assigned To | Paul Hunkar | ||
| Priority | high | Severity | major | Reproducibility | have not tried |
| Status | assigned | Resolution | open | ||
| Summary | 0005144: Create a facet for version number and model change events so that it can be an individually identifiable feature | ||||
| Description | The functionality is already defined but is optional and not separately tested for compliance. By creating a facet it can be tested, can be required by companion specs, and can also be in the server as a supported facet so that a client can read out the list of supported facets to identify it. | ||||
| Tags | No tags attached. | ||||
| Commit Version | |||||
| Fix Due Date | |||||
|
|
There is a conformance unit for it, the conformance unit can be included in companion specification (and has been). Does it really need an facet all it's own? Should it be included in some existing facet as optional |
|
|
I should be able to start working on this before the end of 2020 - product release pressures have kept me busy. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-10-14 15:02 | David Levine | New Issue | |
| 2019-10-22 15:51 | Jim Luth | Assigned To | => Paul Hunkar |
| 2019-10-22 15:51 | Jim Luth | Status | new => assigned |
| 2020-09-17 05:47 | Paul Hunkar | Status | assigned => feedback |
| 2020-09-17 05:47 | Paul Hunkar | Note Added: 0012891 | |
| 2020-09-18 17:03 | David Levine | Note Added: 0012956 | |
| 2020-09-18 17:03 | David Levine | Status | feedback => assigned |
