The part on adding new entry definition occurs only after the discussion on the service=driveway talk page. Unfortunately, it is not possible to find a better definition for a generic term other than driveway2, as the intention was to trace to the SHC definition so that this broader definition can be used as the classifier tag.

The initial proposal page for parking_aisle and driveway never included statements on issue (1), the changes for (1) was also added directly to the Wiki without any discussion on Wiki talk page/proposal process in 2016/2017. People should not be expecting different process where in the first place, this was never discussed on the talk page when implementing the changes for (1) in 2016 unlike when the service=driveway2 page was introduced following discussion. The more straightforward resolution is to simply remove the part that was never approved, which is the proper resolution steps in the proposal. However, there is great resistance to changing the status quo, and that results in the service=driveway2 tag documentation following a very detailed and comprehensive discussion, unlike the change that occurred in 2016/2017.

Why is there a need to mention “one mapper that mapped 3000 ways” on the Wiki page, where all the page attempts to do is to detail what constitutes the conditions that the tag applies to, and what are the differences with respect to the other tag. The Wiki is always used to clarity tagging conventions, but never before attempting to document what a user did in the main text.

This statement here is clearly a targeted attack on that particular user, and coming from a OSM US board member and OSM Wiki Administrator, this behaviour is clearly upsetting and of poor judgement.

I agree with the rational that it is possible to directly extract these information by working directly with the data even without the group relations. However, this makes maintenance and verification of such route relations difficult unless has access to the entire database and can do filtering on such data directly.

The second option is to use wiki pages to maintain such group relations which is cumbersome and the time effort to maintain these pages with the number of relations (around 300+ and growing) is not worthwhile.

Good job done!