search

AMSP-04 / NETN-ETR

NATO Education and Training Network (NETN) Entity Tasking and Reporting (ETR) Module
Other
2 stars 0 forks source link

Change QueryCapabilitiesSupported and CapabilitiesSupported to be TaskManagement #26

Closed lofstrandbjorn closed 4 years ago

lofstrandbjorn commented 4 years ago

Is there a rationale or reason for QueryCapabilitiesSupported and CapabilitiesSupported to be SimCon interactions and not TaskManagement?

bergtwvd commented 4 years ago

Rationale:

Otherwise there is no way to programmatically find out what is supported by a plugin.

lofstrandbjorn commented 4 years ago

I understand that Tasks and Reports are optional but what is the difference between SimCon and TaskManagement interactions and why should the QueryCapabilitiesSupported not be a TaskManagement interaction?

bergtwvd commented 4 years ago

Some time ago we had a discussion if MagicMove and MagicResource should be part of ETR. We concluded maybe not, but keep them in for now. And put them aside under Simulation Control - SimCon.

For reasons - currently - unknown the two capability related tasks ended up there too. Need to check why.

martin-s commented 4 years ago

I agree with @lofstrandbjorn and propose to move the capability interactions to task management group. Second, magic move and magic resource belong to the task group, IMHO. Further question arises from that: Do we need to reply with a taskstatusreport for these interactions?

Regarding the SimCon group, I would see a new NETN SMC, for example. As its not related to a specific entity, at first.

lofstrandbjorn commented 4 years ago

QueryCapabilitiesSupported and CapabilitiesSupported moved to TaskManagement