[Tagging] Feature Proposal - RFC - Social media contact prefix

[Alan Mackie]

deja vu

Don't we have a failed proposal for this about every month or so?

On Fri, 1 Apr 2022 at 03:48, Mason Cox <MxdangerGamingYT at outlook.com> wrote:

> This does NOT mark any of the prefixed social media, messengers, or web
> services keys as approved. This is a proposal that only deprecates social
> media, messengers, web services keys that are not prefixed under the
> contact:*=* namespace.
>
>
>
> Removes tag fragmentation by using the most used keys.
>
>
>
> There is an unnecessary existence of a parallel tagging scheme on only
> some of the social media contact methods.
>
>
>
> Without diving too deep into the benefits of the contact prefix, which has
> been discussed very thoroughly on other pages, having all contact
> information under one namespace simplifies the usage while preventing any
> contact methods from overlapping with any other tags for real world usage.
>
>
>
> Simplifies the usage for data consumers who would otherwise have to
> support both at the same time. On the other side this also gives data
> consumers with all the necessary data they need if they are unaware of some
> of the several non-prefixed versions that still exist.
>
>
>
>
> https://wiki.openstreetmap.org/wiki/Proposed_features/Social_media_contact_prefix
>
>
>
> Please discuss this proposal on its Wiki Talk page.
>
>
> _______________________________________________
> Tagging mailing list
> Tagging at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20220401/9826bb82/attachment.htm>