New typespec config definition - Will CSV be deprecated in future?

[wrongisthenewright]

Hi,
I've noticed that there is a new way of defining configuration files for ebusd (typespec iif I'm not wrong), as I've defined and maintaining a custom configuration for Ariston Group appliances that doesn't respect the ebus application layer (L7) I'm asking here if the new standard will in future deprecate the "standard" CSV files as a way to define configs.

I've not been able to see if the new way of configuring the daemon (that as I understand now "simply" convert these definitions to CSV lines on the fly) will in future replace the CSV.

I'm a little concerned because atm I'm not able to determine if the new config standard will be able to represent my current CSV.

TY