These are two issue, but lets explain each separately:

UAFX AutomationComponent ConnectionEstablishment Bundled - The Automation component establish connection method supports a list of commands by default. any of the commands (list of them) can be included in an invocation of the method, There are some rule about the order of the commands, but a method could invoke one commands at a time (as long as they meet the sequence rules) or a group of commands. This conformance Unit indicates that this Automation component will not accept individual command, that it will only accept a predefined bundle of commands. This is restricting what this automation component can do and support for this conformanceUnit indicate that the automationComponent is restricted.

UAFX AutomationComponent PubSub Preconfigured Datasets - this conformance Unit again is used to indicate that the AutomationComponent is restricted. An AutomationComponent may have a preconfigured data set or may not. the dataset maybe created as part of the establish connection process. This is the default. If the AutomationComponent has a preconfigured dataset, it is exposed in the address space and can be used in a connection. If an AutomationComponent does not support creation of Dynamic datasets, but can only have pre-configured dataset then this conformance unit is selected. Again indicate the AutomationComponent is restricted.

In both case the AC indicates the restriction by setting capabilities that an ConnectionManager can discover (also and more likely an engineerTool can discover) and only setup (or for engineering tool configure) restricted connections.

In general a server would not want to support these ConfirmanceUnits unless it wants to restrict functionality.

Do we need more text to better explain this in the ConformanceUnit

Does Paul's comment answer the question, or are the spec changes required?

After much discussion it was agreed that no changes would be made.

Discussed during AWG meeting and agreed no changes should be made.