I would absolutely agree with this use case. Especially for cases such as the regularly mentioned Burger King. If somebody from out of town is either traveling through or armchair mapping they could be confused. If they are using the ID editor, it suggests that you "upgrade the tags" which could lead to a "Burger King" that is not part of the international Burger King tag having the same brand:wikidata tag.
I also think that the not: namespace could be useful in other cases such as not:name, so I support it. -Tim On Saturday, September 14, 2019 9:57:32 AM EDT Joseph Eisenberg wrote: > I think "not:brand" and "not:brand:wikidata" should only be used when > the name of the feature or the brand of the feature is identical (or > nearly identical) to a well-known brand. > > - Joseph > > On 9/14/19, Martin Koppenhoefer <dieterdre...@gmail.com> wrote: > > I am leaning to supporting the tag, because it offers a standard way to > > give specific hints for some special cases. The risk is that the tag could > > in theory be added with infinite value lists to any object, but we should > > not expect it to happen ;-) > > > > Cheers, > > Martin > > _______________________________________________ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
