This proposal aims to update and modernize charging station tagging in OSM to be more explicit, easier to parse, up-to-date terminology wise, and organizationally, as well as establish flexibility for future advancements.
I have added some comments to the wiki talk page too. In summary:
This is trying to change too much in one go
Please don’t try to make big changes to existing tags (as you are proposing to do with the current tag)
Site relations are too complex; multipolygons will do.
Adding the socket info to the parking bay is a bad idea as some bays can access more than one charge point / dispenser. Better to put the socket information on the physical charge point / dispenser (it’s also easier for the mapper).
You seem to be trying to solve a problem that doesn’t exist.
Take a look at how I map charging stations. In this example I use a multi-polygon to capture the fact that the charging station covers two area. I add up all the sockets in the charging station (semi-colon separated) and add that to the amenity=charging_station area/multi-polygon relation. See example here:
And then within that area, I place a node for each man_made=charge_point and add the socket info to that. This way the socket info for each charge point is recorded on the charge point, with the summarised aggregate added to the charging station.
This fits with currently documented wiki pages and is much simpler than a site relation.
This (as quoted above) is the fundamental issue with your proposal. The bay<-> socket relationship simply does not hold true in the real world. As demonstrated in this photo where blue is the Chademo connector and black is the Type 2 CCS connector. The user has purposefully crossed the cables over thereby breaking your assumption that the left cable is for the left bay and the right cable is for the right bay.
Just for informations, following this discussion and the problems with the actual schema, i had started a draft to add the charge point, and I’ve tried to not use relations.
Feel free to pick some ideas if you want: