Jo, I believe you are thinking too far and I suspect of use cases that don't actually exist for the wikidata tag itself, for the *:wikidata tags perhaps.
The wikidata tag gives a one to one mapping between an OSM object and its wikidata entry (I know that this is a bit of a simplification in that you could and will have multiple OSM objects for the same wikidata entry, but that doesn't actually change any of the arguments) an API could be as simple as a file generated once per per day and which could, naturally, take manually added tags in to account. @Mateusz I believe that adding missing wikidata or OSM entries is orthogonal to the question. You don't get around that in any case. What you do avoid by not tagging in OSM is maintenance (given that OSM objects are not necessarily a persistent reference to a single real world entity). And maintenance would include adding a wikidata tag to new objects in OSM, which for the next years likely going to be the largest source of errors. Simon Am 28.08.2014 07:45, schrieb Jo: > And how exactly does one use Overpass then to extract that data once > again from Openstreetmap? > > Jo > > > 2014-08-28 0:08 GMT+02:00 Simon Poole <si...@poole.ch > <mailto:si...@poole.ch>>: > > > Given that Edward has written code that, as it seems, accurately > determines the corresponding wikidata objects for a given OSM entity, > I'm not quite clear on what the benefits of statically tagging the > references on OSM objects is supposed to be. Wouldn't providing this as > an API make a lot more sense with numerous added advantages (avoiding > bit rot and so on)? > > Simon > > > _______________________________________________ > talk mailing list > talk@openstreetmap.org <mailto:talk@openstreetmap.org> > https://lists.openstreetmap.org/listinfo/talk > >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk