> The harder you make it for them to edit, the less volunteers you’ll get.

I'm not sure I like OSMs obsession with the data model. I guess this has to do with its business model, but then let's not pretend the product manager is tasked to optimize for end-users.

I'd like it to focus on the UI. The easier it is to input a geographic thingie and the easier it is to visualize the geographic thingie, the better OSM both for users and volunteers.

Two issues to strengthen my point:

1. The osm-tag mailing list regularly discusses how tags are visualized in various renderers when recommending which to choose.

2. Quick mobile-based correction are nearly impossible with OSMAnd. I'd love to take a picture and write a quick note like "speed limit changed", so that someone (perhaps a bot) can pick this up and update the data model. Same with restaurant opening hours. Or various POIs.

This can be done with StreetComplete (Android app) - long press on map to create note, photo can be added.

> Same with restaurant opening hours. Or various POIs.

You can also outright survey this with StreetComplete. See https://github.com/streetcomplete/StreetComplete

Note: speed limit needs to be enabled, it is disabled by default. It is also unavailable in USA due to horrific default speed limit system which requires massive work to support.

Disclaimer: I am one of people working on StreetComplete

> I'm not sure I like OSMs obsession with the data model.

Given effort that went into various parts - fundamental data model has not received any changes for a long time. I would not describe it as obsession.

> I guess this has to do with its business model

OSM do not really have business model, it is not a business