View Issue Details

IDProjectCategoryView StatusLast Update
000472610000-005: Information ModelApi Changepublic2020-09-16 17:44
ReporterDavid Levine Assigned ToJeff Harding  
PrioritylowSeveritytrivialReproducibilityalways
Status closedResolutionreopened 
Summary0004726: ArrayDimensions description in Part 5 is inconsistent with definition in Part 3
Description

In Part 3, section 5.6.2, Table 13, the attribute ArrayDimensions is listed as Optional, not Mandatory.

Part 5, section 5.3, Table 5, implies it is mandatory. It states:
"...If the ValueRank specifies an array of a specific dimension (i.e. ValueRank > 0) then the ArrayDimensions Attribute shall be specified in the table defining the Variable."

The sentence in Part 5 probably needs to be amended to something like this:
"...If the ValueRank specifies an array of a specific dimension (i.e. ValueRank > 0) then the ArrayDimensions Attribute should be specified in the table defining the Variable, or, if the server cannot determine its value, it can be set to either null or missing."

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

lacroix

2019-09-30 08:59

reporter   ~0011024

Moreover, in §3.3 of the part 5 revision 1.03, Table 1 contains examples of DataTypes with ValueRank > 0 and ArrayDimensions can be omitted. This is very confusing.

Jeff Harding

2020-06-08 15:00

developer   ~0012192

Changed Variable descripition of ArrayDimensions in Table 5 to:

"If the ValueRank does not identify an array of a specific dimension (i.e. ValueRank <= 0) the ArrayDimensions can either be set to null or the Attribute is missing. This behaviour is server-specific.
If the ValueRank specifies an array of a specific dimension (i.e. ValueRank > 0) and the Server can determine dimension size, then the ArrayDimensions Attribute shall be specified with the definition of the Variable. If the Server cannot determine the exact size of the dimension it shall be set to 0 or omitted."

Jeff Harding

2020-06-18 18:48

developer   ~0012452

After review the WG determined that Table 5 is specific to Nodes define in the 10000 series specs and not a general statement.
Therefore no change is needed.

David Levine

2020-06-30 14:58

developer   ~0012515

The context is missing - what are the 10000 series specs?

Table 5 says "For all Variables specified in this standard, the Attributes named in Table 5 shall be set as specified in Table 5. " I interpret that it applies to all variables.

The spec should be clear and unambiguous and not require information not contained in the spec.

Jim Luth

2020-06-30 16:05

administrator   ~0012516

Agreed to change "in the 10000 series" to "defined in namespace index 0".

Jeff Harding

2020-06-30 16:18

developer   ~0012518

change references in clause 5 from "the OPC 10000 series of documents" to "NamespaceIndex 0".

Jim Luth

2020-09-16 17:44

administrator   ~0012864

Agreed to changes in Virtual F2F.

Issue History

Date Modified Username Field Change
2019-04-10 14:21 David Levine New Issue
2019-06-25 16:34 Jim Luth Project UA => 10000-005: Information Model
2019-06-25 16:34 Jim Luth Category Documentation Errata => Api Change
2019-06-25 16:39 Jim Luth Assigned To => Jeff Harding
2019-06-25 16:39 Jim Luth Status new => assigned
2019-09-30 08:59 lacroix Note Added: 0011024
2020-06-08 15:00 Jeff Harding Status assigned => resolved
2020-06-08 15:00 Jeff Harding Resolution open => fixed
2020-06-08 15:00 Jeff Harding Fixed in Version => 1.05
2020-06-08 15:00 Jeff Harding Note Added: 0012192
2020-06-18 18:48 Jeff Harding Status resolved => feedback
2020-06-18 18:48 Jeff Harding Resolution fixed => reopened
2020-06-18 18:48 Jeff Harding Note Added: 0012452
2020-06-30 14:58 David Levine Note Added: 0012515
2020-06-30 14:58 David Levine Status feedback => assigned
2020-06-30 16:05 Jim Luth Note Added: 0012516
2020-06-30 16:18 Jeff Harding Status assigned => resolved
2020-06-30 16:18 Jeff Harding Note Added: 0012518
2020-09-16 17:44 Jim Luth Status resolved => closed
2020-09-16 17:44 Jim Luth Note Added: 0012864