Re: [Tagging] Feature Proposal - RFC - Wikidata

2014-04-03 Thread fly
Some parts are still valid and not off topic.

As material:wikidata shows that we need to well define the usage of
*:wikidata.

On the other hand we already the wiki as data base for tags and their
values. So if we stay with material or surface adding link to wikidata
in the value description would be nice.

Cheers
fly

___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging


Re: [Tagging] Feature Proposal - RFC - Wikidata

2014-04-02 Thread Janko Mihelić
2014-04-02 0:46 GMT+02:00 Eugene Alvin Villar sea...@gmail.com:


 I'm not so sure about operator:wikidata=* (or wikidata:operator=* as
 suggested on the wiki talk page) and the other similar tags like that. I
 think this should be discussed more since the current set of proposed
 supplementary tags seem like an arbitrary set. Why these (operator, brand,
 artist, etc.) and not others? If we can conceivably tag other properties
 with Wikidata entities, we should have a more generalized scheme for adding
 such tags.


What do you suggest?

I think these tags are essential because the wikidata tag should be used
very carefully. People are probably going to start tagging McDonalds
restaurants with wikidata=Q38076 https://www.wikidata.org/wiki/Q38076.
That is (maybe not so obviously) wrong because that little restaurant isn't
a multinational company. It's a restaurant that uses their franchise.

That's why there should be several predefined tags so we don't end up with
lots of bad data.

operator:wikidata is better IMHO because you can also have operator:source,
operator:webpage, and it makes more sense to do it in that order.

Janko
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging


Re: [Tagging] Feature Proposal - RFC - Wikidata

2014-04-02 Thread Janko Mihelić
2014-04-02 6:10 GMT+02:00 André Pirard a.pirard.pa...@gmail.com:


 The last URL I used for OSM is  http://www.palogne.be  and I would like
 to know how I can find the corresponding Wikidata ID to go alongside.


That's one of the strengths of  Wikidata over Wikipedia. In wikidata you
just have to make a new item, give it a name and there you go. You can link
it from OSM. You can add a few attributes in Wikidata that can supplement
the data in OSM.

In Wikipedia you have to write the whole article, add pictures, and hope
that administrators won't remove it because it has no significance, or
isn't written well enough.

Janko
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging


Re: [Tagging] Feature Proposal - RFC - Wikidata

2014-04-02 Thread Martin Koppenhoefer
2014-04-02 10:47 GMT+02:00 Janko Mihelić jan...@gmail.com:

 I think these tags are essential because the wikidata tag should be used
 very carefully. People are probably going to start tagging McDonalds
 restaurants with wikidata=Q38076 https://www.wikidata.org/wiki/Q38076.
 That is (maybe not so obviously) wrong because that little restaurant isn't
 a multinational company. It's a restaurant that uses their franchise.

 That's why there should be several predefined tags so we don't end up with
 lots of bad data.

 operator:wikidata is better IMHO because you can also have
 operator:source, operator:webpage, and it makes more sense to do it in that
 order.



+1
Still in the case of a Franchise operator:wikidata would not be McDonald's
Corp. but the company that operates the small restaurant (sometimes it is
McD, but mostly not).

cheers,
Martin
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging


Re: [Tagging] Feature Proposal - RFC - Wikidata

2014-04-02 Thread Jo
I've been experimenting with wikidata tagging in OSM a bit lately. One
doubt I have is when tagging tombstones with subject:wikidata. Is that
correct? Normally that one is used when an artistic image is made of
someone. What if it's a family grave with more than one 'subject'?
What if it's only the tombstone that was possibly moved in the mean time?
So not the actual burial place anymore?

I do think it's important to be specific and quite a few of our OSM objects
have several references to Wikidata.

What I found though, is that it seems like it's necessary to create an
article on at least one WP, to make it possible to have a notable Wikidata
entry. This is not as easy as it seems with all the rules concerning living
people and notability of the Wikipedias. So maybe notability on Wikidata
should be expanded to all objects that we might want to map on OSM. i.e. if
it's physical, it can have a qualifier in Wikidata. It is further
complicated by the lack of freedom of panorama in Belgium and France,
otherwise it would be enough to add pictures of the objects to Commons and
create a category for them. (statues and buildings which don't get their
own WP pages for example)

