<ProfileIdentifier> has a ModellingRule ManatoryPlaceholder which means a node with BrowseName <ProfileIdentifier> NEVER appears on instance so the proposed fix is wrong.

Technically a new Node with some undetermined BrowseName should appear on every instance but if this is to occur a "Sample" node needs to be explicitly stated in the specification where an instance of ConnectionPointType is defined.

From a practical perspective, the modelling rule should be OptionalPlaceholder. We could have more philosophical discussions on what the point of ManatoryPlaceholder is given this unexpected side effect.

Based on feedback from Randy during meeting today this is a issue in the tooling that needs to be fixed.

The instance declaration nodes do now reference the mandatory placeholder from the TypeDefinition node.
This creates the required mandatory placeholder

Completed review in meeting today based on latest nodeset in the member only nodest repository