I recall a requirement (but couldn't find it) where a connection configuration based on either the offline descriptor or on online retrieved information shall be possible (should ask Paul Brooks for the MR). In addition, we have a statement in 6.16.3.2 that the ConnectionManager may generate the PubSubConfiguration. Both cases (online retrieval and CM generated PubSub) require the exposure of preconfigured DataSets.

Thus an AutomationComponent having preconfigured DataSets has to expose the PublishSubscribe Object, including the mandatory items as required by Part14; these are Status, SupportedTransportProfiles, and the (maybe empty) PublishedDataSets folder.
In addition, the AutomationComponent has to expose all preconfigured PublishedDataSets in the folder (and maybe sub-folders of it).
If preconfigured SubscribedDataSets exist, the AutomationComponent has to expose the SubscribedDataSets folder (and maybe sub-folders) and all preconfigured SubscribedDataSets.

Side Note: We have a statement in Part81 that a FunctionalEntity may decide not to expose the ConnectionEndpoints.
Thus all preconfigured items, i.e., DataSets, ConnectionEndpoints, and if later supported PubSub configuration elements, have to be exposed.

If an AutomationComponent does not support preconfigured DataSets or later preconfigured PubSub configuration elements, there is no need to expose the PubSub configuration, including the PublishSubscribe object.

For the SKS an exposure of the configuration model (SecurityGroups, PubSubKeyPushTargets) including the Methods for configuration (i.e., AddSecurityGroup, AddPushTargert, ConnectSecurityGroups), if the SKS is not co-located with a ConnectionManager (in this case the CM may use vendor specific means to configure the SKS).

best to handle this in ConformanceUnits

We decided that preconfigured datasets should be exposed. This will require new conformance units that mandate support of the PublishSubscribe Object.

UAFX Preconfigured Published Dataset and UAFX Preconfigured Subscribed Dataset conformance units were added.
Both were made mandatory in the controller server profile.

The additions were reviewed and approved in an AWG meeting.