New proposal about traffic_sign international code mapping

It is not the first time that we have two schemes or more going on in OSM. Think about Public Transport V1 and V2 or the deprecation but not translation of parking:lane vs parking=lane scheme. Now we have some traffic signs with human readable values and others with international codes in the same place. Also there is an accepted proposal with human readable values but specialized mappers wish international codes.
Also there are more than a way of mapping traffic signs.
And we don’t map for the render/the editor…but if the render or the editor is important for us we can change the things without big problems

My proposal is voluntary because the other was finally a nightmare for me.

I remember the (from my point of view) “bad” language I had, the modifications of the wiki “in the process of voting”, or the “no reason” to say no in voting process, things that I had the sensation it only happened with that proposal (I have never read something similar in proposals in OSM, probably you know more cases than this).

The problem is as it is, we can close our eyes and say there’s no problem, we can “edit” the editors, have no better solution but not this or apply ten other subkeys but not this proposal.

For mapping traffic signs, one thing I like to contribute since I am in OSM, this will be a big problem. And I try to solution it with tools I have in my hand. Start separating this kind of information by interested mappers without being hostile to other ways of mapping is a good start to make this possible.

Please tell me other ways of make this proposal or others proposals successful about this topic. I will appreciate your comments.