1. Please don't change `website=` to `contact:website=`, or `phone=` to `contact:phone=`. I use both for compatibility and fairness.
2. I use `contact:website=` for the contact form on a website directly. Unlike other cases where it is a synonym of `website=`, and may not be possible to make "contact" for active communications.
3. `contact:url=` is a list of contact info, similar to `opening_hours:url=`.
4. Both hyphen and space separated phone numbers are valid.

Why would you directly delete this named PoI which is clearly more informative, and in fact correct?

First of all, the direction is wrong. Separate lines are not used when there is no physical separation. This doesn't represent the reality where vehicles can change lanes on the entire length. Turn restrictions supported by `change:lanes=` are used.

This is a POC related to `footway=crossing_access` drafted in a proposal. It tries to imitate `footway=access_aisle`, `service=emergency_access=`, and the wild `service=parking_access`. It attempts to improve the meaning of `footway=link`, and sidewalk vs crosswalk issue as currently unresolved in OpenSidewalks. osm.wiki/Proposed_features/Crosswalk_clean-up#Crosswalk_as_lines

It is not a frontage roadway.

Please don't remove it without at least adding `is_sidepath=yes` (which I do not prefer)

It is converted to be part of a crosswalk, but still preserve physical accessibility.

This not a legal access. it is a couterpart to `footway=alley`. It is not a `=service`. I don't agree with using `=service` for the sake of `service=alley`. Especially as this is a public street.

Please check that this is a pedestrianized street physically usable by four-wheeled vehicles.

Please check that this sailing is suspended indefinitely.

2. More critically, `destination:ref=` is used for the road route, not exit. `junction:ref=` is the correct one with unfortunate naming.

We have discussed this before. They now are function as the main line. If you do this, the westbound downstream of EHC exit has to be `_link`=*, and there is no logical point for the eastbound to become `=motorway`. See Tuen Mun -- Chek Lap Kok Tunnel Rd as a case for Route 10.

https://taginfo.openstreetmap.org/keys/access:roof#chronology is obviously added en masse.

This doesn't do any help. `*:roof=` is not an `access:*=` mode or condition. `access:roof=` was mass-added by an organized edit osm.wiki/HOT_-_PDC_InaWARE_Indonesia_Project_(Surabaya_&_Jakarta) which uses other questionable tags such as `building:roof=` and `building:wall=` which are flagged roof:material=*#Possible_tagging_mistakes or even deprecated building:roof=* in favor of the standard osm.wiki/Tag:format`roof:*`=. There is a list of `building:roof:*=` https://taginfo.openstreetmap.org/search?q=building:roof which should be transitioned out. I have nothing to do with them.
https://taginfo.openstreetmap.org/keys/building:roof#chronology has clear jumps. The 2nd most numerous https://taginfo.openstreetmap.org/keys/building:Aroof:shape#chronology was being eliminated from the peak near 100k.
Most importantly `access:roof=` is defined as "has an access to the roof " which probably means physical means of access for inspection and maintenance, not legal access by the public. Did you verify this?

For the n-th time, please fix your application. Not fiddle with data used by everyone else.

Ok nothing. Maybe that section can be treated as otherwise.

Airport Tunnel, Scenic Hill Tunnel, and Shing Mun Tunnels are the exceptions.

I use the same criteria for other major structures as `name=` should be the most common name. Viz Tuen Mun - Chek Lap Kok Tunnel Rd Tseung Kwan O Tunnel Rd, Tsing Long Hwy, Lantau Link, and Tsing Sha Hwy.

It's not open. Should be kept at `=construction`

Please refer to Tuen Mun -- Chek Lap Kok Tunnel. While Route 10 and main line with Tuen Mun Bypass is not opened yet, it is still a `=motorway` until the roundabout. (For it, even then there is an argument to remain due to the Tunnel Road being a fork connecting with the roundabout)