Validate social media tags

[tastrax]

The consensus seems to be that any listings using website=xxx.facebook,xxx should instead use contact:facebook. Likewise facebook= should also be changed to contact:facebook=

Perhaps this could be added to the validation

https://taghistory.raifer.tech/#***/facebook/&***/contact:facebook/

[tastrax]

This could also apply to lots of social media accounts

facebook= instragram= twitter= youtube=

could all be changed to contact:'socialmediaaccounttype'=

[1ec5]

Related to openstreetmap/iD#3915 and openstreetmap/iD#7566.

[tastrax]

The two issues above are more related to phone, email and website - I think folks adding their social media accounts is a different issue. For instance what tagging would you use to add all four social media accounts PLUS a website?

[1ec5]

For instance what tagging would you use to add all four social media accounts PLUS a website?

No argument there. I was just trying to provide context for the part about changing facebook to contact:facebook. The contact:* namespace has been proposed as a comprehensive namespace that includes phone and website, but in those issues above, the argument against preferring the namespace was that phone and website are more often used without a namespace. Sorry for not making that relationship more clear.

[josephguillaume]

If this goes ahead, I request that the solution is to add the contact tag without removing the website tag. As discussed on wiki in 2017, and more recently, we need a way of indicating that the social media page is the only official presence on the web, and allowing the official website to be a social media page is the easiest way to do that.

• https://www.openstreetmap.org/changeset/98396819
• https://wiki.openstreetmap.org/wiki/Talk:Key:website#Key:website.23Best_practice_modification

[ZeLonewolf]

There are two parts to this issue. One is converting website=*facebook url* to contact:facebook, and the other is converting facebook to contact:facebook.

The second part, key renaming from facebook to contact:facebook (and the same for instagram, youtube, twitter, etc) should definitely be done.

The website=* tag should NOT be removed just because it's a social media site. There is also the question of how it gets represented. If the website is http://twitter.com/realPizzaShop, should contact:twitter have that whole URL or @realPizzaShop? I don't think iD should make that decision, and website=http://twitter.com/realPizzaShop is still correct tagging by itself.

[matkoniecz]

The consensus seems to be that any listings using website=xxx.facebook,xxx should instead use contact:facebook

What about cases where main website of restaurant is a facebook page? In such sad cases website=xxx.facebook.xxx should be fine.

[tastrax]

The question for me is 'how do we know if this is the main website' for the business? I suspect many folks just add the facebook site as website as that is where they have seen mention of the business, without looking any further. I also think the insistence to tag to website as the primary web reference is close to tagging for a renderer.

But in usual OSM fashion I will go with the flow and duplicate the facebook tag to website if its the only URL mentioned.

[josephguillaume]

On the wiki talk page, it's now been pointed out that: "If the POI has no website and no social media presence, how would we then indicate that no official website exists?" I'm now thinking specifying website=no might be a reasonable option, with social media pages limited to the contact namespace.

Note also that in the OSM spirit, feel free to not touch the website tag and let someone else worry about it :-)

[tyrasd]

I'm hesitating a bit, because https://wiki.openstreetmap.org/wiki/Key:facebook is not yet marked as a deprecated tag, and there is still quite significant number of objects tagged with it. :thinking:

[danieldegroot2]

Related:

• [Tagging] Feature Proposal - RFC - Social media contact prefix
• https://github.com/openstreetmap/iD/issues/6121#issuecomment-477331509 (ignore other comments)