When has this ever happened?
Quite frankly I think the idea is fine, although it will be a lot of work. Projects like these tend to work better when done in small individual packets, like UCGO, UMMU, Orbitersound, and Camshake. If one component can work effectively on its own, no work will be wasted if one feature ends up being a dead end.
I consider those all the "one size fits all solution" its unrealistic, limited and often causing more trouble in the design, than it helps to solve.
Take camshake. It doesn't care about my add-on and I can't control it. I only use it, if I need a stupid cam shake effect, that I have not yet implemented. So, usually never.
This discussion all goes into the same direction: How can we enable more people to make more and much worse add-ons?
Generic vessel could be the optimal solution for non-programmers. LuaVessel is great for those who can program a bit.
Why overload this all now with some strange pseudo-standard, that only makes developing good add-ons harder?
Really: I have never seen worse crap than the spacecraft3 add-ons. They look mediocre and play bad. You can stick great meshes there. And ruin them that way, because players have not only to fly a mission, but also hit some number keys in the right order to prevent badly designed animations from fowling up - you execute essentially add-on software on the brain of the player. Great. Back to the stone age.
Where is the discussion about that? How will a standard that only strengthens the weaknesses of the generic add-on module population really improve the situation?
Why not for example suggest that genericvessel could implement Lua event handlers for it, so it is easier to customize genericvessel add-ons?
Why not rather work on a framework of really useful low-level code objects to make developing DLLs simpler, instead of kerbalizing Orbiter?
Why not just do things, instead of talking about standards that should only apply to other people?
I think I said enough here about my opinion, who has to complain about my POV, should better do it via PM, instead of encouraging me scaring potential add-on developers away. :facepalm: