View Issue Details

IDProjectCategoryView StatusLast Update
0008518NodeSets, XSDs and Generated CodeApi Changepublic2023-03-23 21:28
ReporterJim Luth Assigned ToRandy Armstrong  
PrioritynormalSeverityfeatureReproducibilityhave not tried
Status closedResolutionfixed 
Fixed in Version1.05.03 RC1 
Summary0008518: Missing Statuscode for Index Range not compatible with data to write
Description

Scenario:
Writing an Array[2] with index range (2:3) to an Array[5] is fine.
But writing an Array[2] with an index rang (1:4) to an Array[5] leads to an mismatch in index range length and array length (2<4).
Even if the Array to write is bigger than the index range.

What statuscode should be send by the server receiving this write request.

The definition of the Statuscodes BadIndexRangeInvalid and BadIndexRangeNoData do not match with this situation in my opinion.

We would asume a Statuscode like BadIndexRangeDataMissmatch or BadIndexRangeDataInvalid.
Or should we use some complete different type of StatusCode.

The Spec defines some aspects in NumericRange:
Bad_IndexRangeInvalid is only used for invalid syntax of the NumericRange. All other invalid requests with a valid syntax shall result in Bad_IndexRangeNoData.
When writing a value, the size of the array shall match the size specified by the NumericRange. The Server shall return an error if it cannot write all elements specified by the Client.

The second one is the same as in our scenario but it is not mentioned what error a Server shall return. Or is it Bad_IndexRangeNoData because it is no syntax issue? We think a more detailed StatusCode would be appreciated

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0008432 closedMatthias Damm 10000-004: Services Missing Statuscode for Index Range not compatible with data to write 

Activities

Matthias Damm

2022-12-07 14:43

reporter   ~0018262

Discussion in UA WG meeting - we want to add a new status code

Matthias Damm

2022-12-07 14:43

reporter   ~0018263

Table 61 – Write Operation Level Result Codes

Added StatusCode

Bad_IndexRangeDataMismatch
The written data does not match the IndexRange specified.

Jim Luth

2022-12-07 14:44

administrator   ~0018264

Add new status code to Part 6.

Randy Armstrong

2022-12-28 06:47

administrator   ~0018356

Added Bad_IndexRangeDataMismatch to list of StatusCodes.

Jim Luth

2023-03-23 21:28

administrator   ~0019028

Agreed to changes in Dallas meeting.

Issue History

Date Modified Username Field Change
2022-12-07 14:43 Jim Luth New Issue
2022-12-07 14:43 Jim Luth Status new => assigned
2022-12-07 14:43 Jim Luth Assigned To => Matthias Damm
2022-12-07 14:43 Jim Luth Issue generated from: 0008432
2022-12-07 14:43 Jim Luth Note Added: 0018262
2022-12-07 14:43 Jim Luth Note Added: 0018263
2022-12-07 14:43 Jim Luth Relationship added related to 0008432
2022-12-07 14:43 Jim Luth Project 10000-004: Services => 10000-006: Mappings
2022-12-07 14:43 Jim Luth Assigned To Matthias Damm => Randy Armstrong
2022-12-07 14:44 Jim Luth Note Added: 0018264
2022-12-28 06:47 Randy Armstrong Status assigned => resolved
2022-12-28 06:47 Randy Armstrong Resolution open => fixed
2022-12-28 06:47 Randy Armstrong Fixed in Version => 1.05.03 RC1
2022-12-28 06:47 Randy Armstrong Note Added: 0018356
2023-03-23 21:28 Jim Luth Project 10000-006: Mappings => NodeSets, XSDs and Generated Code
2023-03-23 21:28 Jim Luth Category Spec => Api Change
2023-03-23 21:28 Jim Luth Status resolved => closed
2023-03-23 21:28 Jim Luth Note Added: 0019028