Video/object track aggregation event

[bsriramprasad]

Here is the summary of changes included in PR

• Created a new section "Object Track Aggregation" event description in Analytics specification
• Created schema structures referred in the event description
• No additional changes in Metadata configuration, follows existing Event transport.
• Not defined as a property event
  • Primary use case to standardize only the 'final aggregation'
    • Initial/intermediate aggregations are made optional
  • use case NOT at all focused to get the state of every object in the scene at any time.
• If we are sending only one (final aggregation) event per object, it is an overkill to fit into the property event paradigm.

23/08/2024 Update

• Removed individual structures created for snapshot/bounding box
  • Reused the tt:Object with the capture time attribute
• Included Rule options for below
  • ReportTimeInterval
  • Data filter for including complement data like snapshot/bounding box
  • Add Rule options response sample

10/09/2024 Update
Addressed below changes based on the Bangkok F2F discussions

• Rename ObjectComplement as ObjectTrack
• Clarify Object track data as additional data generated by the device based on the ObjectTrackDataFilter configured by the client
• Fixed rule type as tt:ObjectTrack, incorrectly referring tt:ObjectClassification
• Remove AggregationEnd and use event time instead
• Fixed the extension structure as suggested by @HansBusch

[HansBusch]

There seems to be no way for the client to control the amount of produced track information.
Do we need a parameter to limit the number of snapshots?

[bsriramprasad]

There seems to be no way for the client to control the amount of produced track information. Do we need a parameter to limit the number of snapshots?

If we modify the Object track complement structure to change to include tt:Object to make it more generic, Are we not opening up for more data to be sent that could be hard to filter?

• That's the reason we have created a focused structure with just snapshot and bounding box.
  • Our previous F2F discussion focused a lot on trying to filter data - but it turned out to quite complex and hence opted for more focused proposal.

[HansBusch]

Editorial remark on extending types:

	<xs:complexType name="ObjectComplementData">
		<xs:complexContent>
			<xs:extension base="tt:Object">
				<xs:attribute name="CaptureTime" type="xs:dateTime"/>
				<xs:anyAttribute processContents="lax"/>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>

[bsriramprasad]

Editorial remark on extending types:

	<xs:complexType name="ObjectComplementData">
		<xs:complexContent>
			<xs:extension base="tt:Object">
				<xs:attribute name="CaptureTime" type="xs:dateTime"/>
				<xs:anyAttribute processContents="lax"/>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>

Thanks for the suggestion, updated the schema as suggested.

[bsriramprasad]

Remove the redundant text about intermediate aggregation