Re: [Tagging] Where do source tags belong?

2014-07-01 Thread John Packer
Putting notes on every object armcahir mappers: keep away is just as redundant and less informative than a source tag. I don't like all those source tags, but it addresses a real problem. I meant to say: add a note=* tag explaining the situation. Otherwise it indeed wouldn't help, but when

Re: [Tagging] Subsequent wikipedia links

2014-07-01 Thread Andy Mabbett
On 30 June 2014 14:30, Pieren pier...@gmail.com wrote: the wikipedia key is still human readable where the wikidata is just an encrypted interdatabase foreign key. A Wikidata ID is part of a URL and can be rendered as such; for example, Q173882 equates to https://www.wikidata.org/wiki/Q173882

Re: [Tagging] Where do source tags belong?

2014-07-01 Thread Martin Koppenhoefer
2014-06-30 23:17 GMT+02:00 Tod Fitch t...@fitchdesign.com: My issue with source:whatever=* tags is that you need one for every tag to avoid confusion about what the source for a specific tag is and it is a manual entry prone to error. +1, and one for every node (e.g. of a way). Many mappers

Re: [Tagging] Where do source tags belong?

2014-07-01 Thread Martin Koppenhoefer
2014-07-01 0:11 GMT+02:00 John Packer john.pack...@gmail.com: (I'm not sure if OSM Messaging is built-in in JOSM, but it could be useful for quick messaging in this kind of case). there is a link: if you hit ctrl+h you'll get the versions of the selected object with clickable usernames.

Re: [Tagging] Subsequent wikipedia links

2014-07-01 Thread Pieren
On Tue, Jul 1, 2014 at 4:42 PM, Andy Mabbett a...@pigsonthewing.org.uk wrote: A Wikidata ID is part of a URL and can be rendered as such; for example, Q173882 equates to https://www.wikidata.org/wiki/Q173882 It was said at the beginning that wikidata or wikipedia tags will never replace OSM

Re: [Tagging] Subsequent wikipedia links

2014-07-01 Thread Martin Koppenhoefer
2014-07-01 17:40 GMT+02:00 Pieren pier...@gmail.com: Why should we accept one and not the others. Where is the breaking point ? I think the distinction to be made is whether the linked database is public and available under an open license. cheers, Martin

Re: [Tagging] Subsequent wikipedia links

2014-07-01 Thread Tobias Knerr
On 01.07.2014 17:40, Pieren wrote: It was said at the beginning that wikidata or wikipedia tags will never replace OSM tags but now I see counter examples or duplicates of what is already there (like on this scary proposal for the operator, architect, brand, artist, subject, name etymology

Re: [Tagging] Subsequent wikipedia links

2014-07-01 Thread Andy Mabbett
On 1 July 2014 16:40, Pieren pier...@gmail.com wrote: On Tue, Jul 1, 2014 at 4:42 PM, Andy Mabbett a...@pigsonthewing.org.uk wrote: A Wikidata ID is part of a URL and can be rendered as such; for example, Q173882 equates to https://www.wikidata.org/wiki/Q173882 It was said at the beginning

Re: [Tagging] Subsequent wikipedia links

2014-07-01 Thread yvecai
On 01.07.2014 18:08, Tobias Knerr wrote: OSM is open for all new tags. Once we admit wikidata references, what would prevent someone to add the MusicBrainz or freebase.com reference directly in OSM ? Why should we accept one and not the others. Where is the breaking point ? Technically, we

Re: [Tagging] Subsequent wikipedia links

2014-07-01 Thread yvecai
On 01.07.2014 18:08, Tobias Knerr wrote: OSM is open for all new tags. Once we admit wikidata references, what would prevent someone to add the MusicBrainz or freebase.com reference directly in OSM ? Why should we accept one and not the others. Where is the breaking point ? Technically, we

Re: [Tagging] Subsequent wikipedia links

2014-07-01 Thread Eugene Alvin Villar
On Wed, Jul 2, 2014 at 2:48 AM, yvecai yve...@gmail.com wrote: I would find more logical to make links between databases with queries rather by adding external references in one or the other. The later looks like the poor man job (oversimplifying, I don't want to put down the great job done

Re: [Tagging] Subsequent wikipedia links

2014-07-01 Thread yvecai
On 01.07.2014 21:04, Eugene Alvin Villar wrote: I disagree. If the goal is to make separate databases function as one big normalized database[1] such that there is no overlap in data, then these inter-database references are, in fact, necessary. I must admit, when I read 'big normalized

Re: [Tagging] Subsequent wikipedia links

2014-07-01 Thread Andreas Goss
Am 7/1/14 20:48 , schrieb yvecai: but no content Maybe not directly to OSM, but definitely to the maps you can make out of it. http://osm.lyrk.de/wappen/ I think this is a much better solution than upldating all those image links in OSM. And if you want to have them in OpenStreetMap you

Re: [Tagging] Subsequent wikipedia links

2014-07-01 Thread yvecai
On 01.07.2014 21:56, Andreas Goss wrote: Am 7/1/14 20:48 , schrieb yvecai: but no content Maybe not directly to OSM, but definitely to the maps you can make out of it. http://osm.lyrk.de/wappen/ I think this is a much better solution than upldating all those image links in OSM. And if

Re: [Tagging] Subsequent wikipedia links

2014-07-01 Thread Andreas Goss
then search wikimedia commons for flags with the corresponding name. Which is going to fail, because there are names that exist more than once and always the risk of different spellings, especially in different languages. Also Wiki commons often does not care that much about creating

Re: [Tagging] Subsequent wikipedia links

2014-07-01 Thread Jo
I've been experimenting with Wikidata a bit. I'm not a Wikipedian, rather a convinced Openstreetmapper. One of the problems I had with Wiktionary and Wikipedia is how data is duplicated over and over again. Wikidata finally started solving that. We should take advantage from that. Here are some