ooici/coi-services — pull request #326 by swarbhanu (2012-10-24 17:18:04+00:00)
Title: Incorporate the use of the temporal bounds attribute of NotificationRequests in UNS

# UNS changes to incorporate the use of the temporal bounds attribute of NotificationRequests in UNS#

### Who are affected?###

Should be no one.

These changes should not be affecting anyone right now. Right now temporal bounds are not used much outside UNS.

### What's the result ###

Temporal bounds have start_datetime and end_datetime attributes. When the operator creates a notification using create_notification(), the start_datetime value is filled to the current time value (in seconds, for now).

When a delete_notification() method is used, the end_datetime field of the notification request is filled in. The notification request can then be considered to have been retired.

Users do not receive notification pertaining to the retired notification.