On 06.05.2013 18:54, Peter Wendorff wrote: > Do they have something like a persistent ID in wikidata, yet?
I think the Wikidata page title - something like Q35525 - is intended to be rather stable. Of course there are sometimes problems, such as duplicates or interwiki conflicts, that make it necessary to change items. But unlike unlike OSM, Wikidata actually cares about providing an ID for a distinct semantic entity. In my opinion, this is a major reason to link to Wikidata using OSM tags, and not the other way round. (Improving our data model in that regard doesn't seem realistic in the short term.) > Let's see this example: A building that was a merchants kontor a few > hundret years ago, and now contains a museum and a restaurant, while in > between it was - let's say - a hospital). That's historical mapping. The problems would be the same for e.g. the name. But as for the parts of the example that are not directly "historic": > - the merchant's person page (his office) Wikidata would link to their internal building item instead. Not our job imo. > - the museum's page Can be linked using the wikidata key at the museum POI. > - the restaurant's page Can be linked using the wikidata key at the restaurant POI. > - the architect's page Can be linked using the architect:wikidata key at the building. It could be argued that we should leave that to Wikidata, though - they have an "architect" property for buildings themselves. > - the page of the person where the name of the building comes from Can be linked using the name:etymology:wikidata key at the building. Again, we theoretically could omit this and instead rely on Wikidata's "named after" property. > Perhaps look into the overpass-permanent-ID solution for that. In my opinion that's not really a good solution here. Manually creating Overpass API queries is too hard. Tobias _______________________________________________ talk mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk
