View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0009186 | Part 81: UAFX Connecting Devices and Information Model | Spec | public | 2023-10-06 15:37 | 2024-01-05 13:58 |
Reporter | Brian Batke | Assigned To | Georg Biehler | ||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | closed | Resolution | fixed | ||
Fixed in Version | 1.00.03 | ||||
Summary | 0009186: AssetVerificationType needs to specify BrowseName for ExpectedVerificationVariables | ||||
Description | The VerifyAsset method expects Key:Value pairs the ExpectedVerificationVariable, with the key being a BrowseName. However the AssetVerificationType (6.5.2) which is part of CM configuration used PortableNodeIdentifierValuePair. Since changing the type at this point would be a breaking change, it was agreed to clarify AssetVerificationType to specify that the key shall be the BrowseName of the expected verification variable (I suppose it needs to be a "PortableQualifiedName"?) Also consider clarifying the associated structure in Appendix F (Table F.20) | ||||
Tags | No tags attached. | ||||
|
in section 6.15.2 "ExpectedVerificationVariables and ExpectedAdditionalVerificationVariables hold the variables to be verified for compatibility and/or identity. If a PortableRelativePath is specified, the path shall be relative to the expected Asset." |
|
The ExpectedVerificationVariables in the asset are from a fixed list in the method definition - all of which have a fixed browsename that is in Namespace a well defined namespace (i.e. DI or AC) - so these can be hardcoded to a certain extent - I.e this is the only list note: the same parameter name is used in the FE verify method, but in that case it is a list of NodeIds not browsenames. On the configuration side - the structure allows a browsename to be entered and in general for this paremeter that is all that should be provided - propose just to add text explaining that this should always be a browse path |
|
Paul made a text proposal, let's discuss in the meeting about the final text. |
|
reviewed change in call, agreed to change and closed issue |
Date Modified | Username | Field | Change |
---|---|---|---|
2023-10-06 15:37 | Brian Batke | New Issue | |
2023-11-03 13:46 | Paul Hunkar | Note Added: 0020258 | |
2023-11-03 13:47 | Paul Hunkar | Assigned To | => Georg Biehler |
2023-11-03 13:47 | Paul Hunkar | Status | new => assigned |
2024-01-05 07:22 | Paul Hunkar | Note Added: 0020574 | |
2024-01-05 07:28 | Paul Hunkar | Note Edited: 0020574 | |
2024-01-05 08:15 | Georg Biehler | Status | assigned => resolved |
2024-01-05 08:15 | Georg Biehler | Resolution | open => fixed |
2024-01-05 08:15 | Georg Biehler | Fixed in Version | => 1.00.03 |
2024-01-05 08:15 | Georg Biehler | Note Added: 0020575 | |
2024-01-05 13:58 | Paul Hunkar | Status | resolved => closed |
2024-01-05 13:58 | Paul Hunkar | Note Added: 0020578 |