On 19.09.2017 09:46, SwiftFast wrote: > Imagine an app where you'd click a shop, then you'd get a popup with a > logo(see my other proposal), a slogan, and a description. All of these > help a user understand what they're looking it.
While I accept the argument that logos allow easy visual identification (assuming we're allowed to display them – not sure about the legal situation here), I do not personally expect slogans to be particularly helpful for the user. To me, slogans are advertising, not useful information. Slogans also aren't always visible on the ground, and feel quite far removed from geographic data: It's the slogan of the operator of the shop at this location – which is one jump further than what is typical for OSM data. >> Moreover, in your exemple, I don't see the point to repeat on all >> McDonald's the same tag. A separate database with brand data would >> fit more your need (Wikidata?). > > Although I agree it's a problem, it's unrelated to the proposal. Still, the proposal could help address it by promoting a "unless the feature has a Wikidata item, in which case the slogan/logo should be added over there" guideline. > The same could be said about cuisine, name > translations, website, operator, etc. Website doesn't fit into that list because it should only be used for the website of that particular feature – not the website of the brand/operator. But yes, it's true that the problem isn't new. _______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
