It appears you changed official_ref but not source:official_ref, can you complete this please?

They were correct at time of authoring in those less common cases, and there are plenty of instances where the county council has what I consider outdated but legally defined uses of C-road where obviously things moved on, dual carriageways occurred, roads downgraded into paths etc. so they still technically have those references until the council renumbers, which seems to be a never-ending saga of non-happening.

I'm not quite sure that you understand the meaning of accuracy, as amalgamating has nothing to do with that, but being more specific with the key name potentially does (at the cost of repeating the primary key name and increasing length).

My point was about the lack of a wiki article. I added those references for most of Norfolk in the first instance, and had freedom to chose what I thought was the most sensible key name. I'm not sure how the database is any more accurate now than it was before, you've added nothing of new value other than easing a perceived issue with search/canonicalisation that I've already pointed out isn't a problem elsewhere. My critique of your key choice is in changeset/35989077. Aren't you meant to discuss this sort of mass edit in advance?

If you're going to batch change tagging nationally without the consent of authoring users based on a 3-year old thread among a few then I suggest you at least make a wiki page documenting your particular preferred key name, as surely not all C roads have been mapped nationally yet?

The re-use of "highway" in an alternative reference key name, when there's already a highway main key, seems a bit excess to me. These references after all are mostly issued and used by the main official provider, be that a transport authority or street name and numbering department of a city/county council. If there's more than one then the usual approach of ":provider" suffix would do. I'm not sure why the alternate name needs to be more precise, the valuable information is the identifier value itself. Of note, Nominatim doesn't index any of these key names (and said they wouldn't when asked), so search will likely seek keys ending in '_ref' I imagine.

Not sure what happened there, was uploaded in JOSM with title "Store closure (signs remain)" and source "survey".

The tag you wanted is "maxheight" with a value of "2.7" (default unit is metre). I don't know why you added an access=private tag, as that has since prevented pedestrian and vehicle routing through the gate.

Having taken a quick look at Street View I noticed a small sign from the south-bound direction, suggesting "Public Footpath" was tagged as though official, instead of the probable recommendation to avoid people crossing on the bridge asphalt there. I've removed those tags now.

I didn't add those tags, they were just copied to branched parts of new ways without history showing that fact. So I can't qualify the nature of public right of way. I suggest you add a map note.

Puzzling that, and rightly pointed out, so thanks. I've removed those curious tags from the two adjacent ways, given the existing speed limit is already 30 mph there (though due to change to 20 mph in April).

In this particular case, I accept the contracted form is acceptable as I can find no official alternate form. The short_name tag will help search agents still match with a full form query.

I have reviewed 1,034 churches in Norfolk and the Church of England website and I would say around 60% of them use the written word Saint when self-describing. The signage is shortened I believe through brevity, a contraction, not an abbreviation, and for search systems it is far easier to reduce than to expand to assist in search matches. A user could search for "St Something", "St. Something" or "Saint Something" and all should resolve.

Why use "St " abbreviation in churches when "St " has for years been unaccepted for road name abbreviations?

See osm.wiki/Names#Name_is_the_name_only

Please stop adding the parish/village geographic name to churches. The churches are primarily named after saint dedication. It isn't sufficient to append location to uniquely identify, given St Margaret in each of the two Wiltons. Nominatim certainly isn't up to the job of search, given it can't find suburb names or locate objects near to hamlet/village/town properly, but that's a separate issue to the data.

Good spot, seems I tagged that erroneously thinking it was only bus/taxis/cycle but the restrictive sign is indeed just for motor vehicles.

Curious that, perhaps an excess tag paste on to an adjusted location from aerial imagery alignment during editing (as the wrong mounting value hints). There was only one box there, so I have deleted my newer node and refined the position of existing slightly.

I put the addr:* and phone tags on the building, since it is the building that is addressable for postal delivery and location, plus the land line installation was there too. Extracting these to the outer polygon is perhaps useful for school search result, but is less precise. Plus you'll note there are hundreds of schools already mapped in the way described above.

Have only memory of walking around the area from a year or so ago, driving past and Bing aerial. Looking at the aerial imagery again for The Londis there does look to be a sizeable building with non-residential new-looking roofing. So I've drawn that and tagged it. Suggest you confirm via http://www.overstrandparishcouncil.org.uk/contact-us/