View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0009018 | 10000-005: Information Model | Spec | public | 2023-06-20 15:12 | 2023-06-20 19:29 |
Reporter | Jim Luth | Assigned To | Jeff Harding | ||
Priority | normal | Severity | feature | Reproducibility | have not tried |
Status | closed | Resolution | fixed | ||
Product Version | 1.05.01 RC1 | ||||
Target Version | 1.05.03 RC1 | Fixed in Version | 1.05.03 | ||
Summary | 0009018: Need a way to express metadata for Key- Value pairs | ||||
Description | Part 14 makes extensive use of Key-Value pairs for configuration and suggest the use of vendor specific pairs but offers no way to express any metadata for the values (e.g. description, mandatory/optional, limits ...). | ||||
Tags | No tags attached. | ||||
Commit Version | 1.05.03 RC | ||||
Fix Due Date | |||||
related to | 0008062 | closed | Matthias Damm | 10000-014: PubSub | Need a way to express metadata for Key- Value pairs |
|
This is something we can expose similar to meta data for method arguments.
|
|
Added SupportedConfigurationProperties Folder to PubSubCapabilitiesType The Folder SupportedConfigurationProperties is the entry point for the description of configuration properties in the PubSub component KeyValuePair arrays. A configuration property is described by Variables with the following information: |
|
define a non-hierarchical reference to go from the instances and types directly to the metadata for the key-value pairs. |
|
Added SupportedPubSubProperty reference type, removed SupportedConfigurationProperties Folder from PubSubCapabilitiesType and added text on how to use the SupportedPubSubProperty reference type from key-value pair configuration properties to the description. |
|
We decided to move this generic reference type to Part 5 and use it in Part 14. We already reviewed the text that needs to be moved to Part 5. |
|
Added the HasKeyValueDescription ReferenceType Note: new conformance unit ''Base Info HasKeyValueDescription" proposed to be added. |
|
Agreed to changes in virtual F2F. |
Date Modified | Username | Field | Change |
---|---|---|---|
2023-06-20 15:12 | Jim Luth | New Issue | |
2023-06-20 15:12 | Jim Luth | Status | new => assigned |
2023-06-20 15:12 | Jim Luth | Assigned To | => Jeff Harding |
2023-06-20 15:12 | Jim Luth | Issue generated from: 0008062 | |
2023-06-20 15:12 | Jim Luth | Note Added: 0019566 | |
2023-06-20 15:12 | Jim Luth | Note Added: 0019567 | |
2023-06-20 15:12 | Jim Luth | Note Added: 0019568 | |
2023-06-20 15:12 | Jim Luth | Note Added: 0019569 | |
2023-06-20 15:12 | Jim Luth | Note Added: 0019570 | |
2023-06-20 15:12 | Jim Luth | Relationship added | related to 0008062 |
2023-06-20 15:13 | Jim Luth | Project | 10000-014: PubSub => 10000-005: Information Model |
2023-06-20 15:13 | Jim Luth | Commit Version | => 1.05.03 RC |
2023-06-20 15:14 | Jim Luth | Note Edited: 0019570 | |
2023-06-20 19:07 | Jeff Harding | Status | assigned => resolved |
2023-06-20 19:07 | Jeff Harding | Resolution | open => fixed |
2023-06-20 19:07 | Jeff Harding | Fixed in Version | => 1.05.03 |
2023-06-20 19:07 | Jeff Harding | Note Added: 0019578 | |
2023-06-20 19:29 | Jim Luth | Status | resolved => closed |
2023-06-20 19:29 | Jim Luth | Note Added: 0019583 |