Add generic event data elements for Detector events #152
Conversation
Change-Id: I21039e02b20d6048c133bdf6e8073d71f51c5280
- Describe event Data section in the Message Format section. - Update Line, Field and Loitering Detector to refer to Data in the general Message Format section. Change-Id: Ieacb9f16ea49a81ab4da8e72c6fd433ff5031cf8
Change-Id: If0b70b4a21c8c593bc7c3d57a1ba26cc694ad8fc
| @@ -3128,12 +3128,16 @@ | |||
| <varlistentry> | |||
| <term>Data</term> | |||
| <listitem> | |||
| <para role="text">Data items are rule specific. For property events any change of the data values items must be signaled with a changed event. | |||
There was a problem hiding this comment.
Propose to leave the original sentence.
There was a problem hiding this comment.
I agree with Hans comment,
There was a problem hiding this comment.
The original sentence is still there. It now reads: "Data items are rule specific, except for the generic elements described here. For property events any change of the data values items must be signaled with a changed event. Non-property events may have no data items at all."
| @@ -3142,7 +3146,9 @@ | |||
| </tt:Source> | |||
| <tt:Data> | |||
| ... | |||
| </tt:Data> | |||
| <tt:SimpleItemDescription Name="ObjectId" Type="xs:integer"/> | |||
There was a problem hiding this comment.
Many rules already have ObjectID of type StringList. Propose to either align name or drop.
There was a problem hiding this comment.
A quick grep gives ObjectId vs ObjectID: 35 vs 5 so ObjectId wins!
There was a problem hiding this comment.
Agree with ObjectId although it is a mess.
Change-Id: I6c327765463ac41bd4ed1161dee403cba137ddce
Add section about generic event data elements for Line/Field/Loitering Detector.
Resolves #150