Instead of adding another field to the traditional CFE_TBL "FileDef" struct/macro to indicate the EDS type, it might be better to deduce the EDS type name in some more backward compatible ways:
use the table name (which is already in the form "appname.tablename" however the names may not exactly match EDS depending on how consistent the author was)
use/overload the "description" field.
examine the C source code to determine the type name used.
The issue is that any change/extension to the FILEDEF macro is not backward compatible. Overloading the description field would still require an update to the table files, but that update would still work with the non-EDS version of the software.
Instead of adding another field to the traditional CFE_TBL "FileDef" struct/macro to indicate the EDS type, it might be better to deduce the EDS type name in some more backward compatible ways:
The issue is that any change/extension to the FILEDEF macro is not backward compatible. Overloading the description field would still require an update to the table files, but that update would still work with the non-EDS version of the software.