Part 81 is not precise enough on the processing of the members in an instance of PubSubCommunicationConfigurationDataType. Currently it only states “shall add the supplied PubSubConfiguration to PubSub as described in OPC 10000-14”. It is not clear to a reader, that this refers to “9.1.3.7 Modification of PubSub configuration” in part 14.

It is a far stretch, that a reader will look up the datatype, see that it is defined in Part 14, used in a method that is called CloseAndUpdate, and then deduces that this is what is meant in Part 81. That the arguments have matching names may help, but this is really “educated guessing” from the reader’s side and in my opinion a specification should not rely on readers guessing correctly.

Also: An implementer of EstablishConnections, in order to reuse a potentially existing CloseAndUpdate function, must write the configuration to a file, open the file, and pass a file handle to the SDK function.
The file handle is an Uint32 and in part 14 it is probably returned by the FileType.Open() method, which will in turn require the client of CloseAndUpdate to create a FileType object first.
It does seem to me, that EstablishConnections will not be able to use an existing SDK function without any coding effort (which was an initial assumption I believe).

The description of the ConfigurationReferences member in Part 81 mentions a file. Part 81 does not provide a possibility yet to upload a file, thus a reader will not know what this refers to.

(copied from a Mail Thread between David, Brian and Georg)