I would like to keep it as simple as possible and I don't want to replace the OSM-Wiki where all usefull combinations of tags are described.
You would not only destroy the URL to the OSM-Wiki you would also damage the format checking tools that we have in Wikidata[1]. Perhaps you have a better example to let me re-think this topic. "cuisine=fastfood" is only used 12 times [2]. Greeting Tim alias Kolossos [1] https://www.wikidata.org/w/index.php?title=Property_talk%3AP1282&diff=163539475&oldid=163111676 [2] http://taginfo.openstreetmap.org/tags/cuisine=fastfood#overview Am 29.12.2014 um 13:40 schrieb Janko Mihelić: > 2014-12-29 12:26 GMT+01:00 Kolossos <[email protected] > <mailto:[email protected]>>: > > It's possible to build 1:n and n:1 relations. > > That means "amenity=marketplace" links to 2 Wikidata entries Q330284 > (marketplace) and Q132510 (streetmarket). In the other direction > "power=minor_line" and "power=line" are linking both to Q2144320 > (Overhead power line). It's in both cases a OR-connection. > As far I can see it's not possible to support an AND. > > > For this to be a valuable resource, I think we need an AND. What if we used: > > Tag:amenity=restaurant+cuisine=fastfood > > But then the Formater URL Statement of the P1282 wouldn't be entirely > correct. I think that's a small price. > > I have another suggestion. Sometimes tags mean different things in > different countries. For example highway=primary means Q765207 in > Croatia, but it means Q792334 in Belgium. For these cases I would use a > qualifier P131 (located in the administrative territorial entity) and > that means that the tag (or combination of tags) only works in that > administrative entity. > > Janko > > > > _______________________________________________ > talk mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/talk > _______________________________________________ talk mailing list [email protected] https://lists.openstreetmap.org/listinfo/talk
