OGC Climatology-Hydrology Information Sharing Pilot - This use case focuses on exchanging cross-border hydrologic data (stream flow and groundwater levels) with a unified alert service. Stream/river gauge and groundwater well locations are associated with a river network that in turn is associated with a set of basins (watersheds) (For the purposes of this Pilot, a simple geometric buffer will be used to identify gauge and well locations rather than catchments). For any well or stream gauge location, a web service provides access to the gauge and well information on all upstream stream segments or in all contributing basins. An event service provides subscribers a notification if any upstream streamflow or well water level reaches or exceeds a user-defined threshold. Selected river basins cross the U.S./Canada border. Data providers include state, provincial, and federal agencies. Based on sensor events, a flood is determined to be imminent and alerts are sent to the authorities in the affected areas.
Note that for "selected" status, both "cancel" and "subscribe" are enabled.
for "pending" status, clicking "subscribe" and status becomes "active" is the simulation of Vendor operation
for "active" status, clicking "subscribe" and status becomes "invalid" is also the simulation of Vendor operation
Then for "invalid" status, the user can click "cancel" to remove it from map
mlhch
commented
11 years ago 
whyvez
lets change the subscription state to this.
When posting a subscription the broker should return the submitted objects back with their id and status.