Polyglot


2014-04-02 12:08 GMT+02:00 Martin Koppenhoefer dieterdre...@gmail.com:


 2014-04-02 10:47 GMT+02:00 Janko Mihelić jan...@gmail.com:

 I think these tags are essential because the wikidata tag should be used
 very carefully. People are probably going to start tagging McDonalds
 restaurants with wikidata=Q38076 https://www.wikidata.org/wiki/Q38076.
 That is (maybe not so obviously) wrong because that little restaurant isn't
 a multinational company. It's a restaurant that uses their franchise.

 That's why there should be several predefined tags so we don't end up
 with lots of bad data.

 operator:wikidata is better IMHO because you can also have
 operator:source, operator:webpage, and it makes more sense to do it in that
 order.



 +1
 Still in the case of a Franchise operator:wikidata would not be McDonald's
 Corp. but the company that operates the small restaurant (sometimes it is
 McD, but mostly not).

 cheers,
 Martin

 ___
 Tagging mailing list
 Tagging@openstreetmap.org
 https://lists.openstreetmap.org/listinfo/tagging


___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging


Re: [Tagging] Feature Proposal - RFC - Wikidata

2014-04-02 Thread Martin Koppenhoefer
2014-04-02 12:24 GMT+02:00 Andy Mabbett a...@pigsonthewing.org.uk:

 Then we could use wikidata:brand=



+1, or maybe brand:wikidata? Has the advantage to have all brand referers
in one block when sorting alphabetically.

cheers,
Martin
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging


Re: [Tagging] Feature Proposal - RFC - Wikidata

2014-04-02 Thread Andy Mabbett
On 2 April 2014 11:31, Jo winfi...@gmail.com wrote:

 or rather brand:wikidata (which is already in the list)

Please see the proposal's talk page for discussion of how to order the
componets of sub-tags:

   
https://wiki.openstreetmap.org/wiki/Talk:Proposed_features/Wikidata#Order_of_parts

-- 
Andy Mabbett
@pigsonthewing
http://pigsonthewing.org.uk

___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging


Re: [Tagging] Feature Proposal - RFC - Wikidata

2014-04-02 Thread Matthijs Melissen
On 2 April 2014 09:47, Janko Mihelić jan...@gmail.com wrote:
 I think these tags are essential because the wikidata tag should be used
 very carefully. People are probably going to start tagging McDonalds
 restaurants with wikidata=Q38076. That is (maybe not so obviously) wrong
 because that little restaurant isn't a multinational company. It's a
 restaurant that uses their franchise.

Is the assumption that one Wikidata object should correspond to at
most one OSM object? If so, it would be good to make that assumption
explicit.

I think using Wikidata would also make it easier for external parties
to link their data to OSM data. Currently that's very difficult
because OSM identifiers are not guaranteed to be stable. For example,
someone who wants to make a database of restaurant reviews could link
their reviews to the Wikidata identifier, and use that identifier to
fetch the geographic location.

If Wikidata turns out successful, in the long run we might even
migrate tags like cuisine= and wheelchair= to Wikidata (although
that's probably a license nightmare, again one of the reasons why I
dislike the current license). We might even create OSM editors that
can edit Wikidata directly transparent to the user (some fields would
be OSM fields, some fields would be Wikidata fields).

-- Matthijs

___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging


Re: [Tagging] Feature Proposal - RFC - Wikidata

2014-04-02 Thread nounours77
Very interesting and important discussion.

Are you all aware of that one of the main subjects of the next wikimedia 
hackthon in May in Zurich is about this? Maybe it is interesting to discuss 
this subject in Zurich? Like send the worked proposal to the people there or 
something??

nounours77


See:

