Clarify how to handle 0 entries in Module Status
It seems to me that situations exist where a FESA class does not have modules. ModuleStatus
is a mandatory property. So far so good. But the FESA XML validation requires at least one module to be specified. (See also this discussion)
At the moment we often see module names like: {myModule1,myModule2}
which is not helpful for us or for any user.
I think it is okay that ModuleStatus
is mandatory so that each device can be "asked" for modules but I can see that it might not be applicable for all classes. So, just to give an example about where this request is going, maybe one of the following could be done:
- Allow the number of modules to be zero in the XML validation
- Define how a class should look like if no modules are present so that it is consistent and not confusing. For example state that is has to specify as single module with the name
unused
. - If there actually are modules in all of the classes (Like WR Timing receivers or similar) specify what those modules should be and what they should be named