Issue in relation to issue 6341.

Any updates to this issues?

The following text is included in part 6 (section 5.1.9) https://reference.opcfoundation.org/v105/Core/docs/Part6/5.1.9/
'The terms null, empty and zero-length are used to describe array values (Strings are arrays of characters and ByteStrings are arrays of Bytes for purposes of this discussion). A null array has no value. A zero-length or empty array is an array with 0 elements. Some DataEncodings will allow the distinction to be preserved on the wire, however, not all DevelopmentPlatforms will be able to preserve the distinction. For this reason, null, empty and zero length arrays are semantically the same for all DataEncodings. Decoders shall be able to handle all variations supported by the DataEncoding, however, decoders are not required to preserve the distinction. When testing for equality, applications shall treat null and empty arrays as equal. When a DevelopmentPlatform supports the distinction, writing and reading back an array value may result in null array becoming an empty array or vise versa."

what this is saying is that an implementation is required to be able to perform the mapping to what is allowed in the underlining system.

Based on the specification section in part 6, we believe that no changes are required. We understand that an underlining system might not have the same mapping for a null, but they still should have something that represents an empty and that mapping is what is required. Do you see a different issue?

If I am understand this right, the following applies.
For example a ByteString NULL is written, this could be intepret as ByteString.Length = 0, ByteString.Data = NULL. So the underlining system contains after this write a nulled data like ByteString[8]=0x00000000?