Re: [Tagging] Subsequent wikipedia links

2014-07-09 Thread Martin Koppenhoefer
2014-07-09 16:57 GMT+02:00 John Packer : > I removed the link to the key url=* because it's own wiki page advises it > shouldn't be used, so I figured there was no need to link it here. > Thanks for pointing at this, I have amended this sentence to make more sense, please check: http://wiki.ope

Re: [Tagging] Subsequent wikipedia links

2014-07-09 Thread John Packer
I removed the link to the key url=* because it's own wiki page advises it shouldn't be used, so I figured there was no need to link it here. As far as I understood, although it might make sense to tag an URL in some cases, the meaning of this key is too generic, making it hard to be used by tools.

Re: [Tagging] Subsequent wikipedia links

2014-07-09 Thread Martin Koppenhoefer
2014-07-09 16:37 GMT+02:00 John Packer : > I made some changes to the page Key:wikipedia on the wiki. > Please review: > http://wiki.openstreetmap.org/w/index.php?title=Key%3Awikipedia&diff=1060207&oldid=1041603 > your edit looks fine to me, besides that you removed the "url" reference. This is

Re: [Tagging] Subsequent wikipedia links

2014-07-09 Thread John Packer
I made some changes to the page Key:wikipedia on the wiki. Please review: http://wiki.openstreetmap.org/w/index.php?title=Key%3Awikipedia&diff=1060207&oldid=1041603 2014-07-01 19:58 GMT-03:00 Jo : > I've been experimenting with Wikidata a bit. I'm not a Wikipedian, rather > a convinced Openstree

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 e

Re: [Tagging] Subsequent wikipedia links

2014-07-01 Thread Tobias Knerr
On 01.07.2014 22:25, yvecai wrote: > This map could also be done with a third project linking OSM and > Wikidata by automatically linking both datasets instead of manual tag > entry of technical references. > Call Overpass for OSM data (admin boundaries), then search wikimedia > commons for flags w

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 pages/ca

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 you

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 co

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 databa

Re: [Tagging] Subsequent wikipedia links

2014-07-01 Thread Eugene Alvin Villar
On Wed, Jul 2, 2014 at 2:48 AM, yvecai 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 at Wikidata).

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 enter

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 enter

Re: [Tagging] Subsequent wikipedia links

2014-07-01 Thread Andy Mabbett
On 1 July 2014 16:40, Pieren wrote: > On Tue, Jul 1, 2014 at 4:42 PM, Andy Mabbett > wrote: > >> A Wikidata ID is part of a URL and can be rendered as such; for >> example, Q173882 equates to > > It was said at the beginning that wikidata or wikipedia tags

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 Martin Koppenhoefer
2014-07-01 17:40 GMT+02:00 Pieren : > 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 ___ Ta

Re: [Tagging] Subsequent wikipedia links

2014-07-01 Thread Pieren
On Tue, Jul 1, 2014 at 4:42 PM, Andy Mabbett wrote: > A Wikidata ID is part of a URL and can be rendered as such; for > example, Q173882 equates to It was said at the beginning that wikidata or wikipedia tags will never replace OSM tags but now I see count

Re: [Tagging] Subsequent wikipedia links

2014-07-01 Thread Andy Mabbett
On 30 June 2014 14:30, Pieren 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 > I would con

Re: [Tagging] Subsequent wikipedia links

2014-06-30 Thread Andreas Goss
Am 6/30/14 15:30 , schrieb Pieren: And one of the mentionned example is providing the building operator only through the "wikipedia:operator" where most of the data consumers are simply looking for the "operator" tag. I agree this should not happen, but can also be easily fixed by either a bot

Re: [Tagging] Subsequent wikipedia links

2014-06-30 Thread Martin Koppenhoefer
2014-06-30 13:18 GMT+02:00 John Packer : > To clarify: wikipedia:operator is exactly the same thing as > operator:wikipedia. that's presumably how (most/all) people intended to use it, yes, but there is no guarantee, and there is indeed room for different interpretations as well. You'd also oft

Re: [Tagging] Subsequent wikipedia links

2014-06-30 Thread Pieren
On Mon, Jun 30, 2014 at 1:36 PM, John Packer wrote: > The main reason is that the wikipedia key is well established and supported > in some sites, which either point a link to it or use some image from the > page. No, the main reason is that the wikipedia key is still human readable where the wi

Re: [Tagging] Subsequent wikipedia links

2014-06-30 Thread John Packer
I would advise to be cautious with adding wikidata tags with a bot, because a wikipedia article could have been moved and the wikidata tag would point to a wrong page. (i.e. the bot should also perform the standard checks even in this case) I believe leaving the wikipedia tag in place while adding

Re: [Tagging] Subsequent wikipedia links

2014-06-30 Thread Jo
I'm strongly in favour of having the order as described here: http://wiki.openstreetmap.org/wiki/Proposed_features/Wikidata The advantage is that they sort near to what they apply to, name:etymology:wikidata is near to name, operator:wikidata is near to operator and so on. I'm not sure why we ha

Re: [Tagging] Subsequent wikipedia links

2014-06-30 Thread Andy Mabbett
On 30 June 2014 10:34, Andreas Goss wrote: >> but I was aware it conflicts with the language version > > > The best solution would be to just use Wikidata. If editors supported that, > then they could also always show the titel of the Wikidata tag to avoid > errors. > > http://wiki.openstreetmap.o

Re: [Tagging] Subsequent wikipedia links

