View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0006039 | NodeSets, XSDs and Generated Code | Api Change | public | 2020-09-18 14:06 | 2021-02-23 17:41 |
Reporter | Jim Luth | Assigned To | Randy Armstrong | ||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | closed | Resolution | fixed | ||
Summary | 0006039: 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. Therefore, it is unclear whether a client should look for this property, at instances of FileType. Easiest solution: Alternative solution: | ||||
Tags | No tags attached. | ||||
Commit Version | |||||
Fix Due Date | |||||
related to | 0006032 | closed | Jeff Harding | 10000-005: Information Model | MaxByteStringLength for file transfer - inconsistency in spec |
|
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. |
|
This is the Part 5 change to support Part 20's Mantis issue 4742 |
|
removed the forward reference to Part 20's FileType and moved the text to Part 20. |
|
Agreed to changes in Virtual F2F. |
|
Added MaxBufferLength to FileType in UA-1.05-2020-11-20 |
|
agreed to changes in telecon. |
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 |