It's not supported by signs to add `foot=no` when it is not signposted. `sidewalk=no` is sufficient at first.
There are many roads where it is not realistic to walk or bike, but have no signposted bans.

Some have also discussed whether `addr:building=` should be used. Perhaps it can be used in subbuildings ie `addr:building=1` + `addr:unit=1A` to show Tower 1A and 1B belongs to the same buildings. In this case, they are the same for one house, so not especially needed yet.
Another question is whether "Tower" or "House" should be included. For `ref=`, numbers are enough for blocks, and "Tower" is usually coded as "T1". But to generate an address with `addr:unit=`, it is unclear how it should be.

Thanks. There is another good question, as `addr:housenumber=` is the number used with street or village. It's unclear what blocks should use. I have used `ref=` and `addr:unit=` together for now.
(According to some definition `addr:unit=` can be used when "inside divides into different units or staircases, where certain apartments/flats/offices can only be reached through a specific unit", so it seems more applicable to subbuildings found in modern apartment towers, ie Tower 1A and 1B inside the same Tower 1 physically. Consequently, it looks usable for houses, as different buildings in a compound can be called "units" overseas. Shop "unit" in a building may be better off using `addr:door=`.)

`addr:place=` should only be used for villages which have address numbers assigned to them. It is very common to have housing estates within villages.

Also `usage=` should not be used together with `service=` with few exceptions.

This is already added as osm.org/way/530830954 ?
Please don't attach unrelated features along areas. This makes editing difficult, and does not represent reality.

Please don't attach unrelated features to tracks. This makes editing difficult, and does not represent reality.
Unless the structure edge is exactly below the centerline of track, this does not make sense. The entire shape has also been broken here.

Please don't add random transliterations. This is unneeded, and doesn't reflect common usage.

Please don't attach unrelated features to roads. This makes editing difficult, and does not represent reality.

`name=` is for the most common name in existing public use.
Please discuss with the local community first before these changes. Use OpenHistoricalMap to show the full history.

`name=` is for the most common name in existing public use.
Please discuss with the local community first before these changes. Use OpenHistoricalMap to show the full history.

Please do not remove other names.

`name=` is for the most common name in existing public use.
Please discuss with the local community first before these changes. Use OpenHistoricalMap to show the full history.

`name=` is for the most common name in existing public use.
Please discuss with the local community first before these changes. Use OpenHistoricalMap to show the full history.

`name=` is for the most common name in existing public use.
Please discuss with the local community first before these changes. Use OpenHistoricalMap to show the full history.

`name=` is for the most common name in existing public use.
Please discuss with the local community first before these changes. Use OpenHistoricalMap to show the full history.

Please don't attach unrelated objects to roads. This makes editing difficult, and does not represent reality.

`name=` is for the most common name in existing public use.
Please discuss with the local community first before these changes. Use OpenHistoricalMap to show the full history.

`name=` is for the most common name in existing public use.
Please discuss with the local community first before these changes. Use OpenHistoricalMap to show the full history.

Please read osm.wiki/Talk:Buses#Bus_Route_Naming etc. This is already provided for in `description=` and `from=` + `to=` .