When testing our server, some tests that generate strings based on MaxStringLength fail due to the tested variable having a smaller MaxStringLength than the server capabilities specify:

• Base Information / Base Info Server Capabilities / 006.js
• Monitored Item Services / Monitor Value Change / 024.js, 026.js, 028.js

All these tests use WriteService.GenerateString() to provide a string. The tested variable has its own MaxStringLength property, but GenerateString does not recognise this because it only checks for a BrowseName of "0:MaxStringLength".
The server currently generates the variable property in the same namespace as the variable itself, i. e. with the BrowseName "4:MaxStringLength".

I am not sure whether the server or WriteService.GenerateString() is incorrect as I could only find relatively vague information about this searching the specification:

1.04 Part 5 6.3.2 and 1.04 Part 3 5.6.2 don't mention the namespace index of the property.
1.04 Part 3 3.3.2 includes following paragraph "This standard defines Properties, but Properties can be defined by other standard organizations or vendors and Nodes can have Properties that are not standardised. Properties defined in this standard are defined by their name, which is mapped to the BrowseName having the NamespaceIndex 0, which represents the Namespace for OPC UA."

Does this mean the MaxStringLength property of the string variable has to be in namespace 0? If not, then WriteService.GenerateString() needs to check for other namespaces than 0 as well.