The CCS contents including the embedded PubSubConfiguration is intended to be generated offline by the "connection design" engineering tool. The "connection design" engineering tool, which gets information about the participating ACs from Descriptor files, doesn't have knowledge about NodeIds of items in the AC models. Across the CCS model in Part 81 this has been solved by using the PortableNodeIdentifier type instead of a real NodeId. The PortableNodeIdentifiers can then be resolved online by the CM to the real NodeIds before making further calls to the ACs.

It had been not realized that PubSubConfiguration structure, which is also a part of the CCS, still requires NodeIds to be specified in several places, most notably in the definitions of custom DataSets.

There has to be an alternative way to supply the DataSet definitions, which doesn't require a knowledge of actual NodeIds.

By the way, even if it's assumed that the actual NodeIds are known at engineering time, there is still an issue that the Namespace indexes in the PubSubConfiguration within the CCS would need to be resolved online to the actual indexes used by the AC server. But to be able to do this, there would need to be a Namespaces array supplied in parallel with the PubSubConfiguration.