nigel-r-davis
nigel-r-davis
I agree that there appear to be some issues here. We need to consider each measurement property in terms of the “attributes” set out in 4.5.2 of TR-512.A.4. Obviously, not...
The challenge is that the client may not, and probably does not, know the optimum order. If you force order specification on the client then it needs to do a...
In TR-548 the alarm is considered as an entity. When the alarm state goes to cleared, the entity is considered as having been deleted (so the active alarm list essentially...
I have checked the text and have changed the section you commented on to... As noted earlier, the alarm DELETE record (representing the alarm clear) shall be followed immediately by...
I also made a minor adjustment to the earlier section... CLEARED should not be used. A cleared alarm is represented by a DELETE/TOMBSTONE.
Hi, From a streaming perspective, the entity-key needs to be the same value for the raise, any changes and the clear for any particular detection. The entity-key needs to be...
Thanks for the comment. 1. When an entity is deleted in the controller, should the TAPI Streaming Provider supply 2 log-records to the client? One with record-type==RECORD_TYPE_DELETE and another with...
Thanks for highlighting the page numbers (in V2.0) I will take a look at this text and will attempt to improve the clarity.
Hi @roshan-joyce-fujitsu, I will review the comments on the document and make changes where they are clear. If I have any concerns, I will either raise them here or on...
@bcjohnso99 As @roshan-joyce-fujitsu indicated that there was only one change to do related to this Issue, we should cover this in 2.6.