search

AMSP-04 / NETN-ETR

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

Relax requirement on provided parameters #27

Closed bergtwvd closed 4 years ago

bergtwvd commented 4 years ago

Currently the ETR description states that the sender SHALL provide all interaction class parameters when sending an ETR interaction.

This is potentially asking for problems when a federate does not comply. To make the use of the ETR more robust, this requirement should be relaxed, and actually reversed: make parameters optional as much as possible, and define sensible defaults. The same approach is used in NETN-AIS, leading to much slimmer and easier to develop federates.

lofstrandbjorn commented 4 years ago

Agree. Create feature branch, implement proposed changes and make a pull-req. review.

lofstrandbjorn commented 4 years ago

LO & Henk to post list of optional parameters in this discussion.

LennartOlsson commented 4 years ago

Added Required/Optional in attached ETR-ReqOpt-LO.pdf. There are a lot of typos in the xml file, mostly corrected in the attached file. ETR-ReqOpt-LO.pdf

bergtwvd commented 4 years ago

Lennart's optional list is mostly fine. One issue we have is mentioned in https://github.com/AMSP-04/NETN-ETR/issues/38.

Henk will create a proposal for the FOM update, while at time fixing https://github.com/AMSP-04/NETN-ETR/issues/38.

bergtwvd commented 4 years ago

Done