Remove the restriction on 'initial value'.

Change "provided by an AddComment Method or some other Method" to provided by an AddComment Method or some other mechanism".

Make it clear that an AddComment can set the comment to null. Any other mechanism such as Acknowlegde does not change the the comment if the value provided is null or empty.

Added new methods AcknowledgeNoComment and ConfirmNoComment which allow for acknowledging or confirming an alarm without altering an existing comment. (Changing the existing method would result in a functional change that would affect existing systems.) Added text indicating that the comment maybe provided by other mechanisms and that these mechanism may provide an initial comment with the Alarm.

In call discussion resulted in "no fix" as a solution (spec will be updated to remove the added text)

The alarm comment is to describe the current state of the alarm, an acknowledge or confirms affects the current state - so an ack or confirm changes this current state and the comment should be wiped or updated.

If a user wants additional behaviour they can always add methods in there custom system, but the system must still handle the alarm Acknowledge and confirm as described in the system.

Updated the specification to indicate how the method could be called with out providing a comment and how to call the method with an empty comment to reset the comment field.

Discussed in Walldorf