I think our own wikibase could be used to give a more structured semantic meaning of tags, and combinations of tags.
For example, we want to define what a McDonalds restaurant is in our database. Is it a node with name=McDonalds? Well, a parking lot could be named the same. Is it a way with amenity=fastfood + name=McDonalds? Well, in China they are called differently. Is it a relation, node or way with franchise:wikidata=Q38076? What combination of tags is enough to be sure that something is a McDonalds restaurant? We have to define that somewhere. Well, this wikibase would be a database of all these combinations that can be considered to have a specific meaning. Then those items could be connected with Wikidata or other databases. Also, dataminers would have a reliable place with defined queries for their needs. But this is a bit offtopic. Janko 2014-04-03 1:37 GMT+02:00 Jo <winfi...@gmail.com>: > I'm afraid I don't fully understand the reasoning behind OSM having its > own wikidata DB. What extra (different) data would we store in it, which > couldn't go in Wikidata? I understand it in the case of Commons to store > metadata like diaphragma and lenses used when taking those pictures. > Oh, maybe we can store source and other metadata in it?.. But we're > already storing our data in a DB, aren't we? > > Polyglot > > > 2014-04-02 23:34 GMT+02:00 Janko Mihelić <jan...@gmail.com>: > >> 2014-04-02 16:56 GMT+02:00 Andy Mabbett <a...@pigsonthewing.org.uk>: >> >> >>> There is also the case of sets; for example, four carvings which form >>> a single artwork, but which are mapped as separate entities. >>> >> >> You could put the four carvings into a relation, and put the wikidata tag >> there (along with the name=* and tourism=artwork). Or you could create four >> wikidata items, and give them the attribute "part of" and connect with the >> first item. Then reference those four items in OSM. >> >> >> 2014-04-02 19:13 GMT+02:00 Andy Mabbett <a...@pigsonthewing.org.uk>: >> >> >>> One might also reasonably expect to find multiple instances of things >>> like material:wikidata=Q23757 (that's limestone). >>> >> >> I wasn't talking about xxx:wikidata=* tags. There can be lots of those. >> All sculptures by one artist should have the same artist:wikidata=* tag. >> All streets named after Nikola Tesla should >> havename:etymology:wikidata=Q9036. But there should be only one element with >> wikidata=Q384, or any other number. >> >> P.S. I'm not sure we should reference materials from Wikidata. That's >> going a bit too far. Tagging material=limestone should be enough. If we >> want to go that far with connecting OSM tags with Wikidata, there are >> better ways. I have thought about this, and with common tags like >> material=* we could make our own Wikibase installation, and connect tag >> combinations from OSM with Wikidata items. >> >> Janko >> >> _______________________________________________ >> Tagging mailing list >> Tagging@openstreetmap.org >> https://lists.openstreetmap.org/listinfo/tagging >> >> > > _______________________________________________ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging > >
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging