Expanding Analytics / Rule module and description: Exploring the Possibility of Vendor-Specific Extensions?

[coohottim]

Hello

Recently, I read the spec of profile M and analytics service spec, which define parameters such as human face and body recognition, license plate detection for vehicles.
However, it seems limited to human and vehicle-related items.

Q1: I'm wondering if it's possible to add analytics modules for vendor-specific extensions, such as animal, plant, weather recognition, or any other module that I want.
Would adding such extensions violate the protocol/spec? (6.3.1 Analytics module configuration)

Q2: If Q1 yes, the types are defined like nn:MotionDetection and nn:ObjectTracker etc..., can I add a vendor-specific type?

For Example:

1. <tt:AnalyticsModuleDescription Name="nn:AAA(vendor-specific)">
   ===> <tt:AnalyticsModule Name="XXX(vendor-specific name)" Type="nn:AAA(vendor-specific type)">
   <tt:AnalyticsModuleDescription Name="nn:BBB(vendor-specific)">
   ===> <tt:AnalyticsModule Name="YYY(vendor-specific name)" Type="nn:BBB(vendor-specific type)">

2. <tt:RuleDescription Name="tt:CCC(vendor-specific)">
   ===> <tt:Rule Name="WWW(vendor-specific name)" Type="tt:CCC(vendor-specific type)">
   <tt:RuleDescription Name="tt:DDD(vendor-specific)">
   ===> <tt:Rule Name="ZZZ(vendor-specific name)" Type="tt:DDD(vendor-specific type)">

Thank you.

[Player1-DON]

I second this request. @coohottim I would you like to hear more about vendor-specific type you have in mind.