2014-06-30 Thread John Packer
To clarify: wikipedia:operator is exactly the same thing as operator:wikipedia. Historically, the key wikipedia has the same order as the key source. It might seem strange since this conflicts with the language version, but that's simply the result of an "organic" growth of the tag's definition.

Re: [Tagging] Subsequent wikipedia links

2014-06-30 Thread Jo
Indeed, sorry about that. 2014-06-30 12:46 GMT+02:00 Martin Koppenhoefer : > > 2014-06-30 12:27 GMT+02:00 Jo : > >> The University of Derby would be: >> >> >> wikidata:operator=Q3183295 >> >> Devonshire Royal Hospital >> >> wikidata:operator=Q5267877 >> > > > > wouldn't operator:wikidata make mo

Re: [Tagging] Subsequent wikipedia links

2014-06-30 Thread Martin Koppenhoefer
2014-06-30 12:27 GMT+02:00 Jo : > The University of Derby would be: > > wikidata:operator=Q3183295 > > Devonshire Royal Hospital > > wikidata:operator=Q5267877 > wouldn't operator:wikidata make more sense? ___ Tagging mailing list Tagging@openstreetma

Re: [Tagging] Subsequent wikipedia links

2014-06-30 Thread Jo
Bayford: operator:wikidata=Q4874513 The ones of my previous mail should also have been operator:wikidata Polyglot 2014-06-30 12:27 GMT+02:00 Jo : > The University of Derby would be: > > wikidata:operator=Q3183295 > > Devonshire Royal Hospital > > wikidata:operator=Q5267877 > > Does the buildi

Re: [Tagging] Subsequent wikipedia links

2014-06-30 Thread Jo
The University of Derby would be: wikidata:operator=Q3183295 Devonshire Royal Hospital wikidata:operator=Q5267877 Does the building itself also have wikipedia page? Polyglot 2014-06-30 12:12 GMT+02:00 Andreas Goss : > We're presumably suggesting "wikidata=$something" but what is "$something

Re: [Tagging] Subsequent wikipedia links

2014-06-30 Thread SomeoneElse
On 30/06/2014 11:12, Andreas Goss wrote: We're presumably suggesting "wikidata=$something" but what is "$something"? Every Wikidata entry has an ID. You can find it in the URL and behind the title: OpenStreetMap: Q936 https://www.wikidata.org/wiki/Q936 So you would use wikidata=Q936 That'

Re: [Tagging] Subsequent wikipedia links

2014-06-30 Thread Andreas Goss
We're presumably suggesting "wikidata=$something" but what is "$something"? Every Wikidata entry has an ID. You can find it in the URL and behind the title: OpenStreetMap: Q936 https://www.wikidata.org/wiki/Q936 So you would use wikidata=Q936 __ openstreetmap.org/user/AndiG88 wiki.op

Re: [Tagging] Subsequent wikipedia links

2014-06-30 Thread Martin Koppenhoefer
2014-06-30 12:02 GMT+02:00 SomeoneElse : > I'd agree (that in the Bayford's HO case) having the company details on a > node within the building would be the best way to go, yes, it will be a significant improvement, but a better solution seems to me a multipolygon-relation for the company, cont

Re: [Tagging] Subsequent wikipedia links

2014-06-30 Thread Martin Koppenhoefer
2014-06-30 11:57 GMT+02:00 Andreas Goss : > I think right now the tagging of the building is incomplete. If you want > to tag Bayford & Co on the building, then the building should have a tag > office=company. At that moment the wiki or wikidata tag clearly refers to > them. > +1, the object see

Re: [Tagging] Subsequent wikipedia links

2014-06-30 Thread SomeoneElse
On 30/06/2014 10:57, Andreas Goss wrote: If the building is important I would tag the company as a seperate node on the building and then there is no confusion with the basic tag anymore. I'd agree (that in the Bayford's HO case) having the company details on a node within the building woul

Re: [Tagging] Subsequent wikipedia links

2014-06-30 Thread Andreas Goss
So in this two particular cases (Bayford's head office and building, and Buxton College with its two websites), what _actual_ tag values would you suggest? Cheers, Andy I think right now the tagging of the building is incomplete. If you want to tag Bayford & Co on the building, then the build

Re: [Tagging] Subsequent wikipedia links

2014-06-30 Thread SomeoneElse
On 30/06/2014 10:34, Andreas Goss wrote: but I was aware it conflicts with the language version The best solution would be to just use Wikidata. If editors supported that, then they could also always show the titel of the Wikidata tag to avoid errors. http://wiki.openstreetmap.org/wiki/Wiki

Re: [Tagging] Subsequent wikipedia links

2014-06-30 Thread Andreas Goss
but I was aware it conflicts with the language version The best solution would be to just use Wikidata. If editors supported that, then they could also always show the titel of the Wikidata tag to avoid errors. http://wiki.openstreetmap.org/wiki/Wikidata I think part of the confusion come

Re: [Tagging] Subsequent wikipedia links

2014-06-30 Thread Martin Koppenhoefer
2014-06-30 2:55 GMT+02:00 John Packer : > I used wikipedia:operator instead of operator:wikipedia because the former > is used way more often I think the semantics are different. The tag operator:wikipedia seems to me like the wikipedia page about the operator, while wikipedia:operator seems to

Re: [Tagging] Subsequent wikipedia links

2014-06-29 Thread John Packer
Hi, I was the one that changed wikipedia:2 to wikipedia:operator, after concluding it was really the operator, so that one should not be a problem. I used wikipedia:operator instead of operator:wikipedia because the former is used way more often, but I was aware it conflicts with the language vers