View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0006700 | 10000-003: Address Space | Spec | public | 2021-03-24 11:02 | 2022-06-20 11:59 |
Reporter | Wolfgang Mahnke | Assigned To | Jim Luth | ||
Priority | normal | Severity | feature | Reproducibility | have not tried |
Status | closed | Resolution | fixed | ||
Target Version | 1.05.01 | Fixed in Version | 1.05.01 | ||
Summary | 0006700: Identification if a Value is Constant | ||||
Description | In many applications there are variables with values that are changing and variables with constant values. It would be desiarable to provide this information on the attribute level so it can be applied to Properties (typically, rather Properties than DataVariables have constant values). We could extend the AccessLevelEx attribute like done in Mantis Issue 0004422. If we do, we need to clarify what Constant means
In case 2 it would be desirable and in case 3 required to have something like a global ConfigurationVersion that would be updated, when the configuration has changed. Motivation of this issue is, that we actually need such a functionality in the "Relative Spatial Location" subgroup of the Harmonization WG. We could solve it there with Properties, but it would be desirable to have a more common solution, and it cannot be solved with Properties on Properties. | ||||
Tags | No tags attached. | ||||
Commit Version | |||||
Fix Due Date | |||||
related to | 0007345 | assigned | Jeff Harding | 10000-003: Address Space | Clarifications on notification mechanisms for caching clients |
related to | 0007388 | closed | Jim Luth | 10000-005: Information Model | Identification if a Value is Constant |
|
Agreed in telecon to let Wolfgang design a proposal for this. |
|
Added a Constant bit and ConfigurationConstant bit to AccessLevelExType |
|
We agreed to an alternate solution with the three bits named differently and with slightly different meaning. Jim will edit Part 3 and 5 with the new proposal. |
|
Completed new proposal. |
|
It today's call we concluded that the Immutable bit has little use and there is no best way to allow even an infrequent change in Value. We decided to remove the Immutable bit from 1.05.01 RC1. Wolfgang with check with the Harmonization w.g. to see what the impact is. If necessary, we will add the Immutable bit back in a later version. |
|
Agreed that this is published in 1.05.01. |
Date Modified | Username | Field | Change |
---|---|---|---|
2021-03-24 11:02 | Wolfgang Mahnke | New Issue | |
2021-03-24 11:14 | Jim Luth | Project | UA Specification => 10000-003: Address Space |
2021-04-06 15:18 | Jim Luth | Severity | minor => feature |
2021-04-06 15:23 | Jim Luth | Assigned To | => Wolfgang Mahnke |
2021-04-06 15:23 | Jim Luth | Status | new => assigned |
2021-04-06 15:24 | Jim Luth | Note Added: 0014165 | |
2021-10-06 08:20 | Wolfgang Mahnke | Relationship added | related to 0007345 |
2021-11-02 16:13 | Jim Luth | Assigned To | Wolfgang Mahnke => Jeff Harding |
2021-11-02 16:13 | Jim Luth | Target Version | => 1.05.01 |
2021-11-05 14:59 | Jeff Harding | Issue cloned: 0007388 | |
2021-11-05 15:01 | Jeff Harding | Relationship added | related to 0007388 |
2021-11-05 15:54 | Jeff Harding | Status | assigned => resolved |
2021-11-05 15:54 | Jeff Harding | Resolution | open => fixed |
2021-11-05 15:54 | Jeff Harding | Fixed in Version | => 1.05.01 |
2021-11-05 15:54 | Jeff Harding | Note Added: 0015271 | |
2021-11-09 20:04 | Jim Luth | Assigned To | Jeff Harding => Jim Luth |
2021-11-09 20:04 | Jim Luth | Status | resolved => assigned |
2021-11-09 20:04 | Jim Luth | Note Added: 0015299 | |
2021-11-11 22:06 | Jim Luth | Status | assigned => resolved |
2021-11-11 22:06 | Jim Luth | Note Added: 0015303 | |
2021-11-16 18:23 | Jim Luth | Note Added: 0015320 | |
2022-06-20 11:59 | Jim Luth | Status | resolved => closed |
2022-06-20 11:59 | Jim Luth | Note Added: 0016872 |