0010014: Clarify usage of ValueRank attribute in AML

ID	Project	Category	View Status	Date Submitted	Last Update

0010014	Part 83: UAFX Offline Engineering	Spec	public	2024-11-14 10:52	2025-02-28 15:09

Reporter	Emanuel Kolb	Assigned To	Emanuel Kolb
Priority	normal	Severity	minor	Reproducibility	have not tried
Status	closed	Resolution	won't fix
Product Version	1.00.02
Target Version	1.00.03	Fixed in Version	1.00.03

Summary	0010014: Clarify usage of ValueRank attribute in AML
Description	spec: "If not present in the AML SUC, the value in UA is assumed to be Any ( 2)" This would imply that in case the ValueRank attribute is not in the AML file the value in the Server always has to be -2? This would mean that the ValueRank Attribute is required for all ValueRanks other -2, e.g. Scalar. Is this really intended?
Tags	No tags attached.

Emanuel Kolb 2024-11-14 10:53 manager ~0022056	From Test Development WG

Emanuel Kolb 2024-11-15 10:59 manager ~0022066	ValueRank is mandatory for VariableTypes and Variables. In the AML mapping it does not be defined if ValueRank is "any" (-2). Yes, for scalars (1) it must be defined also in AML.

Emanuel Kolb 2024-11-15 11:00 manager ~0022067	see previous note

Jim Luth 2025-02-28 15:09 administrator ~0022447	Agreed to changes in 1.00.03.RC.

Date Modified	Username	Field	Change
2024-11-14 10:52	Emanuel Kolb	New Issue
2024-11-14 10:53	Emanuel Kolb	Note Added: 0022056
2024-11-15 10:54	Emanuel Kolb	Assigned To	=> Emanuel Kolb
2024-11-15 10:54	Emanuel Kolb	Status	new => assigned
2024-11-15 10:59	Emanuel Kolb	Note Added: 0022066
2024-11-15 11:00	Emanuel Kolb	Status	assigned => resolved
2024-11-15 11:00	Emanuel Kolb	Resolution	open => won't fix
2024-11-15 11:00	Emanuel Kolb	Note Added: 0022067
2025-02-14 14:47	Emanuel Kolb	Relationship added	related to 0010155
2025-02-28 15:09	Jim Luth	Status	resolved => closed
2025-02-28 15:09	Jim Luth	Fixed in Version	=> 1.00.03
2025-02-28 15:09	Jim Luth	Note Added: 0022447