0006808: MaxByteStringLength property missing on FileType

ID	Project	Category	View Status	Date Submitted	Last Update

0006808	10000-020: File Transfer	Spec	public	2021-04-11 09:46	2021-05-04 15:50

Reporter	Zbynek Zahradnik	Assigned To	Jeff Harding
Priority	normal	Severity	minor	Reproducibility	always
Status	closed	Resolution	duplicate

Summary	0006808: MaxByteStringLength property missing on FileType
Description	We have following text in ServerCapabilitiesType: "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 OPC 10000-3 to an individual DataVariable or FileType Object. If a Server does not impose a maximum number of bytes or is not able to determine the maximum number of bytes this Property shall not be provided." The MaxByteStringLength Property is not, however, listed in Table C.1 - FileType.
Tags	No tags attached.

Commit Version
Fix Due Date

Date Modified	Username	Field	Change
2021-04-11 09:46	Zbynek Zahradnik	New Issue
2021-04-13 16:11	Jim Luth	Project	10000-005: Information Model => 10000-020: File Transfer
2021-04-13 16:14	Jim Luth	Issue cloned: 0006812
2021-04-13 16:14	Jim Luth	Relationship added	related to 0006812
2021-04-13 16:15	Jim Luth	Assigned To	=> Jeff Harding
2021-04-13 16:15	Jim Luth	Status	new => assigned
2021-05-04 14:31	Zbynek Zahradnik	Note Added: 0014298
2021-05-04 15:50	Jim Luth	Relationship added	related to 0004742
2021-05-04 15:50	Jeff Harding	Status	assigned => closed
2021-05-04 15:50	Jeff Harding	Resolution	open => duplicate
2021-05-04 15:50	Jeff Harding	Relationship replaced	duplicate of 0004742

duplicate of	0004742	closed	Jeff Harding	10000-020: File Transfer	MaxByteStringLength for file transfer - inconsistency in spec
related to	0006812	closed	Randy Armstrong	ModelValidator	MaxByteStringLength property missing on FileType

Zbynek Zahradnik 2021-05-04 14:31 developer ~0014298	I have now found 0004742 which appears to be dealing with the same problem, although the proposed and accepted solution is slightly different (a different property).