https://www.mediawiki.org/wiki/Zürich_Hackathon_2014  under Maps Integration
https://www.mediawiki.org/wiki/Zürich_Hackathon_2014/Geo_Namespace
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging


Re: [Tagging] Feature Proposal - RFC - Wikidata

2014-04-02 Thread Janko Mihelić
2014-04-02 13:46 GMT+02:00 Matthijs Melissen i...@matthijsmelissen.nl:

 Is the assumption that one Wikidata object should correspond to at
 most one OSM object? If so, it would be good to make that assumption
 explicit.


I wrote exactly that here:
https://wiki.openstreetmap.org/wiki/Proposed_features/Wikidata#wikidata.3D.2A

There shouldn't be more than one Openstreetmap item with the same Wikidata
ID.

Although that's not entirely possible. The reason is that our rule one
object per entity isn't always enforced. For example, one street is often
made of several parts that have the same name. If we were strict with that
rule, we would use relations for all streets (which isn't practical). So if
there was a Wikidata entry for a street, there should be a Wikidata tag on
every street part.

Janko
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging


Re: [Tagging] Feature Proposal - RFC - Wikidata

2014-04-02 Thread Jo
In order to apply the name:etymology:wikidata=Q... tags, I created
associatedStreet relations for most cases.

Polyglot


2014-04-02 14:47 GMT+02:00 Janko Mihelić jan...@gmail.com:

 2014-04-02 13:46 GMT+02:00 Matthijs Melissen i...@matthijsmelissen.nl:

 Is the assumption that one Wikidata object should correspond to at
 most one OSM object? If so, it would be good to make that assumption
 explicit.


 I wrote exactly that here:

 https://wiki.openstreetmap.org/wiki/Proposed_features/Wikidata#wikidata.3D.2A

 There shouldn't be more than one Openstreetmap item with the same
 Wikidata ID.

 Although that's not entirely possible. The reason is that our rule one
 object per entity isn't always enforced. For example, one street is often
 made of several parts that have the same name. If we were strict with that
 rule, we would use relations for all streets (which isn't practical). So if
 there was a Wikidata entry for a street, there should be a Wikidata tag on
 every street part.

 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


Re: [Tagging] Feature Proposal - RFC - Wikidata

2014-04-02 Thread Tobias Knerr
On 02.04.2014 12:24, Jo wrote:
 I've been experimenting with wikidata tagging in OSM a bit lately. One
 doubt I have is when tagging tombstones with subject:wikidata. Is that
 correct?

wikipedia:subject is mentioned on the German wiki page
https://wiki.openstreetmap.org/wiki/Friedhofmapping
(graveyard mapping, has no English equivalent unfortunately). So
subject would appear to be at least a common choice.

Of course there's the problem when you have a tombstone with artwork
that depicts some real or mythical person who would also be a candidate
for subject ...



___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging


Re: [Tagging] Feature Proposal - RFC - Wikidata

2014-04-02 Thread Martin Koppenhoefer
2014-04-02 14:47 GMT+02:00 Janko Mihelić jan...@gmail.com:

 For example, one street is often made of several parts that have the same
 name. If we were strict with that rule, we would use relations for all
 streets (which isn't practical).



it isn't practical to create them for all streets, but my guess is it would
well be doable for all streets with a wikidata correspondent. The same for
rivers (where it would be generally desirable to have a common object, as
these have to be split for several reasons, e.g. at language borders
because of the changing name-tag).

cheers,
Martin
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging


Re: [Tagging] Feature Proposal - RFC - Wikidata

2014-04-02 Thread Janko Mihelić
2014-04-02 15:35 GMT+02:00 Martin Koppenhoefer dieterdre...@gmail.com:


 it isn't practical to create them for all streets, but my guess is it
 would well be doable for all streets with a wikidata correspondent. The
 same for rivers (where it would be generally desirable to have a common
 object, as these have to be split for several reasons, e.g. at language
 borders because of the changing name-tag).


Ok, I agree. Then we can set it in stone: only one unique wikidata=Q* tag
per database. If a Wikidata item is about two real-world entities, create a
relation in OSM (if it's in the spirit of OSM tagging) or make new Wikidata
items which can be sub-items of the main Wikidata item.

Janko
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging


Re: [Tagging] Feature Proposal - RFC - Wikidata

2014-04-02 Thread Andy Mabbett
On 2 April 2014 13:05, nounours77 kuessemondtaegl...@gmail.com wrote:

 Very interesting and important discussion.

Thank you.

 Are you all aware of that one of the main subjects of the next wikimedia 
 hackthon in May in Zurich is about this? Maybe it is interesting to discuss 
 this subject in Zurich?

Yes; unfortunately I was not able to secure a scholarship to attend.

-- 
Andy Mabbett
@pigsonthewing
http://pigsonthewing.org.uk

___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging


Re: [Tagging] Feature Proposal - RFC - Wikidata

2014-04-02 Thread Andy Mabbett
On 2 April 2014 13:47, Janko Mihelić jan...@gmail.com wrote:

 There shouldn't be more than one Openstreetmap item with the same Wikidata
 ID.

 Although that's not entirely possible.

There is also the case of sets;  for example, four carvings which form
a single artwork, but which are mapped as separate entities.

-- 
Andy Mabbett
@pigsonthewing
http://pigsonthewing.org.uk

___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging


Re: [Tagging] Feature Proposal - RFC - Wikidata

2014-04-02 Thread Eugene Alvin Villar
On Wed, Apr 2, 2014 at 1:47 AM, Janko Mihelić jan...@gmail.com wrote:

 2014-04-02 0:46 GMT+02:00 Eugene Alvin Villar sea...@gmail.com:


 I'm not so sure about operator:wikidata=* (or wikidata:operator=* as
 suggested on the wiki talk page) and the other similar tags like that. I
 think this should be discussed more since the current set of proposed
 supplementary tags seem like an arbitrary set. Why these (operator, brand,
 artist, etc.) and not others? If we can conceivably tag other properties
 with Wikidata entities, we should have a more generalized scheme for adding
 such tags.


 What do you suggest?

 I think these tags are essential because the wikidata tag should be used
 very carefully. People are probably going to start tagging McDonalds
 restaurants with wikidata=Q38076 https://www.wikidata.org/wiki/Q38076.
 That is (maybe not so obviously) wrong because that little restaurant isn't
 a multinational company. It's a restaurant that uses their franchise.

 That's why there should be several predefined tags so we don't end up with
 lots of bad data.

 operator:wikidata is better IMHO because you can also have
 operator:source, operator:webpage, and it makes more sense to do it in that
 order.


I would suggest that a requirement for a foo:wikidata=* tag (or
wikidata:foo=* tag) is that foo=* is already an established tag. After all,
the point of linking to Wikidata in the first place is we want a semantic
way of indicating an entity.

For example, there are lots of things named McDonald's and this makes
something like name=McDonald's or brand=McDonald's ambiguous. But by
linking to a particular McDonald's in Wikidata, we specify exactly which
McDonald's we are talking about.

Thus, I think that brand:wikidata=* or operator:wikidata=* is a semantic
version of brand=* and operator=*. So, foo:wikidata=* makes a lot of sense
if we already have foo=* in the first place.
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging


Re: [Tagging] Feature Proposal - RFC - Wikidata

2014-04-02 Thread Andy Mabbett
On 2 April 2014 15:56, Andy Mabbett a...@pigsonthewing.org.uk wrote:
 On 2 April 2014 13:47, Janko Mihelić jan...@gmail.com wrote:

 There shouldn't be more than one Openstreetmap item with the same Wikidata
 ID.

 Although that's not entirely possible.

 There is also the case of sets

One might also reasonably expect to find multiple instances of things
like material:wikidata=Q23757 (that's limestone).

-- 
Andy Mabbett
@pigsonthewing
http://pigsonthewing.org.uk

___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging


Re: [Tagging] Feature Proposal - RFC - Wikidata

2014-04-02 Thread Janko Mihelić
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 have name: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


Re: [Tagging] Feature Proposal - RFC - Wikidata

2014-04-02 Thread Jo
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


Re: [Tagging] Feature Proposal - RFC - Wikidata

2014-04-02 Thread Janko Mihelić
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


[Tagging] Feature Proposal - RFC - Wikidata

2014-04-01 Thread Andy Mabbett
I commend this proposal to the list:

   https://wiki.openstreetmap.org/wiki/Proposed_features/Wikidata

-- 
Andy Mabbett
@pigsonthewing
http://pigsonthewing.org.uk

___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging


Re: [Tagging] Feature Proposal - RFC - Wikidata

2014-04-01 Thread Tobias Knerr
On 01.04.2014 19:04, Andy Mabbett wrote:
 I commend this proposal to the list:
 
https://wiki.openstreetmap.org/wiki/Proposed_features/Wikidata

I like Wikidata and therefore want to see this proposal approved. :)

What I'm interested in, though: If an object exists both in Wikipedia
and Wikidata, would you expect both tags to be used? Wikipedia links can
be obtained from the Wikidata API for a given Wikidata ID and vice
versa, so one of the two would suffice.


___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging


Re: [Tagging] Feature Proposal - RFC - Wikidata

2014-04-01 Thread John Packer

 If an object exists both in Wikipedia
 and Wikidata, would you expect both tags to be used? Wikipedia links can
 be obtained from the Wikidata API for a given Wikidata ID and vice
 versa, so one of the two would suffice.


It might seem redundant but the key wikipedia shouldn't be removed when
adding the key wikidata to an object, because there are a number of sites
that use the wikipedia tag and don't understand the wikidata tag right now.



2014-04-01 18:17 GMT-03:00 Tobias Knerr o...@tobias-knerr.de:

 On 01.04.2014 19:04, Andy Mabbett wrote:
  I commend this proposal to the list:
 
 https://wiki.openstreetmap.org/wiki/Proposed_features/Wikidata

 I like Wikidata and therefore want to see this proposal approved. :)

 What I'm interested in, though: If an object exists both in Wikipedia
 and Wikidata, would you expect both tags to be used? Wikipedia links can
 be obtained from the Wikidata API for a given Wikidata ID and vice
 versa, so one of the two would suffice.


 ___
 Tagging mailing list
 Tagging@openstreetmap.org
 https://lists.openstreetmap.org/listinfo/tagging

___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging


Re: [Tagging] Feature Proposal - RFC - Wikidata

2014-04-01 Thread André Pirard
On 2014-04-01 23:17, Tobias Knerr wrote :
 On 01.04.2014 19:04, Andy Mabbett wrote:
 I commend this proposal to the list:
 https://wiki.openstreetmap.org/wiki/Proposed_features/Wikidata 
 I like Wikidata and therefore want to see this proposal approved. :)
 What I'm interested in, though: If an object exists both in Wikipedia
 and Wikidata, would you expect both tags to be used? Wikipedia links
 can be obtained from the Wikidata API for a given Wikidata ID and vice
 versa, so one of the two would suffice.

It has already been said that the word instead is not appropriate here
right now.
On the long range, the practical success of two methods will decide by
itself.
Practically, if I click item with ID Q1722
https://www.wikidata.org/wiki/Q1722, the first impression is
 A script on this page may be busy, or it may have stopped responding.
 You can stop the script now, or you can continue to see if the script
 will complete.
then quite a dump of seemingly computer savvy data (OK with me but
frightening many).
I suppose that it should be formatted differently, but I'd like to see
how to have an opinion.
On the other hand, Wikipedia is fast and pretty and, as indeed I often
want to switch to Дубровник for more interesting data and a challenge to
understand I click ru in the left pane.
It took me some time to get to Wikipedia from Wikidata and I was
surprised to see there reference to Wikidata only in tools.
The last URL I used for OSM is  http://www.palogne.be  and I would like
to know how I can find the corresponding Wikidata ID to go alongside.

Cheers,

André.





___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging