View Issue Details

IDProjectCategoryView StatusLast Update
0006039NodeSets, XSDs and Generated CodeApi Changepublic2021-02-23 17:41
ReporterJim Luth Assigned ToRandy Armstrong  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Summary0006039: MaxByteStringLength for file transfer - inconsistency in spec
Description

In Part 5, 6.3.2. ServerCapabilitesType it says

"The MaxByteStringLength Property indicates the maximum number of bytes in a ByteString supported by Variables of the Server. It also specifies the default maximum size of a FileType Object’s read and write buffers. Servers may override this setting by adding the MaxByteStringLength Property defined in Part 3 to an individual DataVariable or FileType Object."

However, the MaxByteStringLength property is not mentioned in the definition of FileType (Part 5, C.2 FileType ) and also not mentioned in the definition of the Object NodeClass, as in Part 3, Table 11.
It is defined for the Variable NodeClass, as in Part 3, Table 13.

Therefore, it is unclear whether a client should look for this property, at instances of FileType.
See also Mantis 2979, where the use case was discussed and it was decided to change Part 5. Apparently it was forgotten to change Part 3.

Easiest solution:
Add MaxByteStringLength as optional Property to the definition of FileType.
I think this would be the best way to go, since the use case where we have a problem with the spec, is really only for file transfer.

Alternative solution:
Add MaxByteStringLength as optional Property to the Object Nodeclass.

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0006032 closedJeff Harding 10000-005: Information Model MaxByteStringLength for file transfer - inconsistency in spec 

Activities

Jeff Harding

2020-09-18 14:06

reporter   ~0012948

Part 5 state "The MaxByteStringLength Property indicates the maximum number of bytes in a ByteString supported by Variables of the Server. It also specifies the default maximum size of a FileType Object’s read and write buffers." which is correct however the following sentence "Servers may override this setting by adding the MaxByteStringLength Property defined in OPC 10000-3 to an individual DataVariable or FileType Object." needs correcting since the standard Property MaxByteStringLength is defined as a standard property of VariableNode. Since FileType is an ObjectType we need to fix something.

I agree the solution should be to add a new optional property to the FileType and then fix the text in Part 5 by removing the reference to FileType.

Jeff Harding

2020-09-18 14:06

reporter   ~0012949

This is the Part 5 change to support Part 20's Mantis issue 4742

Jeff Harding

2020-09-18 14:06

reporter   ~0012950

removed the forward reference to Part 20's FileType and moved the text to Part 20.

Jim Luth

2020-09-18 14:06

administrator   ~0012951

Agreed to changes in Virtual F2F.

Randy Armstrong

2020-11-16 07:32

administrator   ~0013222

Added MaxBufferLength to FileType in UA-1.05-2020-11-20

Jim Luth

2021-02-23 17:41

administrator   ~0013782

agreed to changes in telecon.

Issue History

Date Modified Username Field Change
2020-09-18 14:06 Jim Luth New Issue
2020-09-18 14:06 Jim Luth Status new => assigned
2020-09-18 14:06 Jim Luth Assigned To => Randy Armstrong
2020-09-18 14:06 Jim Luth Issue generated from: 0006032
2020-09-18 14:06 Jim Luth Note Added: 0012948
2020-09-18 14:06 Jim Luth Note Added: 0012949
2020-09-18 14:06 Jim Luth Note Added: 0012950
2020-09-18 14:06 Jim Luth Note Added: 0012951
2020-09-18 14:06 Jim Luth Relationship added related to 0006032
2020-09-18 14:07 Jim Luth Project 10000-005: Information Model => NodeSets, XSDs and Generated Code
2020-09-18 14:07 Jim Luth Category Spec => Api Change
2020-11-10 17:10 Jim Luth Target Version => 1.05
2020-11-16 07:32 Randy Armstrong Status assigned => resolved
2020-11-16 07:32 Randy Armstrong Resolution open => fixed
2020-11-16 07:32 Randy Armstrong Note Added: 0013222
2021-02-23 17:41 Jim Luth Status resolved => closed
2021-02-23 17:41 Jim Luth Fixed in Version => 1.05
2021-02-23 17:41 Jim Luth Note Added: 0013782