I would suggest barrier=gate; access=private, presuming the gate is occasionally unlocked by the land owner. The routing agents need to realise that it is not ideal for pedestrian access, so access=no or access=private should do it.

In English, a farm is a general term for everything on a farm site - the buildings, yard and fields. So farmland and farmyard are just more specific terms. I am fine with landuse=farm for a general definition of the purpose of the land. See http://en.wikipedia.org/wiki/Farm for European definitions.

Is there any point recording noexit at all? The data in OSM as used by routing algorithms will determine itself that there's no exit, and they may need to route inside a noexit section too. Other mappers just want to know if somewhere needs more attention, so perhaps use FIXME="Incomplete way" instead on the final node?

That wasn’t there earlier.

Not an attribution for OSM in sight.

Personally I prefer to align the Bing aerial to the OS_OpenData_StreetView tiles based on buildings and junction central points, on the basis that the OS tiles after conversion to WGS84 are still likely the highest precision available in terms of allowable use.

There are already default maximum speed limits on a per-country basis by highway type:
osm.wiki/OSM_tags_for_routing/Maxspeed

So I typically add any exceptional speed limits that couldn't be implicitly derived.

Though the last time I checked Skobbler didn't use any of the implicit defaults, hence a lot of missing speed limit reports on the MapDust site.

Perhaps the first trace was someone using a smart phone in a light aircraft.

Probably because Microsoft could withdraw it (or start charging) at any point, no derivative versions from it could be easily made, requests for feature improvements could be ignored, etc.

I too would like to see addr:housename rendered in preference to addr:housenumber, but for now I'll continue adding an additional name tag to ensure that house names are displayed.

Postcodes are codes associated with addressable properties, not the road itself. Roads can be considered to fall wholly/partially within postcode areas by the outline shape that is made from the properties. In OSM, there is the "postal_code" tag for rough use on a way. Better would be drawing the outlines from the now-legal Bing aerial imagery and then assigning the addr:* fields, including addr:postcode, from local knowledge.

(except where lit=no on them)

Perhaps you could render highway=street_lamp as point light sources?

Create a new relation, with type=restriction, and restriction=no_right_turn tags and add to the relation the way before the junction with role 'from', the junction node with role 'via' and the restricted right turn way with role 'to'. Be aware that not all routing algorithms currently support turn restrictions, but the surviving ones likely will.

You could use addr:housename for the taught subject and addr:housenumber for the building identifier, then use the name tag to display the building code by default.

Double posting shouldn't be possible if a simple content hash is made and compared before adding another entry on the server.

Spam with compliments :)

Soccer and football are shortened terms for Association Football, so rather than use a tag that's specific to US/Australia (but it is distinct in meaning) I opt for sport=association_football, which is a similar name format to the other options. It's up to the renderers to apply a suitable graphic for that tag. Soccer may be shorter, but the rest of the world calls it football.

Spam didy do dar spam!

There doesn't appear to be a means of saying that the spots should be ignored because of being false positives like the KeepRight site can do.