View Issue Details

IDProjectCategoryView StatusLast Update
000738810000-005: Information ModelSpecpublic2022-06-20 12:02
ReporterJeff Harding Assigned ToJim Luth  
PrioritynormalSeverityfeatureReproducibilityhave not tried
Status closedResolutionfixed 
Product Version1.05.01 
Target Version1.05.01Fixed in Version1.05.01 
Summary0007388: Identification if a Value is Constant
Description

In many applications there are variables with values that are changing and variables with constant values.
Currently, there is no standard way to expose the information whether a value is constant and thus a client would need to subscribe to the constant variables as well.

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

  1. Forever (I would not assume this case in most cases)
  2. Until Server restarts
  3. Until configuration changes, that might occur while server is running

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.

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0006700 closedJim Luth 10000-003: Address Space Identification if a Value is Constant 

Activities

Jeff Harding

2021-11-05 15:02

developer   ~0015269

This is the Part 5 work to address the feature enhancement of Part 3 defined by Mantis 6700

Jeff Harding

2021-11-05 15:52

developer   ~0015270

Added optional ConfigurationVersion Property to NamespaceMetadataType

Jim Luth

2021-11-09 20:06

administrator   ~0015300

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.

Jim Luth

2021-11-11 22:06

administrator   ~0015302

Completed new proposal.

Jim Luth

2021-11-16 18:23

administrator   ~0015319

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.

Jim Luth

2022-06-20 12:02

administrator   ~0016874

Agreed that this is published in 1.05.01.

Issue History

Date Modified Username Field Change
2021-11-05 14:59 Jeff Harding New Issue
2021-11-05 14:59 Jeff Harding Status new => assigned
2021-11-05 14:59 Jeff Harding Assigned To => Jeff Harding
2021-11-05 14:59 Jeff Harding Issue generated from: 0006700
2021-11-05 14:59 Jeff Harding Project 10000-003: Address Space => 10000-005: Information Model
2021-11-05 15:01 Jeff Harding Relationship added related to 0006700
2021-11-05 15:02 Jeff Harding Note Added: 0015269
2021-11-05 15:52 Jeff Harding Status assigned => resolved
2021-11-05 15:52 Jeff Harding Resolution open => fixed
2021-11-05 15:52 Jeff Harding Fixed in Version => 1.05.01
2021-11-05 15:52 Jeff Harding Note Added: 0015270
2021-11-09 20:06 Jim Luth Assigned To Jeff Harding => Jim Luth
2021-11-09 20:06 Jim Luth Status resolved => assigned
2021-11-09 20:06 Jim Luth Note Added: 0015300
2021-11-11 22:06 Jim Luth Status assigned => resolved
2021-11-11 22:06 Jim Luth Note Added: 0015302
2021-11-16 18:23 Jim Luth Note Added: 0015319
2022-06-20 12:02 Jim Luth Status resolved => closed
2022-06-20 12:02 Jim Luth Note Added: 0016874