Alarms in iControl > Key Concepts > Alarm Attributes > General Guidelines for Alarm Attributes > Derived (alarm) URIs
 
Derived (alarm) URIs
There is sometimes a case for generating meaningful URIs that are associated to other existing (and presumably also meaningful) URIs. This occurs when you publish an alarm that depends directly on another alarm. A good example are the alarms published by the cycling engine; we want these alarms to be derived from the base alarms that they relate to, adding a notion of channels into the mix. Another example are event URIs for events that are closely related to alarms, for instance an event that pertains to acknowledging an alarm, or switching a router crosspoint.
The approach that we favor is to add a prefix to the existing alarm (which is less problematic than adding a suffix). For instance you might get:
cycled:<channelID>:<baseAlarmURI>
event:ack:<relatedAlarmURI>