Fundamentally, in this direction of thinking, `road_marking=` could still be treated as a combination under some hypothetical `traffic_sign:*=road_marking` ...
Similar to the possibility of "signs" being fixed plates, flip-flap, or LED display, markings can be paint, surfacing (bricks) , studs, reflectors, Botts' dots, etc. This is complex enough.

1. The common language connotation is preferable over some legal interpretation. Despite being titled "Traffic Sign" , Vienna Convention is still split into chapters of "Traffic Sign" and "Road Marking". Under TSRGD, UK's Traffic Signs Manual still mentions "on the correct use of traffic
signs and road markings ". https://assets.publishing.service.gov.uk/government/uploads/system/uploads/attachment_data/file/773421/traffic-signs-manual-chapter-05.pdf
2. What would be the reason to use `traffic_sign=` , when markings already use `road_marking=` ? They aren't using `traffic_sign=solid_stop_line` . It has been suggested this be continued. osm.wiki/Talk:Key:road_marking#Stroke_details
3.1. `road_marking=` is not freeform text. Language suffixes don't have to apply. `url` is the Urali language. Does `*:url=` need to be banned? I don't oppose to alternatives eg as in osak:identifier=* , but `*:id=` is popular enough now.
3.2. `traffic_sign:id=` was rejected for many reasons. I voted against the proposal, but the idea isn't bad.

Please notice that tower-on-podium architecture is standard in HK. `building=` is used by convention. They are considered different buildings. `building=` + building:min_level=* is allowed.
`building:part=` is best used for a single tower, and parts of each tower.

I'm transitioning from `road_marking=` to `road_marking:id=` as words are predominant in `road_marking=`

This is obviously not a `traffic_sign=`

1. Please don't delete roads that will be reopened. This wastes others' work, and causes more work in the future. It's bad for applications with low data update frequency.
2. There's an overlapping segment in slip road. It has no raised separation on the other end.

Please don't connect left-turn slip lanes to the same point of the main lanes. This distorts the left turn.

1. What should be used here is `addr:suburb=`
2. Please stop reusing the same unrelated comment. It pollutes that project, this changeset, and your image.

1. You removed the learner driver restriction
2. The *:lanes:conditional=` syntax is wrong. JOSM has a bug. That's not what is complaining.

This is a less simple issue. Many "Playground" were `=playground` before wrongly, which is defined for children's playing only. I corrected them to `=sports_centre` to emphasize they are for sports, and differentiate from other "Park". `=sports_centre` is not limited to indoors.

`landuse=` in HK is effectively corresponding to the lot. The Luk Yeung development can be considered part of the depot. `landuse=` should be as simple as possible. You shouldn't split a `landuse=residential` for a mall and estate separately either.

This is not a conflict, but caused by existing issues. `landuse=railway` is correct. Problem is housing estates don't have a feature, so they have to use `landuse=residential` + `residential=apartments` .

1. This obviously doesn't reflect the depot area. Please see the other changeset.
2. Please don't delete then recreate the same points. You can detach the area.

1. This is not `tunnel=yes` . `covered=` is already used. At most, we can debate whether it should be `=building_passage` , but there's no "building" left or right at ground level. Please don't edit for validators.
2. You removed the `service=yard` ...

Please don't delete directly, as they represent a shop space, and may contain an address. Change it to a plain "point" to eliminate it.

Please notice these info should be added on the site way/124697425 , not the `building=`

Please don't blindly correct, or make uninformed assumptions. There is a noticeable sidewalk here. The existence of `footway=sidewalk` doesn't affect that.

Please don't delete shops with addresses. Change them to a plain "point".

Please use `branch=` and not add that to the `name=` (unless that's really part of the original naming as in hotels)

6. `=site` is not neccessary in the simple 2D case of all objects inside a polygon. It's only needed for complicated 3D situations.