See also second Note to 8076

Added a note including a cross reference to 5.5.5 in 6.2.4.3.5

After longer discussion in team today, need to reopen the issue

Make a proposal for the new capability - Support preconfigured PubSubConfiguration objects

The need to modify PubSub configuration elements may result from two use cases:
(1) Use of preconfigured PubSub configuration elements (such as DataSetWriter, DataSetReader…)
(2) Update an established connection by updating for example the PublishingInterval
Using ElementModify may work for preconfigured objects (if they are not in use by a connection but how to detect that), but we have to consider when opening the ElementModify the second aspect (update). Both will use the ElementModify – how to differ between them.

Need to elaborate a concept post C2C V1.0.

Team decision on August 26th

In this release we are silent about preconfigured PubSub configuration elements (except the preconfigured DataSet). Therefore removed all places where we talk about preconfigured config element and ElementModify / ElementRemove.

Open is whether we should remove now in addition the support of preconfigured ConnectionEndpoints.

Agreed in call to leave IsPreconfigured flag as currently described in the spec (no changes), but that we will add a ConformanceUnit to the controller profile that sets this flag to False for this release. [in future release we can discuss if this ConformanceUnit should be removed]

Changed text in 5.5.5, 6.2.4.3.5,

Review text changes in call, agreed to changes and closed issue