View Issue Details

IDProjectCategoryView StatusLast Update
000603210000-005: Information ModelSpecpublic2020-09-18 14:06
ReporterJeff Harding Assigned ToJeff Harding  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Summary0006032: 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 0004742 closedJeff Harding 10000-020: File Transfer MaxByteStringLength for file transfer - inconsistency in spec 
related to 0006039 closedRandy Armstrong NodeSets, XSDs and Generated Code MaxByteStringLength for file transfer - inconsistency in spec 

Activities

Jeff Harding

2020-09-17 15:05

developer   ~0012908

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-17 15:13

developer   ~0012909

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

Jeff Harding

2020-09-17 15:14

developer   ~0012910

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

Jim Luth

2020-09-18 14:04

administrator   ~0012947

Agreed to changes in Virtual F2F.

Issue History

Date Modified Username Field Change
2020-09-17 15:05 Jeff Harding New Issue
2020-09-17 15:05 Jeff Harding Status new => assigned
2020-09-17 15:05 Jeff Harding Assigned To => Jeff Harding
2020-09-17 15:05 Jeff Harding Issue generated from: 0004742
2020-09-17 15:05 Jeff Harding Note Added: 0012908
2020-09-17 15:05 Jeff Harding Relationship added child of 0004742
2020-09-17 15:06 Jeff Harding Project 10000-020: File Transfer => 10000-005: Information Model
2020-09-17 15:07 Jeff Harding Relationship added child of 0004157
2020-09-17 15:12 Jeff Harding Relationship deleted child of 0004157
2020-09-17 15:13 Jeff Harding Note Added: 0012909
2020-09-17 15:14 Jeff Harding Status assigned => resolved
2020-09-17 15:14 Jeff Harding Resolution open => fixed
2020-09-17 15:14 Jeff Harding Fixed in Version => 1.05
2020-09-17 15:14 Jeff Harding Note Added: 0012910
2020-09-18 13:49 Jim Luth Relationship replaced related to 0004742
2020-09-18 14:04 Jim Luth Status resolved => closed
2020-09-18 14:04 Jim Luth Note Added: 0012947
2020-09-18 14:06 Jim Luth Issue cloned: 0006039
2020-09-18 14:06 Jim Luth Relationship added related to 0006039