The LwCCM removes the usage of cidl from CCM, but this looses also the fixed name of the base class of the executor. The spec should define how the base class of an executor is generated by the framework, so that the implementor of the executor can write a portable executor

In the ZIOP 1.0 specification, the IDL in Annex A has:

typedef unsigned short CompressorId { };

The braces are invalid and should be removed.

In the ZIOP 1.0 specification, Annex A has:

Compressor get_compressor(
in CompressorId compressor_id,
in CompressorLevel compression_level)
raises (UnknownCompressorId);

CompressorLevel should be CompressionLevel.

Section 17.3.1 of CORBA 3.1 / 3.2 says:

17.3.1 Structures

PolicyValue

This structure contains the value corresponding to a Policy of the
PolicyType indicated by its ptype. This representation allows the
compact transmission of QoS policies within IORs and Service
Contexts. **The format of pvalue for each type is given in the
specification of that Policy.**

When the ZIOP 1.0 specification describes the ZIOP policies, it does not
give the format for pvalue.

The ZIOP body format contains the original length of the compressed
data, which is important because it allows the compressor to efficiently
allocate a buffer to uncompress it. Unfortunately, the
Compressor::decompress() operation is not given that size, meaning that
it has to guess how big the uncompressed data will be.

The original data size should be given to the decompress() operation.
One way to do that without changing the operation signature would be to
specify that the inout Buffer target sequence should have its length
pre-populated to the expected size.

In section 10.3.1.2 the typedef CCMObjectSeq is listed, we propose to move it to Section 6.11.1 just after the definition of CCMObject

The CCM spec describes the event mechanism default part of CCM. We want to propose to change this event machine to a connector based model as part of the DDS4CCM specification. Then there would be an event connector and the container then is much more light weight and easier to use. People that don't want to use CORBA event machinisms don't pull in all the dependent code

The IDL file 07-02-01 related to CCM is lacking ResourceCommitmentManager

HomeConfiguration::set_configuration_values documentation should mention which exception to thrown when an any/name value pair has a not supported name or when the any can't be extracted

The IDL file 07-02-01 related to CCM we have the following exceptions

exception LastConfiguration {
};

exception InvalidReference {
};

LastCOnfiguration is not listed at all in 06-04-01 and 06-04-02

InvalidReference is listed in 06-04-02 in text and diagrams, but not in idl at all

The spec mentions InvalidConfiguration as exception but there is no idl in this spec that describes this exception and its members

In chapter 6.6.8, sub paragraph "connect_consumer" the following statement is given:

The cookie return value can be used to disconnect from the source.

I think that this sentence should be removed from the specification since connect_consumer is declared as follows:

void connect_consumer (
in FeatureName emitter_name,
in EventConsumerBase consumer)
raises (InvalidName, AlreadyConnected,
InvalidConnection);

Also, disconnect_consumer doesn't provide a cookie as input parameter.