In section
6.16.3.2 PubSubCommunicationModelConfigurationType definition

TranslationTable is introduced, which contains PortableNodeItentifiers, which can take a form of PortableRelativePath.

Every time a RelativePath is used in the specification, it requires a textual description of the starting Node of the path. Here, a description is missing.

Existing text:
"The first step is done locally within the ConnectionManager, and it involves the conversion of these NodeIds to PortableNodeIdentifiers according to the TranslationTable."

Proposal to add after that:

"If a PortableNodeIdentifier takes a form of PortableRelativePath, the starting node of such a path depeds on which PubSubConfiguration element the identifer corresponds to. If the identifer corresponds to a published or subscribed Variable (e.g. PublishedVariable of PublishedVariableDataType, or TargetNodeId of FieldTargetDataType), the path shall start at the hosting AutomationComponent, otherwise (e.g. DataType of FieldMetaData) the path shall start at the Server's Root."