View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006590 | 10000-014: PubSub | Spec | public | 2021-03-09 13:37 | 2023-06-22 18:06 |
| Reporter | Matthias Damm | Assigned To | Matthias Damm | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | unable to reproduce | ||
| Summary | 0006590: Content of broker ua-metadata messages not precisely defined | ||||
| Description | Both MQTT and AMQP transports define the content of a “ua-metadata” body as UA Binary or JSON encoded DataSetMetaData Message. This is not concrete enough. I assume this refers to
| ||||
| Tags | No tags attached. | ||||
| Commit Version | |||||
| Fix Due Date | |||||
|
|
Add concrete references to the JSON disovery message and UADP discover message. |
|
|
This is already fixed by the introduction of MessageTypes and topic tree |
|
|
Accepted in Virtual F2F |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2021-03-09 13:37 | Matthias Damm | New Issue | |
| 2021-03-09 17:38 | Matthias Damm | Assigned To | => Matthias Damm |
| 2021-03-09 17:38 | Matthias Damm | Status | new => assigned |
| 2021-03-09 17:40 | Matthias Damm | Note Added: 0014018 | |
| 2023-06-21 21:01 | Matthias Damm | Status | assigned => resolved |
| 2023-06-21 21:01 | Matthias Damm | Resolution | open => unable to reproduce |
| 2023-06-21 21:01 | Matthias Damm | Note Added: 0019637 | |
| 2023-06-22 18:06 | Randy Armstrong | Status | resolved => closed |
| 2023-06-22 18:06 | Randy Armstrong | Note Added: 0019655 |
