Proposal talk:Link
Is this proposal dead?
I would still find it usefull to have something like this. Doesn't it make sense to do at least a voting?--Haves (talk) 16:44, 6 November 2015 (UTC)
why?
What can link:$(some website)=$(link) do what you can't do with the already existing website- or url-tag?
Besides, with this one can generate some more fast outdating data. Who is going to take care of it in future, once it got mapped?
Additionally, googling for that Object (as long as it has the correct name on it) should give you all the sites you want to tag.
-> oppose -- malenki 11:38, 26 May 2012 (BST)
PS: not to forget that "link" is ambiguous. Already had a look on taginfo? -- malenki 11:41, 26 May 2012 (BST)
- I just reworded the first few sentences because they didn't quite make sense, but I think I've written what the original proposer intended
- The proposal is not to replace the Key:website but about to allow an object (I think a nightclub is the example) to have an official website and in addition tags pointing to facebook and other 3rd party listings sites. Am I right?
- -- Harry Wood 14:35, 3 October 2012 (BST)
other approaches
url:[service_name]- url:facebook
- url:myspace
social_network:[service_name]- social_network:facebook
- social_network:twitter
- social_network:youtube
- social_network:myspace
- social_network:flickr
link:[service_name]- link:facebook
- link:qype
- link:twitter
web:[service_name]- web:facebook
- web:twitter
- [service_name]
- foursquare
- google+
- myspace
website:[service_name]- website:qype
ref:[service_name]- ref:qype
contact:[service_name]- contact:myspace
- contact:twitter
- contact:facebook
Keep it simple. Just service name
Tags with colons in them are mostly overkill. For example you could more elegantly and simply enter a facebook URL using as "facebook=http://www.facebook.com/pages/this-part-doesnt-matter/325001280021". I've mapped things this way already (or certainly for twitter I have)
couple of other people on IRC said the same today.
-- Harry Wood 14:37, 3 October 2012 (BST)
- sure. I just intended to avoid key collisions in the future. But I can live without that prefix--Shmias 14:51, 3 October 2012 (BST)
- after a bit googleing I added some more links to the example node 905883257
905883257
- Well known international platforms
- facebook = http://www.facebook.com/pages/_/325001280021
- foursquare = https://foursquare.com/v/a/4adcda7af964a520e84621e3
- google+ = https://plus.google.com/106569062506348263598
- myspace = http://www.myspace.com/zumiroderzudir_bar
- yelp = http://www.yelp.de/biz/zu-mir-oder-zu-dir-berlin
- established regional platforms
- qype = http://www.qype.co.uk/place/645
- berlin.de = http://www.berlin.de/restaurants/1646837-1622830-zu-mir-oder-zu-dir.html
- tip-berlin.de = http://www.tip-berlin.de/essen-und-trinken/restaurants-und-bars/zu-mir-oder-zu-dir
- Platforms I've never heard of before
- tripadvisor = http://www.tripadvisor.co.uk/187323-d942801
- partyearth = http://www.partyearth.com/berlin/lounges/zu-mir-oder-zu-dir-2/
- would you suggest to create one key for all of them? --Shmias 15:12, 3 October 2012 (BST)
- If this tagging scheme is still being discussed here, why are you, Shmias, doing things like this changeset changing all of my facebook= tags to link:facebook= on October 8, 2012? --Dobratzp 02:30, 3 December 2012 (UTC)
Do not keep it simple, keep it easy
I really like the idea of referencing content of external content providers.
- As a mapper and app developer I highly favor ids instead of urls. They make it easier to actually call external APIs and request information. The apps themselves can integrate the ids to a full url if necessary.
- I do not like the name of service/content providers as the tag name. They do not tell what the reference is about. Something like ref:service_name is much better. Then we do know it's a reference. The colon is not an issue. Manually it is easy to type, the concept behind is simple and most of all: editor applications should be smart enough to set colons automatically.
- I would like to see something like ref:facebook:page=foo or ref:facebook:group=foo as devs need to know what actual API to query. If you query page information in the user database at Facebook you might get an unexpected result, if any at all. -- andreas.balzer 00:10, 24 February 2013 (UTC+1)