I believe there’s a typo here, should be [eBUS 2.0] Configuration support/contribution 
Sorry to ask again, but do you plan to implement csv report in the
2.x binding as well ? Because for me it’s the best tool to identify the unkown messages, then to improve json configuration files.
I use it to import messages in Excel and by using pivot table and filtering, I can have extensive list of messages in a very comprehensive way.