Question: does it make sense to merge CocClockService and LightWeightTime in a single file "define" controlled?

To include the LightWeight part of the spec in the cosClockService IDL and update the LightWeight part of specification (section 9) accordingly.

On 8.8

Does it make sense to change the module encapsulation for Monotonicity?

I'd propose

module Monotonicity
{
enum RecoveyStrategy

;

struct Violation

;

local interface ViolationHandler;
local interface ViolationRegistry

;

local interface ViolationHandler

;

};

To introduce a specific module “Monotonicity” to be nested into cosClockService module.

LightWeight idl contains some error (Local vs Local_), some macro (e.g. LW_TIME)
is not described, some type is not coherent with the complete service (e.g. ClockCatalog),
consolidate IDL is not present in the spec.

To substitute attribute “Local” in module “ClockProperty” with “_Local”.

Forever should be 0x7FF.... instead of 0xFFFF (java problems

To modify “Forever” attribute value in “0x7FFF”

General
some fix in the description of parameter (changed names with clash with type e.g. Clock clock -> Clock aClock)

To change the names of the attributes as, for example: Clock clock -> Clock aClock

On 8.5.4.2
There is a typo error in the formatting

To format §8.5.4.2 as the other subsection of section 8.5.4

ClockCatalog is an uncostrained interface in the spec description but not in the idl, I propose to maintain it uncostrained everywhere.

To maintain ClockCatalog interface unconstrained in the EVoT services (lightweight or not).

On 8.4.2
typo error getRaises instead of raises

See issue 11309 for disposition

On 8.8
Monotonicity handling is not in the IDL

See issue 11317 for disposition

On 8.4.2
current_time is a readonly attribute: this way to declare a method
doesn't offer a great added value instead of a simple current_time method,
my proposal is to change it in a method
TimeBase::TimeT current_time()
this also improve the idl compilation capabilities, indeed some idl compiler
(e.g. JacORB and omniORB) fails with readonly attribute and raises keywords.

To substitute the readonly attribute “current_time” in Clock interface with “TimeBase::TimeT current_time()” method.