DDSXTY_ — New QoS policies don’t indicate whether they can be changed

Source:

RTI (Mr. Alejandro de Campos, alejandro@rti.com)

Summary:

Each DDS QoS policy must define a couple of attributes: whether or not the policy has request-offer (RxO) semantics and whether or not it can be changed after an entity is enabled. The two new QoS policies defined by DDS-XTypes—TypeConsistencyEnforcementQosPolicy and DataRepresentationQosPolicy—define the first part but not the second.

Discussion:

Because of their potential interactions with historical data, neither of these policies should be changeable after an entity is enabled.

Proposed Resolution:

State in the introduction to each policy that its value cannot be changed after an entity is enabled.

Proposed Revised Text:

TO DO

State in the introduction to each policy that its value cannot be changed after an entity is enabled